Acquire a token granting you access to perform sensitive operations on behalf of an identity.
Weavr Multi Product BackOffice API (v3)
Weavr Multi Back Office API allows you, as an innovator, to perform various back office operations concerning identities and their instruments, without requiring the users to be logged in.
A token is to be obtained through the access_token method, and this will allow relevant operations to be performed on behalf of this same identity.
Managed Accounts are a type of financial instrument offered by Weavr. They hold funds for their owner, and can be upgraded to IBANs so as to receive and send funds to instruments outside of the Weavr Platform, via Wire Transfers. These accounts can also be used as sources and destinations in the transfer transaction.
With the access_token representing the identity and the consent of the identity, you will be able to operations on the identity's managed accounts, such as getting a managed account's details and retrieving its statement.
Managed Cards are a type of financial instrument offered by Weavr. Cards created in prepaid mode have their own balance, whereas those created in debit mode tap into the balance of their parent Managed Accounts. Apart from being used at merchants for puchases, prepaid mode cards can also be used as sources and destinations in the transfer transaction.
With the access_token representing the identity and the consent of the identity, you will be able to perform operations on the identity's Managed Cards, such as getting a Managed Card's details and managing its spend rules.
Request
Must be user after a POST, to update individual spend rules associated with the managed card identified by the id path parameter.
Whitelist MCC: A list of allowed merchant category codes (MCCs). If the MCC does not match, then the transaction will be declined. If an MCC is also in the blocked list, the blocked list will take precedence.
Blacklist MCC: A list of disallowed merchant category codes (MCCs). If the MCC matches, then the transaction will be declined. If an MCC is also in the allowed list, the blocked list will take precedence.
Whitelist Merchant Id: A list of allowed merchant IDs. If the Merchant Id does not match, then the transaction will be declined. If a Merchant Id is also provided in the blocked list, the blocked list will take precedence.
Blacklist Merchant Id: A list of disallowed merchant IDs. If the Merchant Id matches, then the transaction will be declined. If a Merchant Id is also in the allowed list, the blocked list will take precedence.
Whitelist Merchant Country: A list of allowed merchant countries, in ISO 3166-1 alpha-2 format. If the Merchant country does not match, then the transaction will be declined. If a Merchant Country is also provided in the blocked list, the blocked list will take precedence.
Blacklist Merchant Country: A list of disallowed merchant countries, in ISO 3166-1 alpha-2 format. If the Merchant country matches, then the transaction will be declined. If a Merchant Country is also in the allowed list, the blocked list will take precedence.
Indicates if a cashback transaction at a physical terminal is allowed on the card.
The rollover policy will dictate how Weavr handles any eventual overspending. This is possible if a merchant clears more funds than authorised, or when a merchant clears funds without authorising, resulting in the availableToSpend value to go into negative. Rollover is relative to a spendLimit.interval
The total amount of funds that can be spent using this card, in a given time interval.
The minimum transaction amount, in card currency, that is allowed. If the transaction amount is less than this value, then the transaction will be declined.
The maximum transaction amount, in card currency, that is allowed. If the transaction amount is greater than this value, then the transaction will be declined.
The spend limit update method to apply. Currently supported:
- OVERWRITE: (default option if nothing selected). Overwrites the previous values for the spendLimit object i.e. sets new limits
- INCREMENT : This will increase the existing value of the spend limit by the amount input the value field. If used in conjunction with an ALWAYS interval, this can be used to increment a spend limit on a periodic basis (controlled by you, e.g. monthly), and means that any 'unused' balance from the previous period will still available to spend. See examples in our documentation
- Mock serverhttps://api.weavr.io/_mock/products/multi-backoffice/openapi/managed_cards/{id}/spend_rules
- Weavr Sandbox Environmenthttps://sandbox.weavr.io/multi/backoffice/managed_cards/{id}/spend_rules
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PATCH \
'https://api.weavr.io/_mock/products/multi-backoffice/openapi/managed_cards/{id}/spend_rules' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-H 'api-key: YOUR_API_KEY_HERE' \
-H 'idempotency-ref: string' \
-d '{
"allowedMerchantCategories": [
"string"
],
"blockedMerchantCategories": [
"string"
],
"allowedMerchantIds": [
"string"
],
"blockedMerchantIds": [
"string"
],
"allowedMerchantCountries": [
"st"
],
"blockedMerchantCountries": [
"st"
],
"allowContactless": true,
"allowAtm": true,
"allowECommerce": true,
"allowCashback": true,
"allowCreditAuthorisations": true,
"rolloverPolicy": {
"rolloverNegative": true
},
"spendLimit": [
{
"startTimestamp": 0,
"value": {
"currency": "str",
"amount": 0
},
"interval": "DAILY"
}
],
"minTransactionAmount": 0,
"maxTransactionAmount": 0,
"updateSpendLimitMethod": "OVERWRITE"
}'No content- Mock serverhttps://api.weavr.io/_mock/products/multi-backoffice/openapi/managed_cards/{id}/spend_rules
- Weavr Sandbox Environmenthttps://sandbox.weavr.io/multi/backoffice/managed_cards/{id}/spend_rules
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X DELETE \
'https://api.weavr.io/_mock/products/multi-backoffice/openapi/managed_cards/{id}/spend_rules' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'api-key: YOUR_API_KEY_HERE'No contentRequest
Returns a list of transactions against the managed card identified by the id path parameter, matching the criteria provided in the request.
The offset value for paging, indicating the initial item number to be returned from the data set satisfying the given criteria. Leave out to fetch the first page of results.
The limit of the results for paging, starting at the offset. Limit is always capped at 100.
Orders the result in ascending or descending order.
- ASC: Ascending order, oldest transactions first.
- DESC: Descending order, most recent transactions first.
If not specified, the transactions will be returned in descending order.
Filter for transactions having transaction timestamp after fromTimestamp. Timestamp is expressed in Epoch timestamp using millisecond precision. If omitted, all matching transactions up to the present will be included.
Filter for transactions having transaction timestamp before toTimestamp. Timestamp is expressed in Epoch timestamp using millisecond precision. If omitted, all matching transactions up to the present will be included. If both fromTimestamp and toTimestamp are provided, toTimestamp must be greater than fromTimestamp.
Returns transactions that span multiple movements as a single entry. Only includes transactions that have been completed. Defaults to true for PDF statements, false otherwise. Note: due to the fact that only completed transactions are included, some transactions that are in progress and have modified the balance of the instrument will not be shown, which could lead to seemingly inconsistent balance being displayed.
- Mock serverhttps://api.weavr.io/_mock/products/multi-backoffice/openapi/managed_cards/{id}/statement
- Weavr Sandbox Environmenthttps://sandbox.weavr.io/multi/backoffice/managed_cards/{id}/statement
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://api.weavr.io/_mock/products/multi-backoffice/openapi/managed_cards/{id}/statement?offset=0&limit=1&orderByTimestamp=ASC&fromTimestamp=0&toTimestamp=0&singleEntryPerTransaction=true&transactionType=INSTRUMENT_CREATE' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'accept: string' \
-H 'api-key: YOUR_API_KEY_HERE'- application/json
- application/pdf
- text/csv
{ "entry": [ { … } ], "count": 0, "responseCount": 0, "startBalance": { "currency": "str", "amount": 0 }, "endBalance": { "currency": "str", "amount": 0 }, "footer": "string" }