Paysafe

BR-DGE integrates directly with Paysafe, offering a powerful and flexible solution for online payment processing. This integration centralises your transactions within the BR-DGE platform, allowing you to fully leverage Paysafe's extensive capabilities.

The following tables detail the integration methods and transaction features currently supported through BR-DGE's connection with Paysafe.

If a desired Paysafe feature is not listed or supported, please contact our support team for assistance.

Integration methods

Paysafe is supported for merchants integrating with the following methods:

Payment types

The following transaction types are supported with Paysafe via BR-DGE:

** Please also refer to the additional information section below.

Payment instruments

The following Payment Instrument types are available with Paysafe via BR-DGE:

Additional information

Account funding transactions

BR-DGE supports Account Funding Transactions (AFTs) via Paysafe, enabling you to correctly identify and process payments that fund a non-merchant account, such as a wallet top-up or a person-to-person transfer.

To send an AFT to Paysafe via BR-DGE, include the aft object, along with the required sender and recipient fields, in your POST /v1/payments API request.

When using Paysafe with AFTs, note the following:

• Paysafe's own documentation: Paysafe Developer: Payments API – fundingTransaction schema
• Paysafe does not use a funding purpose.
• Paysafe does not use recipient.accountType — only recipient.accountNumber is passed through.
• Paysafe confirms in its response whether the payment was processed as an AFT; BR-DGE passes this confirmation back to you via the processedAsAft field.
• If an AFT is requested via Paysafe and it fails to meet certain criteria, the payment does not fallback and get processed as a standard purchase payment. However, if the requested fundingType is not applicable for your MCC, Paysafe defaults to the funding type set in your account configuration.

For more information on Account Funding Transactions, refer to our dedicated AFT guide.

Card Issuer Raw Responses

BR-DGE allows you to directly access the original responses from card issuers for payments processed through Paysafe using the include query parameter in the BR-DGE REST API Create a Payment endpoint.

Go to the Successful payment with included issuerResponse example response in our API reference documentation for an example of this.

Testing

Once enabled on your BR-DGE retail channels, you can begin testing Paysafe using their dedicated test cards and scenarios.

For a comprehensive overview of testing with Paysafe, visit their Testing pages.

Support

To enable Paysafe on your BR-DGE retail channels, please contact BR-DGE Support.