We have added customerOrderCode and merchantTransactionId to payment notifications.
We have added reference and merchantTransactionId to payout notifications.
CustomerOrderCode is your own code provided to reference a transaction on BR-DGE portal.
MerchantTransactionId is a unique identifier provided by you upon initial transaction.
Additional Information
For more detailed information and examples, please refer to the complete API documentation.
If you have any further questions, please contact customer support.
We have added new custom metadata fields for Payments and Payouts
Custom metadata allows you to include additional information with each transaction, giving you more flexibility and
control over your payment processing. You will soon be able to define your own routing rules based on this metadata, optimizing payment
processing and improving customer satisfaction.
We have added merchantTransactionId to the request and response of the POST /payments endpoint. This is your unique
identifier for the API request that can be used when a connection issue occurs, and you don't receive a paymentId. We
will validate the uniqueness of the merchantTransactionId value per retail channel. If a payment/payout/refund is
created with merchantTransactionId abc, no other payment/payout/refund can be created with abc. If this happens we
will return an HTTP Status 409 Conflict with a 4701 response code.
The merchantTransactionId is a contract between BR-DGE and a merchant. This field will not be mapped downstream to any
PSP.
We have also added a new GET payments endpoint to our API which requires a merchantTransactionId as a query parameter,
this endpoint will return a payment in a list structure. If no payment can be found relating to this
merchantTransactionId, we will return an HTTP Status 200 and an empty list.