Manage authentication for your users.
Weavr Multi Product API (3.63.5)
Weavr Multi API provides a simple and flexible way to issue cards and accounts to your customers.
By integrating Weavr Multi API in your application you can embed banking capabilities within your app and provide a seamless experience for your customers.
Authentication
Each request to the Multi API must include an api-key that represents your account. You can obtain an API Key by registering for a Multi account here.
Almost all endpoints require a secondary authentication token auth_token that represents the user for whom the request is being executed.
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.
Managed accounts can also be used as source and destination instruments in the transfer and send transactions.
Managed Cards are a type of financial instrument offered by Weavr.
You can create virtual or physical cards that are issued to the consumer or corporate identity.
A card created in prepaid mode has its own balance, whereas a card created in debit mode does not have its own balance but taps into the balance of its parent managed account.
Linked Accounts are external bank accounts that users connect to their profiles within the Weavr Platform.
These accounts allow users to link their existing bank accounts, held at external financial institutions, to the Weavr Platform, enabling secure and efficient transfer of funds between their own accounts.
Linked Accounts are designed to streamline the process of moving money between a user’s various bank accounts, providing a convenient and integrated way to manage personal finances across different financial institutions.
A unique call reference included in every call, that enables the receiver to avoid duplicate handling of a webhook request (e.g. webhook was resent).
The timestamp, expressed in Epoch timestamp using millisecond precision, when this event was published.
The signature to verify the authenticity of this request. This is the base64 hash (HmacSHA256) of the call-ref + payload + published-timestamp using your API key.
The unique identifier of the linked account.
The profile Id which a specific identity, instrument or transaction type is linked to.
Profiles contain configuration and determine behavioral aspects of the newly created transaction, for example, fees that may apply.
You can have one or more profiles linked to your application, and these can be used to drive different behaviors according to your product's needs.
Profile Ids can be found in the Multi Portal, in the API Credentials page.
The tag field is a custom field that can be used to search and filter.
A user-friendly label assigned to the Linked Account to help end-users easily identify it within the application. This name can be updated at any time using the PATCH endpoint
The full name or corporate name of the account holder as registered with the external bank or payment service provider. This is the name under which the account is officially held.
An account can be of two types, Personal or Business:
- PERSONAL means that the account held at the external bank or PSP is registered under the ownership of a natural person or consumer identity;
- BUSINESS means that the account held at the external bank or PSP is registered under the ownership of a corporate entity.
The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.
The country of the bank or institution at which the account is held.
The IBAN or Account Number and Sort Code of the account held at the external bank or payment service provider.
Bank details
The state of the linked account:
- PENDING_VERIFICATION: The Linked Account is pending the completion of the required verification steps.
- ACTIVE: The Linked Account is verified and active, ready to be used for self-to-self wire transfers.
- BLOCKED: The Linked Account is temporarily blocked, preventing any use of this external account in self-to-self wire transfers. A Linked Account can be unblocked by calling the Multi API endpoint
POST /linked_accounts/{id}/unblock. - REMOVED: The Linked Account has been removed from the platform and can no longer be used for self-to-self wire transfers unless a new verification is completed in future.
- REJECTED: The Linked Account failed the verification process and cannot be used for self-to-self wire transfers unless a new verification is completed in future. A Linked Account can transition through these different overall states, starting at the
PENDING_VERIFICATIONstate until all verification steps are followed through.
The timestamp when the linked account was created, expressed in Epoch timestamp using millisecond precision.
The unique identifier of a Managed Account.
The profile Id which a specific identity, instrument or transaction type is linked to.
Profiles contain configuration and determine behavioral aspects of the newly created transaction, for example, fees that may apply.
You can have one or more profiles linked to your application, and these can be used to drive different behaviors according to your product's needs.
Profile Ids can be found in the Multi Portal, in the API Credentials page.
The tag field is a custom field that can be used to search and filter.
The friendly name given to the managed account.
The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.
Instruments with funds have 2 balances, the availableBalance indicating the funds that are available for transactions such as purchases, and the actualBalance indicating the funds that are actually on the instrument.
The funds available for transactions on the instrument. Funds that are blocked or pending are not included in the available balance.
The state of the instrument indicating what it can and cannot do as follows:
- ACTIVE: The instrument is in an active state and can be used in transactions.
- BLOCKED: The instrument is temporarily blocked and cannot be used. Any funds on the instrument are also frozen. The
blockedReasonprovides more information as to why it was blocked. - DESTROYED: The instrument has been permanently destroyed. The
destroyReasonprovides more information as to why it was destroyed.
The reason why the instrument has been blocked:
- USER: The root, or an authorised user, of the identity owning the instrument has temporarily blocked the instrument.
- SYSTEM: The platform or an administrator of the platform has temporarily blocked the instrument.
- LOST: The instrument has been blocked because it was marked as lost.
The reason why the instrument has been destroyed:
- SYSTEM: The platform or an administrator of the platform has destroyed the instrument.
- USER: The root, or an authorised user, of the identity owning the instrument has destroyed the instrument.
- LOST: The instrument was automatically destroyed as it was marked as lost.
- STOLEN: The instrument was automatically destroyed as it was marked as stolen.
- EXPIRED: The instrument was automatically destroyed as it expired.
- COMPROMISED: The instrument was automatically destroyed as it was marked as compromised.
The unique identifier of the Corporate Identity.
The profile Id which a specific identity, instrument or transaction type is linked to.
Profiles contain configuration and determine behavioral aspects of the newly created transaction, for example, fees that may apply.
You can have one or more profiles linked to your application, and these can be used to drive different behaviors according to your product's needs.
Profile Ids can be found in the Multi Portal, in the API Credentials page.
The tag field is a custom field that can be used to search and filter.
The root user of the Corporate Identity.
First name of the root user.
Last name of the root user.
E-mail Address of the user
The company position of the Corporate Root User.
The state of the root user. If false, then the user will not be able to log in.
Indicates if the root user's email has been verified.
Indicates if the root user's mobile number has been verified.
Date of birth of the authorised user.
The tag field is a custom field that can be used to search and filter.
The registered name of the company.
Supported company types - if company type is not listed, please contact our support team to check if the company type can be supported.
The company registration number.
The legal address of the company. This information is captured via the Due Diligence (KYB) process.
The address where the business is based.
Must be set to true to indicate that the root user has accepted the terms and conditions.
The IP address of the user doing the registration.
The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.
Fee groups allow the possibility to charge different fees to users under the same profile. If fee groups are not required, ignore this field.
The time when the Corporate was created, expressed in Epoch timestamp using millisecond precision.
Indicates the type of corporate entity based on its retail status.
The industry of the identity.
The corporate's source of funds.
The object representing a monetary amount in a particular currency.
The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.
- Mock serverhttps://api.weavr.io/_mock/products/multi/openapi/bank_transfers_in/authorisation_request
- Weavr Sandbox Environmenthttps://sandbox.weavr.io/multi/bank_transfers_in/authorisation_request
{ "id": "string", "source": { "instrument": { … } }, "destination": { "instrument": { … }, "owner": { … } }, "amount": { "currency": "str", "amount": 0 }, "timestamp": 0 }
{ "result": "APPROVED" }