Generic Fee Reimbursement transaction types

For this case reimbursement is not linked to specific charged fee and amount of reimbursement should be provided. Generic reimbursement transaction types can be used to reimburse one or several fees.

There is a possibility to create reimbursement on account or on card level.

To create reimbursement on account level please POST transaction to given account with “AR” as type parameter.

To create reimbursement on card level please POST transaction to given card with “RR” as type parameter.

On account level there also supported interest reimbursement transactions with “IR” and “OR” types.


Idempotent Requests

Endpoints in this section support idempotency, which means that you can safely submit identical requests without making changes to the data storage twice. To perform an idempotent request, provide x-idempotency-key header with the request.

Idempotency works by saving URL, method and idempotency header of your request as a key and the result of the request as value for 24 hours.

In case an error occurs while processing the request, the error message will be persisted and resent on possible retries. Please note that the uuid and timestamp fields of the error will be regenerated to be able to track down the identity of each error.

Idempotency key needs to be a unique value generated by the client which the server then uses to activate the feature to be able to recognize possible future retries of the same request. The maximum length of the idempotency key is 64 characters.

Endpoints