πTransactions
Authorisation
Before a debit (payment) transaction is created, we usually receive an authorisation request from a payment network. We then either approve or reject the request based on various parameters, including customer and account statuses, on-chain balances etc. If authorisation is approved and authorised funds are claimed by the merchant, we proceed with creating a transaction entity.
Retrieving a Specific Authorisation
For the time being we only support retrieving an individual authorisation entity, however we will be expanding our API soon to support more endpoints.
To retrieve an individual authorisation, make a GET
request to /authorisations/{authorisationId}
.
Authorisation Entity Updates
Any internal updates to the authorisation entity will be reported through webhook update events. For details on how to set up and manage webhook subscriptions, please refer to Webhooks.
Transaction
Retrieving Transactions for a Specific Account or Card
To obtain a comprehensive list of transactions for a specific account or card, initiate a GET
request to the corresponding endpoint:
/accounts/{accountId}/transactions
for account transactions
/cards/{cardId}/transactions
for card transactions
Transaction Entity Updates
Any internal updates to the transaction entity will be reported through webhook update events. For details on how to set up and manage webhook subscriptions, please refer to Webhooks.
Retrieving a Specific Transaction
To retrieve detailed information about a specific transaction, make a GET
request to /transactions/{transactionId}
.
Last updated