Transaction event reports let you track every tranasction event you've processed with Bango.
Bango creates daily, weekly, and monthly reports grouped by merchant. Bango can make these available to you by email or SFTP upload. You can use these reports for reconciliation purposes.
Reports are published within 24 hours of the end of the reporting period.
| Report | Frequency | Description |
|---|---|---|
| Event report | Daily, weekly, monthly | All transaction events during the reporting period (One transaction may appear several times). This report includes cancellation and refund events. |
Filenames have the format:
{type}_V1_{frequency}_{date}.csvWhere:
ERfor the Event reportM for monthlyW for weeklyD for dailyYYYYMM, for example 202008 for August 2020YYYYMMDD, for example 20200817 for August 17, 2020For example:
ER_V1_W_20200810.csv is the Event report for the week commencing August 10, 2020ER_V1_M_202009.csv is the Event report for September 2020All report files are Windows-1252 encoded and contain RFC 4180-compliant comma-separated values (CSV).
Here's an example transaction report:
MasterTransactionId,TransactionId,EventTimestamp,TransactionType,BillingIdentifier,UserId,OperatorTransactionId,MerchantTransactionId,MerchantAccountKey,SubmerchantReferenceKey,Status,OperatorStatus,GrossAmount,TaxAmount,CurrencyIso3,ItemName,ItemDescription,ItemCategory,ExtraInformation
2006721250,993483290434,"2018-09-19T16:49:03Z",Auth,"Customer1",1531214765,"OperatorId1","MerchantId1","BANGO",FUNDS_RESERVED,OK,,1.23,0.00,"GBP","In-App1","In app content 1","Gaming",
2006721260,993445435435,"2018-09-19T16:49:03Z",Charge,"Customer2",1531263015,"OperatorId2","MerchantId2","BANGO",OK,OK,,1.23,0.00,"GBP","In-App2","In app content 2","Software",
2006721270,993443434254,"2018-09-19T16:49:03Z",Refund,"Customer3",1531214765,"OperatorId3","MerchantId3","BANGO",OK,OK,,1.23,0.00,"GBP","In-App3","In app content 3","Music",| Column name | Type | Description |
|---|---|---|
MasterTransactionId | String | The global unique transaction identifier assigned by the Bango Platform |
TransactionId | String | The unique identifier assigned by the Bango Platform for individual request that caused the event |
EventTimestamp | String | ISO 8601 UTC timestamp for when the transaction event started (for example, when the payment was authorized). |
TransactionType | String | The type of event: Auth, Charge, Cancel, Refund, Partial_Refund, Partial_Cancel |
BillingIdentifier | String | The billable identifier for the user making the purchase |
UserId | String | The customer's globally unique, anonymous Bango ID |
OperatorTransactionId | String | Your own unique transaction identifier, if you provided one |
MerchantTransactionId | String | The merchant's own unique transaction identifier, if they have provided one |
MerchantAccountKey | String | The merchant's unique identifier in the Bango Platform |
SubmerchantAccountKey | String | The merchant's sub merchant unique identifier in the Bango Platform |
Status | String | The status of the transaction as a result of the event |
OperatorStatus | String | The operators status of the transaction as a result of the event |
GrossAmount | Decimal | The transaction amount in the specified currency, with two decimal digits For example, a payment of GBP 1.23 this column contains 1.23 |
CurrencyIso3 | String | The three-character ISO 4217 currency code (for example, GBP) |
ItemName | String | The name of the content which the user has purchased, passed by the merchant |
ItemDescription | String | The description of the content which the user has purchased, passed by the merchant |
ItemCategory | String | The category of the content which the user has purchased, passed by the merchant |
ExtraInformationFormat | String | Format of the ExtraInformation column |
ExtraInformation | XML serialised to string | Extra information stored by the Bango platform when communicating with the operators systems |
The transaction report shows the current status for every transaction. These are the possible status values:
| Status | Description |
|---|---|
OK | The transaction was successfully processed |
REJECTED | The payment provider declined the payment |
ERROR | An error occurred on the payment provider system while processing the transaction |
AUTHORIZING | The first step of the two-step transaction is currently being processed |
FUNDS_RESERVED | The first step of the two-step transaction was processed successfully – funds have been reserved |
CANCELLED | The first step of the two-step transaction was canceled – reserved funds have been freed |
USER_SUSPENDED | The user account was suspended on the payment provider system |
USER_NOT_ENABLED | The user account was not enabled for payments on the payment provider system |
USER_SPEND_LIMIT | The user account reached its spend limit on the payment provider system |
USER_BARRED | The user account was barred on the payment provider system |
CONNECT_ERROR | There was a connection error to the payment provider system |
DECLINED | The payment provider declined the transaction request |
USER_INVALID | The payment provider didn't recognize the user |
USER_NOT_FOUND | The user account didn't exist on the payment provider system |
DATA_INVALID | The request included invalid data (for example, a negative price) |
USER_INSUFFICIENT_CREDIT | The user did not have enough credit |
INTERNAL_ERROR | An error occurred on the Bango Platform while processing the transaction |
INVALID_PIN | The supplied PIN was incorrect (some payment providers require the user to input a PIN for the transaction to complete) |
RESERVATION_EXPIRED | The first step of the two-step transaction expired – reserved funds have been freed |
PRICE_NOT_SUPPORTED | The amount sent by the merchant was not a permitted value |
BANGO_USER_BARRED | The user account was barred on the Bango Platform |
NOT_SUPPORTED | The attempted operation was not supported by the payment provider |
DATA_MISSING | The request was missing data (for example, missing parameters) |
USER_EXCEEDED_LIMIT | The user account reached its spend limit on the Bango Platform |
OPERATOR_SPEED_LIMIT | The payment provider declined the transaction because the user account was attempting transactions too frequently |