AISP and PISP access
The API functionality exposes details of the request accounts, their balances, bookings and transactions and it includes Accounts, Payments, Fees, and FX. This data can be accessed by licensed Account Information Service Providers and Payment Initiation Service Providers by providing a valid certificate and credentials.
To get onboarded as AISP or PISP, you’ll have to provide our Sales team with your company name, username, email address, phone number, IP address that will be used for sending requests to us, and Qualified Certificate (QSEAL). Get in touch with us here.
Unique request ID
We have implemented a RequestID Uniqueness Check. This means that if you are an AISP or a PISP you need to send a unique ID with each call. The request header must contain a unique X-Request-ID for each request. If the X-Request-ID is found not to be unique, a 400 Bad Request Inavalid X-Request-ID is returned.
Connecting to our APIs as an AISP and PISP
To get the access token, AISPs and PISPs should include in the Authorization call these headers:
| Header | Description |
|---|---|
| Authorization | HTTP Basic Authentication (username and password) |
| X-ARR-ClientCert or X-BC-ClientCert | AISP or PISP QSEAL Type Certificate |
For sending requests, the following headers need to be included in all API calls:
| Header | Description |
|---|---|
| X-Request-ID (Unique): Mandatory | ID of the request (in UUID format), unique to the call (generated by the initiating party, who must ensure uniqueness) |
| Digest | Base64 encoded hash of body (SHA-256 and SHA-512 supported). Use an empty string if there is no body. |
| Digest | Comma separated list of values for keyId, algorithm, headers and signature:
|
| TPP-Signature-Certificate | Base64 encoded Qualified Certificate (QSEAL) used for signing |
| PSU-ID: Optional | Payment Service User ID. If PSU-ID is specified as part of the Signature headers, it must be specified in the Request header |
AISP access
As an AISP, you will be able to make the following calls:
Accounts
| Endpoints | Supported HTTP Method |
|---|---|
| /api/v1/accounts | GET |
| /api/v1/accounts/{account-id} | GET |
| /api/v1/accounts/{account-id}/balances | GET |
| /api/v1/accounts/{account-id}/bookiengs | GET |
Fees
| Endpoints | Supported HTTP Method |
|---|---|
| /api/v1/fees | GET |
| /api/v1/fees/{fees-id} | GET |
FX
| Endpoints | Supported HTTP Method |
|---|---|
| /api/v1/fx | GET |
| /api/v1/fx/{foreign-exchange-id} | GET |
Payments
| Endpoints | Supported HTTP Method |
|---|---|
| /api/v1/payments/bulks | GET |
| /api/v1/payments/bulks/{payment-bulk-id} | GET |
| /api/v1/payments/bulks/{payment-bulk-id}/status | GET |
| /api/v1/payments/singles | GET |
| /api/v1/payments/singles/{payment-id} | GET |
| /api/v1/payments/singles/{payment-id}/status | GET |
PISP access
As an PISP, you will be able to make the following calls:
Payments
| Endpoints | Supported HTTP Method |
|---|---|
| /api/v1/payments/single | POST |
FX
| Endpoints | Supported HTTP Method |
|---|---|
| /api/v1/fx/instant | POST |
| /api/v1/fx/rates/{sell-currency}/{buy-currency} | GET |