Skip to content

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.

Download OpenAPI description
Overview
Languages
Servers
Mock server
https://api.weavr.io/_mock/products/multi-backoffice/openapi
Weavr Sandbox Environment
https://sandbox.weavr.io/multi/backoffice

Access Token

Acquire a token granting you access to perform sensitive operations on behalf of an identity.

Operations

User Impersonation

Operations

Corporates

Operations

Charge fee to a corporateDeprecated

Request

Charge a fee to the corporate identified by the auth token, based on a pre-defined custom fee. Custom fees can be configured in the Multi Portal.

The fees collected will be deposited into your Revenue Account. The balance and transaction history of your revenue account can be viewed in the Multi Portal.

Security
auth_token and api_key
Headers
idempotency-refstring

A unique call reference generated by the caller that, taking into consideration the payload as well as the operation itself, helps avoid duplicate operations. Idempotency reference uniqueness is maintained for at least 24 hours.

Bodyapplication/jsonrequired
feeTypestringrequired

The fee type as defined in the Multi Portal.

sourceobject(InstrumentId)required

The instrument from where the fee should be deducted.

source.​idstring(Id)^[0-9]+$required
source.​typestring(InstrumentType)required
Enum"managed_cards""managed_accounts"
curl -i -X POST \
  https://api.weavr.io/_mock/products/multi-backoffice/openapi/corporates/fees/charge \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>' \
  -H 'Content-Type: application/json' \
  -H 'api-key: YOUR_API_KEY_HERE' \
  -H 'idempotency-ref: string' \
  -d '{
    "feeType": "string",
    "source": {
      "id": "string",
      "type": "managed_cards"
    }
  }'

Responses

Success

Headers
request-refstringrequired

A request identifier. Providing this reference when contacting our support team will help us investigate your query.

Bodyapplication/json
transactionIdobject(TransactionId)required

The unique identifier of the transaction.

transactionId.​typestringrequired
Enum ValueDescription
AUTHORISATION
SETTLEMENT
MANUAL_TRANSACTION

For a manual transaction, the additionalFields: note will contain a description with the reason for the transaction. This will start with one of the following prefixes:

  • Account Closure
  • Chargebacks - Represented
  • Chargebacks - Won
  • Deleted Card - Transfer from
  • Deleted Card - Transfer to
  • Duplicate Authorisation Issue
  • Duplicate Settlement Issue
  • Expired Card - Transfer from
  • Expired Card - Transfer to
  • Forex Padding Release Issue
  • Funds Redemption & Account Closure
  • Manual Auth Expiry
  • Missing Settlement Issue
  • Negative Card Balance
  • Reversal - Duplicate Transaction
  • Reversal - Manual Auth Expiry
  • Reversal - Manual Transaction
  • Amend Balance - Auth Expiry
  • Balance Adjustment
  • Completing Deposit
  • Duplicate Deposit
TRANSFER
SEND
DEPOSIT
AUTHORISATION_REVERSAL
AUTHORISATION_EXPIRY
AUTHORISATION_DECLINE
AUTHORISATION_MANUAL_CLOSE
transactionId.​idstring^[0-9]+$required
profileIdstringrequired

The profile Id which a specific identity, instrument or transaction type is linked to.

feeTypestringrequired

The fee type as defined in the Multi Portal, and as sent in the request.

sourceobject(InstrumentId)required
source.​idstring(Id)^[0-9]+$required
source.​typestring(InstrumentType)required
Enum"managed_cards""managed_accounts"
availableBalanceAdjustmentobject(CurrencyAmount)required

The object representing a monetary amount in a particular currency.

availableBalanceAdjustment.​currencystring(Currency)= 3 characters^[A-Z]*$required

The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.

availableBalanceAdjustment.​amountinteger(int64)required

The monetary amount, scaled to the lowest denomination of the currency.

Example, an amount of 1000 for a EUR currency is actually 1000 Euro cents or EUR 10.00.

statestring(TransactionState)required

The transaction entry state.

Enum"INITIALISED""COMPLETED""REJECTED""FAILED""PENDING""SCHEDULED""CANCELLED"
creationTimestampinteger(int64)required
Response
application/json
{ "transactionId": { "type": "AUTHORISATION", "id": "string" }, "profileId": "string", "feeType": "string", "source": { "id": "string", "type": "managed_cards" }, "availableBalanceAdjustment": { "currency": "str", "amount": 0 }, "state": "INITIALISED", "creationTimestamp": 0 }

Consumers

Operations

Authorised Users

Corporate and Consumer identities can invite authorised users to access their account. Once on-boarded, authorised users can create and manage instruments and transactions on behalf of the identity they are on-boarded with.
With the access_token representing the identity and the consent of the identity, you will be able to create and invite authorised users for the Identity.

Creating and inviting users on behalf of identities are restricted features; by default these endpoints are not available for use.

Operations

Managed Accounts

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.

Operations

Managed Cards

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.

Operations

Transfers

Operations

Fees

Operations

Operations

Operations

Manage

Operations