Manage authentication for your users.
- Verify a list of resources using a one-time password
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.
Request
Starts the verification process for a list of resources in which a one-time password is sent to a device belonging to the logged-in user that was previously enrolled through the /authentication_factors/otp/{channel} endpoint.
This endpoint can be used to challenge Outgoing Wire Transfers, Sends, and Linked Account Declarations.
You should only start this process if the operation state is PENDING_CHALLENGE.
Note that on the Sandbox Environment, text messages are not sent and the one-time-password is always "123456".
The resource type that the subsequent Ids pertain to. Note that the linked_account_declaration can only be performed by a logged in Root User.
- Mock serverhttps://api.weavr.io/_mock/products/multi/openapi/challenges/otp/{channel}
- Weavr Sandbox Environmenthttps://sandbox.weavr.io/multi/challenges/otp/{channel}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
'https://api.weavr.io/_mock/products/multi/openapi/challenges/otp/{channel}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-H 'api-key: YOUR_API_KEY_HERE' \
-H 'idempotency-ref: string' \
-d '{
"resourceType": "outgoing_wire_transfers",
"resourceIds": [
"string"
]
}'{ "scaChallengeId": "string" }
Request
Completes the verification process for a list of resources.
This endpoint can be used to challenge Outgoing Wire Transfers & Sends.
If the outcome of the verification is successful, the resource is executed.
If not verified challenge expires after 5 minutes and the number of incorrect OTP attempts is limited to reduce the risk of fraud.
Note that on the Sandbox Environment, text messages are not sent and the verificationCode is always "123456".
- Mock serverhttps://api.weavr.io/_mock/products/multi/openapi/challenges/{scaChallengeId}/otp/{channel}/verify
- Weavr Sandbox Environmenthttps://sandbox.weavr.io/multi/challenges/{scaChallengeId}/otp/{channel}/verify
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
'https://api.weavr.io/_mock/products/multi/openapi/challenges/{scaChallengeId}/otp/{channel}/verify' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-H 'api-key: YOUR_API_KEY_HERE' \
-H 'idempotency-ref: string' \
-d '{
"verificationCode": "string",
"resourceType": "outgoing_wire_transfers"
}'No contentRequest
Starts the verification process for a list of resources in which a push notification is sent to a device belonging to the logged-in user that was previously enrolled through the /authentication_factors/push/{channel} endpoint.
This endpoint can be used to challenge Outgoing Wire Transfers & Sends.
You should only start this process if the resource state is PENDING_CHALLENGE.
- "AUTHY": The push notification is sent on the user's device using Twilio Authy
- "BIOMETRIC": The push notification is sent to the user's device
The resource type that the subsequent Ids pertain to. Note that the linked_account_declaration can only be performed by a logged in Root User.
- Mock serverhttps://api.weavr.io/_mock/products/multi/openapi/challenges/push/{channel}
- Weavr Sandbox Environmenthttps://sandbox.weavr.io/multi/challenges/push/{channel}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
'https://api.weavr.io/_mock/products/multi/openapi/challenges/push/{channel}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-H 'api-key: YOUR_API_KEY_HERE' \
-H 'idempotency-ref: string' \
-d '{
"resourceType": "outgoing_wire_transfers",
"resourceIds": [
"string"
]
}'{ "scaChallengeId": "string" }
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.