Introduction

BR-DGE helps you streamline your payments processes by providing a single unified orchestration abstraction. BR-DGE is a platform for managing payments, allowing you to connect with multiple Payment Service Providers (PSPs), Alternative Payment Methods (APMs), Digital Wallets, and fraud services.

You will be able to use APIs to interact with different PSPs and payment services. Some examples of how you would use this are to:

Improve payment acceptance rates: If a payment does not succeed with one PSP, you can then redirect to the next PSP.
Route between different PSPs: Some PSPs are more favourable for different currencies or risk levels based on the industry or payment size.
Support all card schemes.
Support tokenization, including network tokenization.
Support 3-D Secure.
Assess Risk with Risk Engines.

Integrate

REST API

BR-DGE takes an API first approach, where we aim to make all features available via our REST API.

The BR-DGE REST API provides a standardised way for you to communicate with PSPs via BR-DGE and interact with various areas:

Payments: Use this section to collect money from your customers.
Payouts: Use this section to send money to your customers.
Orders: Use this section to create and manage orders for the BR-DGE Hosted Payment Page outlined below.
Payment Instrument Tokenization: Use this section to convert payment instruments (cards, Card on File) into tokens.

For more information and examples, see the BR-DGEs Rest API documentation.

BR-DGE SDKs

Our optional Software Development Kits (SDKs) provide a streamlined approach to leverage BR-DGE features and functionalities within your client applications. When electing to use a BR-DGE SDK or Hosted Payment Page you will still need to interact with the REST API from your server for all payment flows.

By incorporating a BR-DGE SDK, you gain access to a suite of valuable tools, including:

Hosted Fields: Securely collect and manage sensitive payment information without storing it on your servers.
Customizable UI Elements: Deliver a seamless payment experience that aligns perfectly with your application's design.
Automated Workflows: Streamline your payment process with pre-built automations for tasks like routing and risk management.
Built-in Documentation: Get clear and concise instructions right within the SDK, making development smoother.
Native Bindings to BR-DGE REST API: Enjoy a familiar development experience with easy-to-use code that interacts directly with BR-DGE's API.

For more information, see the BR-DGE SDKs documentation.

Hosted Payment Page

The BR-DGE Hosted Payment Page (HPP) will redirect your customers completely to our secure hosted page. BR-DGE captures and sends the payments, then redirects the customer back to your page when successful. When electing to use a BR-DGE SDK or Hosted Payment Page you will still need to interact with the REST API from your server for all payment flows.

By incorporating with the BR-DGE HPP, you will be able to:

Outsource cardholder data functions: You can outsource all your cardholder data functions to BR-DGE and qualify for PCI-DSS-SAQ-A which minimises your PCI compliance costs.
Reduce development costs: Once you have integrated with BR-DGEs Hosted Payment Page, configuration changes can be automatically applied by BR-DGE with minimal or no changes required to your integration.
Minimize code updates: BR-DGE can automatically push updates, configuration changes and new features to the BR-DGE HPP with zero or minimal changes to your integration with BR-DGE.

For more information, see the Hosted Payment Page documentation.

Vault

The BR-DGE Vault saves card details for the future. This allows your customers to not re-enter card details and also increases approval rates.

For more information, see the Vault documentation.

BR-DGE Portal

The BR-DGE Portal allows you to configure your payments.

Through the BR-DGE Portal interface, you can:

Get visibility on your transactions
Configure routing for your payments
Generate payment reports
Configure and create API Keys

For more information, see the BR-DGE Portal documentation.

Key Definitions

Some useful definitions for key terminology used throughout the integration documentation.

BR-DGE & Comcarde

Comcarde is our company name, and we initially developed BR-DGE with the same name. We are now rolling out the BR-DGE product name, but you will still see Comcarde used in domain and SDK names until the re-branding process is complete.

Merchant Account

You can have one or more accounts with us, each tailored to a specific use case you may have.

An account defines things such as:

The Payment Service Provider accounts you wish to use.
The rules for routing your payment.
The currencies you wish to support.
Which payment instruments and other features you have enabled.

Payment

A payment represents a request to transfer funds between accounts at banks or other financial institutions.

Payment Service Provider

A Payment Service Provider (PSP) offers merchants online services for accepting electronic payments by a variety of payment methods (payment instruments).

PSPs process payments via connections to acquiring banks and payment networks.

Payment Instrument

An electronic instrument with which end users of payment systems transfer funds between accounts at banks or other financial institutions.

3-D Secure

3-D Secure provides an additional layer of cardholder authentication when making electronic payments. Cardholders benefit from reduced risk of fraudulent activity on their account, and merchants benefit from fewer fraud-related chargebacks.

The original implementation (3-D Secure 1.0) added an extra layer of friction to the payment process, so to address these concerns 3-D Secure 2.0 was created, which introduced a frictionless flow and integrates better with smart devices for a smoother overall experience.

3-D Secure 2.0 satisfies the Strong Customer Authentication (SCA) requirements for European merchants transacting with European customers.

API Keys

You can generate API keys in the BR-DGE Portal.

The keys will be specific to a Merchant Account, Environment (Sandbox/Production), and grouped into two main classes based on how they will be used.

Server API Keys must only be used in your server, and never exposed to your client applications.
Client API Keys will be provided for use in client applications to support features such as BR-DGE Hosted Fields, Drop-In UI, 3-D Secure, etc.

👍
We recommend you don't embed API Keys in source code or binaries as this is a security risk and will make it harder for you to update your keys should we need to issue new ones.