Volume per refund file description
The -volume-per-refund.csv
file includes a detail-level report of all refunds across all boarded merchants within a given settlement period. This is delivered every day when the settlement has been made along with the other 7 describing that settlement period.
The naming convention is:
<merchant number>-<frequency>-<year>-<ongoing number>-<suffix>.csv
Example: 1-999-W-2016-07-volume-per-refund.csv
The file will contain the following data:
Column | Description | Type |
---|---|---|
MERCHANT_TX_ID | An optional merchant-provided identifier for the refund[a-zA-Z0-9.,-_]{1,40} | string |
RF_ID | A PPRO-provided identifier for refund | numeric |
PAYMENT_REFERENCE | The public identifier of the refund | string |
EVENT_TYPE | The event type specifies the transaction event which triggers a fund movement. See the table below for details of each event type | string |
EVENT_TIMESTAMP | ISO_8601 UTC timestamp (format YYYY-MM-DDThh:mm:ssZ ) of the event | string |
MERCHANT_ID | Contract ID identifying each unique merchant as provided by PPRO upon onboarding | string |
PAYMENT_METHOD | Name of the payment method (e.g. “SEPA Direct Debit”)[a-zA-Z0-9]{1,40} | string |
AMOUNT | The refund amount | numeric |
CURRENCY | 3-digit ISO currency code describing the amount | string |
COUNTRY | 2-digit ISO country code describing the origin of the payment | string |
REFERENCE_TX_ID | TX_ID of the original transaction of this refund | numeric |
EVENT_TYPE Description
EVENT_TYPE | Description |
---|---|
SUCCEEDED | A transaction in a technical successful state. Assumed OK if it never becomes FUNDSREJECTED |
FUNDSREJECTED | Status shown in the event PPRO is unable to push funds to a consumer. Example: the consumer closed their bank account |
Important
When files are delivered in the SFTP, they will be zipped in a gzip format (*.gz). Please ensure that your system can extract gz files before processing.
Updated 10 months ago