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

Version 1 Next »

User can cancel any existing transaction before being settled. It can only be performed on transactions, which have been authorised but not yet settled. 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 is in “Captured" state, then that transaction can be cancelled.

Resources

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


Cancel Transactions

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

Headers

Content-Type string
Content type.

Authorization string
Access token generated from create token request.

Attributes

note string (optional)
Cancellation note (if any).

Request

POST https://secure.blinkpayment.co.uk/api/pay/v1/transactions/BL-2349AGB/cancels HTTP/1.1
Content-Type: application/json
Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbG...

{
    "note": "cancel note"
}

Response

HTTP/1.1 200 OK
Content-Type: application/json

{
    "success": true,
    "message": "Cancelled successfully",
    "amount" : "1.01",
    "note": "cancel note",
    "transaction_id": "BL-2349AGB"
}
  • No labels