Weavr Payment runs API
A Payment run contains a list of supplier payments. A Payment run can be - created by a user with a `CREATOR` role - confirmed by a user with a `CONTROLLER` role- funded by a user with a `CONTROLLER` 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` or`failed`.
Weavr Payment runs API is one of 43 APIs that Weavr publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Payment runs. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 10 operations across 8 paths. It is described by OpenAPI 3.1.0, at version v3.
Requests are made against a single base URL, https://sandbox.weavr.io/multi/backoffice.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Weavr Payment runs API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as api-key (api_key).
It accepts HTTP bearer tokens (JWT) (auth_token).
api_key— The API Key representing your Multi account.auth_token— The authentication token representing the user. This will be included in the login response object.
Paths & Operations 10
Across 8 paths, the API surfaces 10 operations — 3 GET, 5 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
A Payment run contains a list of supplier payments. A Payment run can be - created by a user with a CREATOR role - confirmed by a user with a CONTROLLER role - funded by a user wi…
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Weavr 12
Other APIs Weavr publishes across the network.