Update a transaction

This service enables refund of transactions including fees.

​

Reversal of previously posted transaction

This use case allows to link reimbursement with previously posted transaction, including fees.

To create this type of refund please use POST “Update a Transaction” endpoint and as “id” parameter please provide id of the transaction which should be reversed, and in “propertyToUpdate” please provide “REVERSE” value. Id can be found with “Get transaction” endpoints under “id” parameter of transaction.

​

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