merchant_reference |
Merchant |
A reference for the merchant to identify the payment.
The merchant_reference is stored in the Brite system and helps you to search or relate the payment based on ids from your system.
Example: "Order ID: ABC-123" |
✅ |
❌ |
POST /api/session.get |
session_id |
Brite |
agfsfsfdb251123yASbv123RyFVANtclcRubvys1123phrx12310a |
✅ |
❌ |
POST /api/session.get |
| Session ID (or key) as a number |
Brite |
421700102 |
❌ |
✅ ** |
Brite client at the bottom ("ID: 421700102") |
transaction_id |
Brite |
agfsfsfdb251123yJSMEDcELEgticaFuc2FvdslghyBDA |
✅ |
❌ |
POST /api/session.get
POST /api/transaction.get |
customer_id |
Brite |
agfsfsfdb251123yJSMEDcALEgndoWab11cryBDA |
✅ |
❌ |
When session.state >= 2:
POST /api/session.get
POST /api/transaction.get |
merchant_id |
Brite |
agfsfsfdb251123ySbwYMTkFgJ5ZE11cnkwY6G3CAjDTd4eBDA |
✅ |
❌ |
Callback notifications |
bank_account_id |
Brite |
agfsfsfdb251123yY7mY6G45cx50mUbeY2hvdv6DAGcoyake5uDA |
✅ |
❌ |
POST /api/bank_account.create
POST /api/session.get
POST /api/transaction.get |
message |
Brite |
This is what is commonly referred to as the bank statement reference visible to the customer in their online banking.
Example: RF5282XX2 |
✅ |
✅ * |
POST /api/transaction.get |
statement_reference |
Merchant |
Brite attempts to send both, the message and the statement_reference to the bank for it to be set as the bank statement reference. However, not all banks support such long references and as a result Brite omits it where it causes issues.
Example: "order-id - abc-123" |
✅ |
⚠️ * (not in all cases) |
POST /api/transaction.get |
