Receiving data about all your attempted payments
Transaction reports let you track every attempted payment you've processed using the Bango Payment API. (This report excludes refunds.)
By default, Bango generates a monthly report including all attempted payments for that month, with their current status. Bango can make reports available to you by email or SFTP upload. Reports use RFC 4180 CSV format.
Here's an example transaction report:
MasterTransactionId,StartDate,UserId,MerchantTransactionId,Status,AmountDecimal,Currency
2006721250,"2018-09-19T16:49:03Z",1531214765,"MerchantId1","OK",0.1,"GBP"
2006721260,"2018-09-19T16:49:03Z",1531263015,"MerchantId2","DECLINED",0.2,"GBP"
2006721280,"2018-09-19T16:49:04Z",1531214765,"MerchantId3","OK",0.1,"GBP"
2006721270,"2018-09-19T16:49:04Z",1531214765,"MerchantId4","OK",2.1,"GBP"
2006721290,"2018-09-19T16:49:04Z",1531214765,"MerchantId5","OK",0.5,"GBP"| Column name | Description |
|---|---|
MasterTransactionId | (number) The globally unique transaction identifier assigned by the Bango Platform |
StartDate | (ISO 8601 timestamp string) When the payment transaction started (for example, when the payment was authorized) |
UserId | (number) The customer's globally unique, anonymous Bango ID |
MerchantTransactionId | (string) Your own unique transaction identifier, if you provided one |
Status | (string) The current status of the transaction (see below) |
AmountDecimal | (decimal) The transaction amount in the specified currency, with two decimal digits. For example, for a payment of GBP 1.23 this column contains 1.23 |
Currency | (string) The three-character ISO 4217 currency code (for example, GBP). For the list of supported codes, see ISO 4217 Currency Codes |
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 |
In this section: