Buyers are identities representing a business
Once on-boarded, Buyers can create payment runs and pay their suppliers in your application.
Weavr Payment Run Plug-in API provides a simple and flexible way for Embedders to add payment execution capabilities in their application.
By integrating Weavr Payment Run plug-in API in your application, you can embed banking and payment capabilities within your app to boost productivity for your users in a seamless experience.
Each request to the API must include an api_key that represents your account. You can obtain an API Key by registering for a Embedder account here.
Almost all endpoints require a secondary authentication token auth_token that represents the user for whom the request is being executed.
The collection makes use of environment variables to pre-fill details associated with your Sandbox account, such as your account’s API Key. You can download your Sandbox Account environment file from the Sandbox Portal.
A Payment run contains a list of supplier payments. A Payment run can be
CREATOR roleCONTROLLER roleCONTROLLER roleNote that the Controller user must have their mobile device enrolled to SCA.
Before a payment run can be executed, it must be funded. Users with the CONTROLLER role must link their company's bank account(s) that are represented as Linked Accounts, which than can be used as the funding source for a payment run.
Depending on the bank's constraints it may not be possible to deposit the total amount of funds required for a payment run, in which case the payment run will be automatically split into funding groups. All funding groups must be funded and executed for the payment run to be marked as completed.
Note that even if the payment is created successfully, you still need to check its status in order to determine if it is completed orfailed.
curl -i -X GET \
https://api.weavr.io/_mock/products/payment-run/openapi/v1/linked_accounts \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'api-key: YOUR_API_KEY_HERE'OK
The unique identifier of the linked account
The bank details that uniquely identify the account on the banking systems.
Bank details used in case the wire transfer is executed over Faster Payments.
Account number, required for wire transfer over Faster Payments.
Sort code, required for wire transfer over Faster Payments.
The primary currency associated with the account
The name to be used when displaying the institution to users on user interfaces
The institution's supported countries
The images that should be used when displaying the institution
The status of the linked account. The status can be one of the following:
PENDING_CHALLENGE: The Linked Account is pending challengePENDING_VERIFICATION: The Linked Account is pending the completion of the required verification stepsPENDING_FUNDING: Awaiting a wire transfer as part of the verification process when adding an account without Open BankingREJECTED: The Linked Account did not pass one or more verification steps and is not eligible for useLINKED: The linked account is linked and ready for useUNLINKED: The linked account is not linked and cannot be used{ "linkedAccounts": [ { … } ], "count": 0, "responseCount": 0 }
curl -i -X GET \
'https://api.weavr.io/_mock/products/payment-run/openapi/v1/linked_accounts/{linked_account_id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'api-key: YOUR_API_KEY_HERE'OK
The unique identifier of the linked account
The bank details that uniquely identify the account on the banking systems.
Bank details used in case the wire transfer is executed over Faster Payments.
Account number, required for wire transfer over Faster Payments.
Sort code, required for wire transfer over Faster Payments.
The name to be used when displaying the institution to users on user interfaces
The institution's supported countries
The status of the linked account. The status can be one of the following:
PENDING_CHALLENGE: The Linked Account is pending challengePENDING_VERIFICATION: The Linked Account is pending the completion of the required verification stepsPENDING_FUNDING: Awaiting a wire transfer as part of the verification process when adding an account without Open BankingREJECTED: The Linked Account did not pass one or more verification steps and is not eligible for useLINKED: The linked account is linked and ready for useUNLINKED: The linked account is not linked and cannot be used{ "id": "652d25b73541d8084a88a38d", "accountIdentification": { "accountNumber": "stringst", "sortCode": "string", "secondaryReference": "string" }, "currency": "GBP", "institution": { "displayName": "string", "countries": [ … ], "images": { … }, "info": { … } }, "consent": { "expiresAt": "2019-08-24T14:15:22Z", "expiresIn": 0, "status": "ACTIVE" }, "status": "LINKED", "friendlyName": "string" }
curl -i -X PATCH \
'https://api.weavr.io/_mock/products/payment-run/openapi/v1/linked_accounts/{linked_account_id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-H 'api-key: YOUR_API_KEY_HERE' \
-H 'idempotency-ref: string' \
-d '{
"friendlyName": "string"
}'OK
The unique identifier of the linked account
The bank details that uniquely identify the account on the banking systems.
Bank details used in case the wire transfer is executed over Faster Payments.
Account number, required for wire transfer over Faster Payments.
Sort code, required for wire transfer over Faster Payments.
The name to be used when displaying the institution to users on user interfaces
The institution's supported countries
The status of the linked account. The status can be one of the following:
PENDING_CHALLENGE: The Linked Account is pending challengePENDING_VERIFICATION: The Linked Account is pending the completion of the required verification stepsPENDING_FUNDING: Awaiting a wire transfer as part of the verification process when adding an account without Open BankingREJECTED: The Linked Account did not pass one or more verification steps and is not eligible for useLINKED: The linked account is linked and ready for useUNLINKED: The linked account is not linked and cannot be used{ "id": "652d25b73541d8084a88a38d", "accountIdentification": { "accountNumber": "stringst", "sortCode": "string", "secondaryReference": "string" }, "currency": "GBP", "institution": { "displayName": "string", "countries": [ … ], "images": { … }, "info": { … } }, "consent": { "expiresAt": "2019-08-24T14:15:22Z", "expiresIn": 0, "status": "ACTIVE" }, "status": "LINKED", "friendlyName": "string" }
Simulators enable you to trigger processes in Sandbox that in Production are triggered from an external action rather than from your application. this way you can test scenarios that otherwise you would only encounter in the Live environment.
Note: These endpoints are only available on Sandbox and won’t work in the Live environment.