Update details about existing payment.
Transaction ID provided by you which should be unique for each payment.
Your unique reference number for the specific operation. You can pass this value to reconcile different operations in a payment (authorization, capture, refund, etc) individually.
Intent of the updating the payment details.Note: Not all event tokens are applicable for all payment method types. Refer payment method specific pages in our product guide to know the relevant event tokens for a specific payment method.
- Testhttps://test.paymentpage.axepta.bnpparibas/api/v2/payments/{id}
- Productionhttps://paymentpage.axepta.bnpparibas/api/v2/payments/{id}
curl -i -X PATCH \
-u '<username>:<password>' \
'https://test.paymentpage.axepta.bnpparibas/api/v2/payments/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-H 'X-API-Key: YOUR_API_KEY_HERE' \
-d '{
"amount": {
"value": 1000,
"currency": "EUR"
},
"paymentMethods": {
"amazonPay": {
"merchantCountryCode": "EU"
}
}
}'Successful operation
A unique identifier assigned by Axepta Online to the payment. This ID remains constant throughout the lifecycle of the payment and is used to track and reference the payment across all subsequent operations, such as authorization, capture, refund, or cancellation.
A unique identifier assigned by Axepta Online for each operation in the payment. For example: xId will be different for the authorization and capture operations of a payment whereas payId will be same.
{ "merchantId": "test_merchant_id", "payId": "6c7c66e5352241c19d82c175a01f713a", "xId": "93c4093c6d3644fcb6c60484f7a831fd", "transId": "98582271-63d2-4b90-9422-5fb597a4c41d", "status": "OK", "responseCode": "00000000", "responseDescription": "success" }