BR-DGE Portal
The BR-DGE Portal allows you, as a merchant, 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.
Access
To get set up with the BR-DGE Portal, please get in contact with support.
To log into the BR-DGE Portal, use the links below:
- Sandbox Environment: https://sandbox.portal.br-dge.io/login.
- Production Environment: https://secure.portal.br-dge.io/login.
| Role | Access |
|---|---|
admin | Dashboard Transactions Issue a Refund Reporting Smart Routing Configuration |
reader | Dashboard Transactions Reporting |
If you are part of multiple organizations you will be able to choose your organization after you log in.
Dashboard
In the Dashboard section of the sidebar, you can view successful (authorised) payments for various periods for your retail channels. The drop-down at the top of the sidebar signifies the retail channel you want to filter by.
Transaction Details
The Transaction Details section provides an overview of payment transactions, including their status, amount, processing details, and associated identifiers. Below is a breakdown of each field and its description.
| Field Name | Description |
|---|---|
| Customer Name | The name of the customer who initiated the transaction. |
| Status | The current status of the transaction (e.g., Approved, Rejected, Pending). |
| Amount | The total transaction amount, including currency (e.g., 752.63 EUR). |
| Time (UTC) | The date and time when the transaction occurred, in Coordinated Universal Time (UTC). |
| Order Code | A unique identifier assigned to the transaction for tracking purposes. |
| BR-DGE Response Code | A response code provided by BR-DGE indicating the reason for the transaction’s success or failure. |
| Gateway Payment Id | A unique identifier assigned by the payment gateway. |
| Merchant Advice Code | Additional guidance provided to the merchant regarding the transaction. |
| Acquirer | The financial institution or bank that processes the payment on behalf of the merchant. |
| Customer Email | The email address associated with the customer who initiated the transaction. |
| Transaction Type | Specifies the nature of the transaction, such as "Payment" or "Refund." |
| Processor | The payment service provider used to process the transaction (e.g., Stripe). |
| Payment Method | The payment method used by the customer, such as a credit card or digital wallet. |
| BR-DGE Payment Id | A unique identifier assigned by BR-DGE to track the transaction. |
| Issuing Bank | The bank that issued the customer’s payment card. |
| Issuer Payment Method | The specific payment method associated with the issuing bank. |
| Issuer Card Type | The type of card used in the transaction (e.g. Visa, Mastercard). |
| Card Category | Additional classification of the card, such as "Business" or "Personal". |
Any missing or unavailable data fields will be displayed as "-".
Transaction History
The Transaction History section provides a detailed record of all events associated with the transaction, including responses from the payment provider and BR-DGE. Below is a breakdown of each field within this section:
| Field Name | Description |
|---|---|
| Order | A sequential number indicating the order of transaction events. |
| Processor | The payment service provider used to process the transaction (e.g., Stripe). |
| Processor Response Code | The response code returned by the payment provider, indicating the outcome or status of the transaction. |
| BR-DGE Response Code | A response code provided by BR-DGE indicating the reason for the transaction’s success or failure. |
| Processor Transaction ID | A unique identifier assigned by the payment provider for tracking the transaction. |
| Time (UTC) | The date and time when the transaction occurred, in Coordinated Universal Time (UTC) format. |
Each entry in the Transaction History table represents a distinct event or update related to the transaction, allowing users to track its progress and status over time.
Any missing or unavailable data fields will be displayed as "-".
Issue a Refund
To issue a refund in the BR-DGE Portal, click on a particular transaction and click the Refund button.
The Refund button functionality is only available for those with admin permissions, it will not be usable for users with other access types, or if the transaction is already fully refunded, pending or not captured.
Reporting
In the Reporting section of the sidebar, you can generate reports on your transactions per retail channel. The drop-down at the top of the sidebar signifies the retail channel you want to report. When you make a report it will add other details, for example, an alternative payment method (APM)-initiated flag and PSP Transaction ID.
Smart Routing
In the Smart Routing section of the sidebar, you can set rules to direct your transactions to the appropriate payment processor. Smart routing allows you to decide how your payments are routed. Helping you increase the approval rate of your transactions, and giving you more control over your payments.
You can select which Retail Channel you'd like to configure the Smart Routing rules for via the drop-down at the top of the sidebar. The currently selected Retail Channel will be visible when the drop down is not expanded.
Processor Priority
In the Processor Priority tab of Smart Routing, you can use drag-and-drop functionality to prioritise payment processors per retail channel.
BIN Metadata
In the BIN Metadata tab of Smart Routing, you can configure and combine multiple trigger conditions in order to route payments to different payment processors.
A BIN Metadata rule will be comprised of one, or a combination of, the following trigger conditions.
- Issuer
- Network
- Funding source
- Country
- Currency
You can add one or more matches to each trigger condition, e.g. the
Currencytrigger could be matched against bothGBP&EURmeaning the payment will be routed by this rule when either of those currencies is returned in the BIN metadata
Volume
In the Volume tab of Smart Routing, you can input percentages per payment processors to divide up the flow of your transactions. These are per retail channel and all the inputted percentages across your PSPs must add up to 100%.
Monetary
In the Monetary tab of Smart Routing, you can configure different Amounts and Currencies to be routed to your different payment processors.
Configuration
API Keys
In the BR-DGE API Keys section of Configuration, you can create, revoke or rotate API Keys.
When you click the Create Key button, you can create both Client Keys and Server Keys for the chosen retail channel and describe the key. The drop-down at the top of the sidebar signifies the retail channel you want to configure API Keys for.
When you create a new API Key you will be shown it once, we recommend that you copy and save it securely straight away.
For any created keys, you can click the Revoke button to revoke access.
Updated 9 days ago