curl --request POST \
--url https://api.dev.ecos.gcservices.io/payments/payment-order/v1/payments/{externalReferenceNo}/cancel \
--header 'Content-Type: application/json' \
--data '
{
"identification": "XYZ1234567890",
"uetr": "AB1234567890CDEF1234567890ABCDEF",
"etoeIdentification": "1234567890abcdef1234567890abcdef",
"cancellationType": "SINGLE_PAYMENT_INSTANCE",
"noOfInstances": "7"
}
'{
"reasonDescription": "Account number invalid or does not exist",
"reasonCode": "AC01",
"status": "failure"
}Cancels an existing payment.
curl --request POST \
--url https://api.dev.ecos.gcservices.io/payments/payment-order/v1/payments/{externalReferenceNo}/cancel \
--header 'Content-Type: application/json' \
--data '
{
"identification": "XYZ1234567890",
"uetr": "AB1234567890CDEF1234567890ABCDEF",
"etoeIdentification": "1234567890abcdef1234567890abcdef",
"cancellationType": "SINGLE_PAYMENT_INSTANCE",
"noOfInstances": "7"
}
'{
"reasonDescription": "Account number invalid or does not exist",
"reasonCode": "AC01",
"status": "failure"
}Idempotent Request Key.
Timestamp.
Type of the payment.
Payment transaction ID.
An identifier that allows to uniquely refer to a payment transaction.
"XYZ1234567890"
Universally unique identifier to provide an end-to-end reference of a payment transaction.
"AB1234567890CDEF1234567890ABCDEF"
Unique identification assigned by the initiating party to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.
"1234567890abcdef1234567890abcdef"
Defines the the cancellation type that user wants can be anything from single to multiple instances
SINGLE_PAYMENT_INSTANCE, MULTIPLE_PAYMENT_INSTANCE, COMPLETE_SCHEDULE Relevant in case user wants to cancel multiple upcoming payments.
"7"
OK.
The status of the transaction.
"failure"
Reason code that connecting system accepted/rejected the payment.
"AC01"
Human readable reason the core banking system accepted/rejected the payment or batch.
"Account number invalid or does not exist"