Riverty Consolidated Electronic Payment Advice
For reconciliation purposes, specifically designed for Partner’s integrations, we provide you with a Consolidated Electronic Payment Advice (C-EPA). Format and structure wise, C-EPA is identical to standard EPA. Unlike standard EPA, C-EPA can contain transactions of multiple merchants which are operating under the same partner umbrella. Also, header of C-EPA will contain total settlement amount towards partner, for all merchants belonging to that respective partner.
The C-EPA file contains Comma-Separated Values (CSV) with payment information that occurred during the Settlement Period.
The C-EPA file format can be used in a single- or multicurrency environment. The C-EPA format consists of two main elements:
- Header: contains consolidated information of the specific C-EPA file.
- Transactions: details on single or multiple lines with transaction information.
With intermittent rounding to 2 decimals, the total amount of all transaction Total Settlement Amount added up might not equal the Total Settlement Amount. The Total Settlement Amount mentioned in the C-EPA header should always equal the amount actually transferred to the bank account. The individual line items are rounded to 2 decimals.
Consolidated EPA Header
The header is the first row in the CSV file, presenting summed amounts and general information. Example:
The header is the first line within an C-EPA file and always starts with ‘H’ (for Header). Table one below describes the other variables in the header and their format.
|record_type||String (1)||Constant string with ‘H’ for Header|
|payout_currency||String (3)||The settlement currency in ISO 4217, all caps. Example: “EUR”|
|total_sale_amount||Integer||The total sale amount. Example: 99988877 for EUR 999888,7711|
|total_fee_amount||Integer||The total fee amount, service fees charged by After Pay. Example: 499944 for EUR 4999,4411|
|total_VAT_amount||Integer||The total VAT amount, related to After Pay fees. Example: 104988 for EUR 1049,8811|
|total_refund_amount||Integer||The total refund amount, presenting returns by the customer. Example: 33322 for EUR 333,2111|
|total_chargeback_amount||Integer||The total chargeback amount, presenting disputes, where merchant is obliged to refund the customer (e.g. Fraud or goods not delivered). Example: 22211 for EUR 222,111|
|total_holdback_amount||Integer||The total holdback amount, presenting the amount that After Pay is holding back. Reason for holdback is merchant surpassing credit limit amount. Example: 22211 for EUR 222,111|
|total_release_amount||Integer||The total release amount, presenting the amount that After Pay is releasing, which was previously held back due to the credit limit. Example: 22211 for EUR 222,111|
|previous_settlement_balance||Integer||Previous settlement balance. Relevant for reconciliation, especially if previous payout was negative or delayed. Example: 99988877 for EUR 999888,7711|
|previous_payout||Integer||The total payout amount in the previous payout cycle. Example: 99988877 for EUR 999888,7711|
|total_settlement_amount||Integer||The total settlement amount. Calculated in following way: total_sale_amount - total_fee_amount - total_VAT_amount - total_refund_amount - total_chargeback_amount - total_holdback_amount + total_release_amount.
Example: 99988877 for EUR 999888,7711
|number_of_transactions||Integer||The total number of transactions settled in this batch. Example: 2511|
|payment_reference||Integer||The total sale amount. Example: 99988877 for EUR 999888,7711|
|payout_date||YYYYMMDD||The date of the payout. Example: 20221125|
|merchant_settlement_type||String||NET - After Pay fees are deducted from the payout.
GROSS - Full amount is transferred to the merchant, fees are deducted with the next payout
|bank_account||String||The bank account in IBAN format of the merchant to be used for pay out. Example: NL15ABNA01234567|
Consolidated EPA Transactions
Directly below the header line are the transactions. Every line corresponds with one single transaction. The amount of transactions in the C-EPA file is depicted in the C-EPA header. Example:
Transaction records within an C-EPA file always starts with ‘D’ (for Detail). The table below describes the other variables in the transaction records and their format.
|record_type||String (1)||Constant string with ‘D’ for Details|
|type||String||SALE - captured order
REFUND - returned order
FEE - service fees charged by After Pay
CHARGEBACK - disputes, where merchant is obliged to refund the customer (e.g. Fraud or goods not delivered)
VAT - VAT related to After Pay fees
OTHER - other types that are not covered by any above listed
|MID||String||The Merchant ID Example: 2019888111|
|transaction_date||YYYYMMDD||The capture, refund or any other type date of the transaction event. Example: 20221125|
|amount||Integer||The original transaction amount, with two digits in the fractional part but no decimal point. Example: 29950 for EUR 299.50|
|currency||String||ISO 4217, all caps. Example: “EUR”|
|order_no||String||Order Number related to the transaction. Example: OFS400019761|
|transaction_no||String||Invoice Number (captures) or Credit Note Number (refunds). Example: 7915236894369412A601122|
|transaction_reference||String||If filled and passed by merchant, we will present it here. Otherwise, this field will be empty (null value)|
|parent_transaction_reference||String||The Parent Transaction Reference may be passed by the Payment Service Provider during through the authorization or capture calls. If passed, we will present it here. Otherwise, this field will be empty (null value)|
Naming Structure / Convention