Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

User can rerun any existing transaction at any time which has been failed earlier. Authenticate this request using HTTP Basic Auth by adding a bearer token to the header, e.g. Authentication: Bearer {{access_token}}. You can get the {{access_token}} from the create token request.

If the previous transaction had the following values for transaction_type, SALE or PREAUTH, then both fields amount and transaction_unique are optional, if they are not entered, then it should use the amount and transaction_unique from the previous transaction.

If the previous transaction  had “VERIFY” as transaction_type, then amount field is required.

Resources



Rerun Transactions

POST /pay/v1/transactions/{transaction_id}/reruns

Headers

Content-Type string
Content type.

Authorization string
Access token generated from create token request.

Attributes

amount float
Transaction amount.

transaction_unique string
Transaction unique.

Request

  • No labels