Unprocessable Content - The server understood the content type of the request, and the syntax of the request content was correct, but it was unable to process.
This scenario can occur when there was no PSP config setup for a payment to be routed to. It is not a bad request as it has passed gateway validation.
500
An internal server error occurred upstream while processing the request.
If you have any questions about why you are receiving these responses, please raise a ticket with support on the BR-DGE Support Portal at https://docs.br-dge.io/docs/support#contact-support with the ID from the response so we track down the individual requests on our end.
502
An error occurred upstream while processing the request, possibly on payment processor.
If have any questions about why you are receiving these responses, please raise a ticket with support on the BR-DGE Support Portal at https://docs.br-dge.io/docs/support#contact-support with the ID from the response so we track down the individual requests on our end.
Callbacks
Payment Status Change Events
post
https://example.com/BR-DGE/ as defined in your retail channel config
PSP Token Status Change Event
post
https://example.com/BR-DGE/ as defined in your retail channel config
PSP Token Provisioning Failed Event
post
https://example.com/BR-DGE/ as defined in your retail channel config
Network Token Provisioning Failed Event
post
https://example.com/BR-DGE/ as defined in your retail channel config
Network Token Status Change Event
post
https://example.com/BR-DGE/ as defined in your retail channel config
Network Token Metadata Update Event
post
https://example.com/BR-DGE/ as defined in your retail channel config
Payment Instrument Account Selection Event
post
https://example.com/BR-DGE/ as defined in your retail channel config
Updated about 2 months ago
Language
ShellNodeRubyPHPPython
Credentials
Bearer
Bearer
URL
Base URL
https://sandbox.comcarde.com/v1/payments
Loading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
201 - Successful payment201 - Successful payment with expanded rawPspResponse201 - Successful payment with included paymentInstrument201 - Successful payment with new Card on File created201 - Successful payment with installments plan successfully activated201 - Successful payment with pspToken and pspCardFingerPrint201 - Successful payment with riskAssessments201 - Successful payment with unavailable risk engine201 - Successful payment with included issuerResponse202 - Further action required to make 3D-Secure payment202 - Further action required to make 3-D Secure payment with new Card on File202 - Redirect Flow Action Response202 - Pending202 - Pending Skrill400 - Bad request with validation errors400 - Transaction declined due to risk engine's assessment409 - Duplicate merchantTransactionId provided422 - No PSP config to be routed to500 - Internal server error502 - Payment processor network error