Alipay, China's leading third-party online payment solutionAlipay, China's leading third-party online payment solution

Settlement details report

The settlement detail report contains transaction settlement details for all transactions within a settlement period. The report is generated along with the settlement summary report on the next day after receiving the bank receipt for the settlement. You can obtain this report through the SFTP server or Antom Merchant Portal.

Report details

The settlement details report consists of three parts: header information, transaction details, and the end-of-file <END> that appears in the last line of the report. The header information is represented by parameter names, and the settlement details are represented by the corresponding values of the parameters.

The following table shows the parameters in the settlement details report and parameter descriptions:

Parameter

Description

settlementBatchId

MANDATORY String (64)

The unique ID that is assigned by the acquirer to identify a settlement period, which corresponds to the settlement batch number in the settlement summary parameter. If the acquirer does not assign settlementBatchId, Antom will generate this ID.

customerId

MANDATORY String (64)

The unique ID that is assigned by the acquirer to identify a merchant.

acquirer

MANDATORY String (64)

The name of the acquirer that processes the transactions.

The acquirer here specifically means the acquirer that provides acquiring and funds settlement services for the merchant.

acquirerReferenceNo

OPTIONAL String (64)

The unique ID assigned by the non-Antom acquirer for the transaction.

This parameter is specified when the transaction is settled by the non-Antom acquirer.

referenceMerchantId

OPTIONAL String (64)

The unique ID of the sub-merchant that directly provides services or goods to users, assigned by the primary merchant to its sub-merchant.

The value of this field needs to be the same as that of the referenceMerchantId field in the original payment or authorization request.

referenceStoreId

OPTIONAL String (64)

The unique ID of the store that belongs to the merchant, assigned by the primary merchant to its sub-merchant.

transactionId

MANDATORY String (64)

The unique ID that is assigned by Antom to identify a transaction. The value of this parameter follows these rules:

  • When transactionType is PAYMENT, CANCEL, AUTHORIZATION or PAYMENT_REVERSAL, the value of this parameter is identical to that of paymentId.
  • When transactionType is CAPTURE, the value of this parameter is identical to that of captureId.
  • When transactionType is REFUND, the value of this parameter is identical to that of refundId.
  • When transactionType is DISPUTE, the value of this parameter is identical to that of disputeId.

originalTransactionId

OPTIONAL String (64)

An identifier for the original transaction.

  • When transactionType is PAYMENT, CANCEL, or AUTHORIZATION, the value of this parameter is empty.
  • When transactionType is VOID, the value of this parameter is identical to paymentId of the original authorization.
  • When transactionType is REFUND, the value of this parameter is identical to paymentId of the original payment or authorization.
  • When transactionType is CAPTURE, the value of this parameter is identical to paymentId of the original authorization.
  • When transactionType is DISPUTE, the value of this parameter is identical to that of paymentId of the original authorization.
  • When transactionType is PAYMENT_REVERSAL, the value of this parameter is identical to that of paymentId of the original payment.

transactionRequestId

MANDATORY String (64)

The unique ID that is assigned by the merchant to identify a transaction request. The value of this parameter is identical to the value of paymentRequestId for a payment, or the value of refundRequestId for a refund.

When transactionType is DISPUTE, the value of this parameter is empty.

referenceTransactionId

OPTIONAL String (64)

The unique ID assigned by the merchant that directly provides services or goods to users, to identify a transaction. The value of this parameter is identical to that of referenceOrderId for a payment.

When transactionType is CANCEL, CAPTURE, or DISPUTE, the value of this parameter is empty.

paymentMethodType

MANDATORY String (64)

The payment method for processing the payment. See Payment methods to check the valid values.

The value of this parameter is identical to that of paymentMethodType in the original payment or authorization request.

pspName

OPTIONAL String (64)

The name of the Alipay+ Mobile Payment Provider, such as GCash.

The value of this parameter is identical to that of pspName in the original payment or authorization request.

transactionType

MANDATORY String

Transaction type. Possible values are:

  • PAYMENT: indicates a payment process.
  • REFUND: indicates a refund process.
  • CANCEL: indicates a cancellation process.
  • AUTHORIZATION: indicates an authorization process.
  • CAPTURE: indicates a capture process.
  • VOID: indicates a void authorization.
  • DISPUTE: indicates a dispute process.
  • REFUND_REVERSAL: indicates a reversed refund because the payment method is unable to correctly process the refund. The funds are returned to your account.
  • PAYMENT_REVERSAL: indicates the success of the payment.
  • SETTLEMENT_FEE: indicates the settlement fee charged by the acquirer. The fee details are represented by the settlementAmountValue and settlementCurrency parameters.
  • DISPUTE_REVERSAL: indicates a reversal of a successfully defended dispute.
  • COLLATERAL_WITHHOLDING: indicates the withholding of collateral funds.
  • RESERVE_WITHHOLDING: indicates the withholding of reserve funds.
  • RESERVE_RELEASE: indicates the release of reserve funds.
  • COLLATERAL_RELEASE: indicates the release of collateral funds.
  • RAPID_DISPUTE_RESOLUTION: indicates a dispute process with Rapid Dispute Resolution (RDR).

paymentTime

MANDATORY String (64)

The date and time when the corresponding transaction reaches a final status of success, in the format of YYYY-MM-DDTHH:MM:SS+hh:mm as defined in ISO 8601.

settlementTime

MANDATORY String (64)

The date and time when the settlement file is generated, in the format of YYYY-MM-DDTHH:MM:SS+hh:mm as defined in ISO 8601.

productCode

MANDATORY String

The type of payment product that is contracted between Antom and the merchant. Valid values are:

  • AGREEMENT_PAYMENT: indicates the auto debit payment.
  • CASHIER_PAYMENT: indicates the cashier payment.

The value of this parameter is identical to that of productCode in the original payment or authorization request.

transactionAmountValue

MANDATORY String (16)

The transaction amount in major units of the corresponding currency (For example, dollars for USD, and yen for JPY).

When the Interchange++ pricing model is used, the interchange fee charged by the issuing bank and the scheme fee charged by the card scheme may be charged in subsequent settlement batches, and the value of this field is 0 in this case.

transactionCurrency

MANDATORY String (3)

The currency of transactionAmountValue, specified by a 3-letter currency code as defined in ISO 4217.

settlementAmountValue

MANDATORY String (16)

The net settlement amount in major units of the corresponding currency (For example, dollars for USD, and yen for JPY).

When the acquirer is Hundsun and the value of summaryType is TOTAL, the value of this parameter is accurate. When the acquirer is Hundsun and the value of summaryType is other than TOTAL, the value of this parameter may be skewed. For more information about the error correction information, see Acquirer Hundsun.

settlementCurrency

MANDATORY String (3)

The currency of settlementAmountValue, specified by a 3-letter currency code as defined in ISO 4217.

quoteCurrencyPair

OPTIONAL String (16)

The currency pair of the settlement currency and the transaction currency, which is provided by the foreign exchange partner. The two currencies are separated with a slash and use a 3-letter ISO-4217 currency code, such as EUR/USD.

The value of this parameter is empty when the settlement currency is the same as the transaction currency.

quotePrice

OPTIONAL Decimal (20)

The quotation of the exchange rate between two currencies in the currency pair specified in the quoteCurrencyPair parameter.

The value of this parameter is empty when the settlement currency is the same as the transaction currency.

feeAmountValue

MANDATORY String (16)

The amount of the processing fee that is charged by the acquirer. The value of this parameter is in major units of the corresponding currency (For example, dollars for USD, and yen for JPY).

When the acquirer is Hundsun, the value of this parameter may be skewed. For more information about the error correction information, see Acquirer Hundsun and Sample 2.

When the acquirer is 2C2P and the Interchange++ pricing model is used, the value of this parameter may represent the error correction information. For more information about error correction information, see Interchange++ pricing model and Sample 3.

feeCurrency

MANDATORY String (3)

The currency of feeAmountValue, specified by a 3-letter currency code as defined in ISO 4217.

taxFeeAmountValue

OPTIONAL String (16)

The tax fee amount in major units of the corresponding currency (For example, dollars for USD, and yen for JPY).

When the acquirer is Hundsun, the value of this parameter may be skewed. For more information about the error correction information, see Acquirer Hundsun and Sample 2.

taxFeeCurrency

OPTIONAL String (3)

The currency of taxFeeAmountValue, specified by a 3-letter currency code as defined in ISO 4217.

processingFeeAmountValue

OPTIONAL String (16)

The amount of the processing fee that is charged for the payment processing services Antom provided for each transaction. The value of this parameter is in major units of the corresponding currency (For example, dollars for USD, and yen for JPY).

processingFeeCurrency

OPTIONAL String (3)

The currency of processingFeeAmountValue. The value of processingFeeCurrency is specified by a 3-letter currency code as defined in ISO 4217.

nonGuaranteeCouponValue

OPTIONAL String (16)

Merchant discount amount, which is not settled to the merchant. The value of this parameter is in major units of the corresponding currency (For example, dollars for USD, and yen for JPY).

nonGuaranteeCouponCurrency

OPTIONAL String (3)

The currency of nonGuaranteeCouponValue, specified by a 3-letter currency code as defined in ISO 4217.

disputeHandlingFee

OPTIONAL String (16)

The amount of the fee that is charged by Antom to the merchant for handling a dispute. The value of this parameter is in major units of the corresponding currency (For example, dollars for USD, and yen for JPY).

disputeHandlingFeeCurrency

OPTIONAL String (3)

The currency of disputeHandlingFee. The value of this parameter is specified by a 3-letter currency code as defined in ISO 4217.

disputeReverseFee

OPTIONAL String (16)

The amount of the reverse fee that is charged by Antom to the merchant. The value of this parameter is in major units of the corresponding currency (For example, dollars for USD, and yen for JPY).

This parameter is specified when the merchant does not agree with the dispute.

disputeReverseFeeCurrency

The currency of disputeReverseFee. The value of this parameter is specified by a 3-letter currency code as defined in ISO 4217.

originalTransactionRequestId

OPTIONAL String (64)

The original payment request ID of the transaction when the transaction type is REFUND, CANCEL, or CAPTURE. Otherwise, the value of this parameter is empty.

installmentsNum

OPTIONAL String (8)

Indicates the number of installment payments.

issuingCountry

OPTIONAL String (2)

The issuing country or region of the card. The parameter is a 2-letter country or region code that follows the ISO 3166 Country Codes standard.

This parameter is specified when paymentMethodType is CARD.

The value of this parameter is identical to that of issuingCountry in the original payment or authorization request.

cardBrand

OPTIONAL String (256)

The brand of the card.

This parameter is specified when paymentMethodType is CARD.

The value of this parameter is identical to that of cardBrand in the original payment or authorization request.

funding

OPTIONAL String (20)

The funding type of the payment method. This parameter is returned when the value of paymentMethodType is CARD, GRABPAY_MY, or GRABPAY_SG.

When the value of paymentMethodType is CARD, valid values are:

  • CREDIT: indicates a credit card payment.
  • DEBIT: indicates a debit card payment.

When the value of paymentMethodType is GRABPAY_MY or GRABPAY_SG, valid values are:

  • WALLETS: indicates a regular wallet payment using the wallet balance.
  • BNPL_POSTPAID: indicates a buy-now-pay-later payment, and the user pays the full amount.
  • BNPL_INSTALLMENT: indicates a buy-now-pay-later payment, and the user pays in installments.

The value of this parameter is identical to that of funding in the original payment or authorization request.

interchangeFeeAmountValue

OPTIONAL String (16)

The fee that is charged by the issuing bank. The value of this parameter has the following features:

  • In major units of the corresponding currency (For example, dollars for USD, and yen for JPY).
  • Accurate to eight decimal places in the settlement details report, and is rounded to two decimal places using Banker's rounding in the settlement summary report.

This parameter is specified when paymentMethodType is CARD and the Interchange++ pricing model is used.

interchangeFeeCurrency

OPTIONAL String (3)

The currency of interchangeFeeAmountValue, specified by a 3-letter currency code as defined in ISO 4217.

This parameter is specified when paymentMethodType is CARD and the Interchange++ pricing model is used.

schemeFeeAmountValue

OPTIONAL String (16)

The fee that is charged by the card scheme. The value of this parameter has the following features:

  • In major units of the corresponding currency (For example, dollars for USD, and yen for JPY).
  • Accurate to eight decimal places in the settlement details report, and is rounded to two decimal places using the banker's rounding in the settlement summary report.

This parameter is specified when paymentMethodType is CARD and the Interchange++ pricing model is used.

schemeFeeCurrency

OPTIONAL String (3)

The currency of schemeFeeAmountValue, specified by a 3-letter currency code as defined in ISO 4217.

This parameter is specified when paymentMethodType is CARD and the Interchange++ pricing model is used.

acquirerMarkupAmountValue

OPTIONAL String (16)

The fee that is charged by the acquirer. The value of this parameter is in major units of the corresponding currency (For example, dollars for USD, and yen for JPY).

This parameter is specified when paymentMethodType is CARD and the Interchange++ pricing model is used.

acquirerMarkupCurrency

OPTIONAL String (3)

The currency of acquirerMarkupAmountValue, specified by a 3-letter currency code as defined in ISO 4217.

This parameter is specified when paymentMethodType is CARD and the Interchange++ pricing model is used.

refundFeeAmountValue

OPTIONAL String (16)

The commission fee charged by the acquirer for a refund. The value of this parameter is in major units of the corresponding currency (For example, dollars for USD, and yen for JPY).

This parameter may be specified when the value of transactionType is REFUND.

refundFeeCurrency

OPTIONAL String (3)

The currency of refundFeeAmountValue, specified by a 3-letter currency code as defined in ISO 4217.

This parameter may be specified when the value of transactionType is REFUND.

region

OPTIONAL String (16)

The region where the transaction occurred. Valid values are:

  • DOMESTIC: domestic transactions, where the issuing country, acquiring country, and merchant registration country are the same.
  • INTRAREGIONAL: intraregional transactions, where the issuing country, acquiring country, and merchant registration country are different, but belong to the same region.
  • INTERREGIONAL: interregional transactions, where the issuing country, acquiring country, and merchant registration country are different, and do not belong to the same region.

Table 1. Parameters and descriptions in the settlement details report

Note: Use the header parameters to parse the transaction details report. The parameter order in the report downloaded from the SFTP server and Antom Merchant Portal may not match the parameter order displayed in Table 1.

Error correction information

The settlement report you obtained may contain the error correction information in the following scenarios.  

Acquirer: Hundsun

The acquirer Hundsun only provides the final settlement total amount. Therefore, Antom calculates the settlement details of each transaction for you. Due to the different calculation methods, the total settlement data calculated by Antom and Hundsun may be different, so Antom provides the error correction information about the amount calculation differences in the settlement report. The error correction information is displayed on the second-to-last line of the report and is represented by settlementAmountValue, feeAmountValue, and taxFeeAmountValue. For example:

  • If the total settlementAmountValue values calculated by Hundsun and Antom are respectively 37164 and 37140, the error correction information for settlementAmountValue is 24.
  • If the total feeAmountValue values calculated by Hundsun and Antom are respectively 760 and 760, the error correction information for feeAmountValue is 0.
  • If the total taxFeeAmountValue values calculated by Hundsun and Antom are respectively 76 and 100, the error correction information for taxFeeAmountValue is -24.

The final settlement amount to you is subject to the settlement amount provided by Hundsun. For information about the settlement report when the acquirer is Hundsun, see Sample 2.

Interchange++ pricing model

Interchange++ is a pricing model that consists of the fees charged by the relevant issuing bank, card scheme, and acquirer for processing every transaction. This pricing model is transparent because it offers the most detailed breakdown of the true costs. The Interchange++ pricing model includes the following three types of fees:

  • Interchange fee: The fee that is charged by the issuing bank.
  • Scheme fee (first+): The fee that is charged by the card scheme.
  • Acquirer fee (second+): The fee that is charged by the acquirer.

When the acquirer is 2C2P and the Interchange++ pricing model is used, the settlement reports may have error correction information. The error correction information represents the discrepancy between the fee that should be charged and the fee that is actually charged, and is presented on the second-to-last line through the feeAmountValue field of the settlement reports.

  • If the value of feeAmountValue is positive, it means the fee that should be charged is less than the fee that is actually charged, and the acquirer needs to pay you the discrepancy fee.
  • If the value of feeAmountValue is negative, it means the fee that should be charged is greater than the fee that is actually charged, and you need to pay the acquirer the discrepancy fee.

The acquirer sends the error correction information to Antom irregularly. Antom sends you the error correction information through the settlement reports.

In addition, under the Interchange++ pricing model, there may be a delay in the collection of Interchange++ fees. For example, for a transaction that happened on January 3, 2023, the interchange fee charged by the issuing bank was not settled in the same batch as other transactions, but the fee was charged in the next batch settlement. For more information about the settlement report that contains the error correction information under the Interchange++ pricing model, see Sample 3.

Report samples

The following samples show settlement details reports in different scenarios.

Sample 1 (Standard report)

On the transaction day of December 25, 2018, the merchant with an ID of 102218800000000**** had two transactions, one for a payment and the other for a refund. After Antom settled with you and you received the bank receipt, Antom generated a settlement details report in CSV. The details of the report are as follows:

copy
settlementBatchId,customerId,acquirer,acquirerReferenceNo,referenceMerchantId,referenceStoreId,transactionId,originalTransactionId,transactionRequestId,referenceTransactionId,paymentMethodType,pspName,transactionType,paymentTime,settlementTime,productCode,transactionAmountValue,transactionCurrency,settlementAmountValue,settlementCurrency,quoteCurrencyPair,quotePrice,feeAmountValue,feeCurrency,taxFeeAmountValue,taxFeeCurrency,processingFeeAmountValue,processingFeeCurrency,nonGuaranteeCouponValue,nonGuaranteeCouponCurrency,disputeHandlingFee,disputeHandlingFeeCurrency,disputeReverseFee,disputeReverseFeeCurrency,originalTransactionRequestId,installmentNum,issuingCountry,cardBrand,funding,interchangeFeeAmountValue,interchangeFeeCurrency,schemeFeeAmountValue,schemeFeeCurrency,acquirerMarkupAmountValue,acquirerMarkupCurrency,refundFeeAmountValue,refundFeeCurrency,region
201812261102104****,102218800000000****,Alipay_SG,,,,201812251907410100000000011****,,20190326L64842300****,,KAKAOPAY,KaKaoPay,PAYMENT,2018-12-25T10:00:00+08:30,2018-12-26T10:00:00+08:30,AGREEMENT_PAYMENT,18000,KRW,1450,USD,USD/KRW,1200,50,USD,,,,,,,,,,,,,,,,,,,,,,,,
201812261102104****,102218800000000****,Alipay_SG,,,,201812251907410200000000004****,201812251907410100000000011****,20190326L64842300****,,KAKAOPAY,KaKaoPay,REFUND,2018-12-25T10:00:00+08:30,2018-12-26T10:00:00+08:30,AGREEMENT_PAYMENT,-9000,KRW,-750,USD,USD/KRW,1200,0,USD,,,,,,,,,,,20190326L648423****,,,,,,,,,,,,,
<END>

📎Settlement details report-Sample 1.csv

In this example, transactions made in KRW need to be settled in USD, so the value of quoteCurrencyPair is USD/KRW. The exchange rate was 1 USD = 1200.0000 KRW, so the value of quotePrice value is 1200.0000.

  • Information about the payment:
    • transactionId: The transaction ID is 201812251907410100000000011****, which is the same as the value of paymentId in the original payment.
    • transactionAmountValue: The transaction amount is 18000 (KRW), which corresponds to 15.00 (USD). 
    • feeAmountValue: The processing fee charged by the acquirer is 0.50 (USD).
    • settlementAmountValue: The net settlement amount, which is the transaction amount minus fees. In this example, the value of this parameter is the value of transactionAmountValue minus the value of feeAmountValue, which is 14.50 (USD).
  • Information about the refund:
    • transactionId: The transaction ID is 201812251907410200000000004****, which is the same as the value of refundId in the original refund.
    • transactionAmountValue: The transaction amount is -9000 KRW, which corresponds to -7.50 (USD). That is, the refund amount is 7.5 USD.
    • settlementAmountValue: The net settlement amount, which is the transaction amount minus fees. In this example, the handling fee charged for the original payment is not returned in the refund, so the net settlement amount is -7.50 (USD). 

Sample 2 (Acquirer Hundsun)

The following settlement details report is an example of when the acquirer is Hundsun. The report includes eleven payments and one refund, as well as the error correction information on the second-to-last line. The settlement date for the transactions under this batch was October 30th, 2022. After Antom settled with you and you received the bank receipt, Antom generated a settlement details report in CSV. The details of the report are as follows:

copy
settlementBatchId,customerId,acquirer,acquirerReferenceNo,referenceMerchantId,referenceStoreId,transactionId,originalTransactionId,transactionRequestId,referenceTransactionId,paymentMethodType,pspName,transactionType,paymentTime,settlementTime,productCode,transactionAmountValue,transactionCurrency,settlementAmountValue,settlementCurrency,quoteCurrencyPair,quotePrice,feeAmountValue,feeCurrency,taxFeeAmountValue,taxFeeCurrency,processingFeeAmountValue,processingFeeCurrency,nonGuaranteeCouponValue,nonGuaranteeCouponCurrency,originalTransactionRequestId,issuingCountry,cardBrand,funding,interchangeFeeAmountValue,interchangeFeeCurrency,schemeFeeAmountValue,schemeFeeCurrency,acquirerMarkupAmountValue,acquirerMarkupCurrency,refundFeeAmountValue,refundFeeCurrency,region
202210190903110****,OB10****,Hundsun,J1PP2022101712312345****,OB022091****,,2022101719401089010011197028085****,,amsdmpay_20221017_113919_81****,,PAYPAY,,PAYMENT,2022-10-17T11:39:21+08:00,2022-10-30T23:00:00+08:00,CASHIER_PAYMENT,100,JPY,96,JPY,,,-4,JPY,0,JPY,,,,,,,,,,,,,,,,,
202210190903110****,OB10****,Hundsun,J1PF2022101717312345****,OB022091****,,2022101719401089010011180028089****,2022101719401089010011180028061****,amsdmrefund_20221017_163611_11****,amsdmpay_20221017_120214****,PAYPAY,,REFUND,2022-10-17T16:36:12+08:00,2022-10-30T23:00:00+08:00,CASHIER_PAYMENT,-100,JPY,-96,JPY,,,4,JPY,0,JPY,,,,,amsdmpay_20221017_120214_01****,,,,,,,,,,,,
202210190903110****,OB10****,Hundsun,J2PP2022101713021234****,OB022091****,,2022101719401089010011180028061****,,amsdmpay_20221017_120214_01****,,PAYPAY,,PAYMENT,2022-10-17T12:02:15+08:00,2022-10-30T23:00:00+08:00,CASHIER_PAYMENT,100,JPY,96,JPY,,,-4,JPY,0,JPY,,,,,,,,,,,,,,,,,
202210190903110****,OB11****,Hundsun,J3PP2022101713021234****,OB022092****,,2022101719401089010011180028062****,,amsdmpay_20221017_120214_02****,,PAYPAY,,PAYMENT,2022-10-17T12:02:16+08:00,2022-10-30T23:00:00+08:01,CASHIER_PAYMENT,100,JPY,96,JPY,,,-4,JPY,0,JPY,,,,,,,,,,,,,,,,,
202210190903110****,OB12****,Hundsun,J4PP2022101713021234****,OB022093****,,2022101719401089010011180028063****,,amsdmpay_20221017_120214_03****,,PAYPAY,,PAYMENT,2022-10-17T13:02:16+08:00,2022-10-30T23:00:00+08:02,CASHIER_PAYMENT,100,JPY,96,JPY,,,-4,JPY,0,JPY,,,,,,,,,,,,,,,,,
202210190903110****,OB13****,Hundsun,J5PP2022101713021234****,OB022094****,,2022101719401089010011180028064****,,amsdmpay_20221017_120214_04****,,PAYPAY,,PAYMENT,2022-10-17T13:07:18+08:00,2022-10-30T23:00:00+08:03,CASHIER_PAYMENT,100,JPY,96,JPY,,,-4,JPY,0,JPY,,,,,,,,,,,,,,,,,
202210190903110****,OB14****,Hundsun,J6PP2022101713021234****,OB022095****,,2022101719401089010011180028065****,,amsdmpay_20221017_120214_05****,,PAYPAY,,PAYMENT,2022-10-17T14:02:44+08:00,2022-10-30T23:00:00+08:04,CASHIER_PAYMENT,100,JPY,96,JPY,,,-4,JPY,0,JPY,,,,,,,,,,,,,,,,,
202210190903110****,OB15****,Hundsun,J7PP2022101713021234****,OB022096****,,2022101719401089010011180028066****,,amsdmpay_20221017_120214_06****,,PAYPAY,,PAYMENT,2022-10-17T14:25:46+08:00,2022-10-30T23:00:00+08:05,CASHIER_PAYMENT,100,JPY,96,JPY,,,-4,JPY,0,JPY,,,,,,,,,,,,,,,,,
202210190903110****,OB16****,Hundsun,J8PP2022101713021234****,OB022097****,,2022101719401089010011180028067****,,amsdmpay_20221017_120214_07****,,PAYPAY,,PAYMENT,2022-10-17T15:25:00+08:00,2022-10-30T23:00:00+08:06,CASHIER_PAYMENT,100,JPY,96,JPY,,,-4,JPY,0,JPY,,,,,,,,,,,,,,,,,
202210190903110****,OB17****,Hundsun,J9PP2022101713021234****,OB022098****,,2022101719401089010011180028068****,,amsdmpay_20221017_120214_08****,,PAYPAY,,PAYMENT,2022-10-17T16:37:00+08:00,2022-10-30T23:00:00+08:07,CASHIER_PAYMENT,100,JPY,96,JPY,,,-4,JPY,0,JPY,,,,,,,,,,,,,,,,,
202210190903110****,OB18****,Hundsun,J0PE2022101713021234****,OB022099****,,2022101719401089010011180028069****,,amsdmpay_20221017_120214_09****,,PAYPAY,,PAYMENT,2022-10-17T17:27:23+08:00,2022-10-30T23:00:00+08:08,CASHIER_PAYMENT,100,JPY,96,JPY,,,-4,JPY,0,JPY,,,,,,,,,,,,,,,,,
202210190903110****,OB19****,Hundsun,J0PJ2022101713021234****,OB022100****,,2022101719401089010011180028070****,,amsdmpay_20221017_120214_10****,,PAYPAY,,PAYMENT,2022-10-17T19:33:11+08:00,2022-10-30T23:00:00+08:09,CASHIER_PAYMENT,100,JPY,96,JPY,,,-4,JPY,0,JPY,,,,,,,,,,,,,,,,,
202210190903110****,OB10****,Hundsun,default,default,default,default,default,default,default,default,default,default,2022-10-30T23:00:00+08:00,2022-10-30T23:00:00+08:00,default,0,JPY,-4,JPY,,,0,JPY,-4,JPY,,,,,default,,,,,,,,,,,,
<END>

📎Settlement details report-Sample 2.csv

In this sample, the main information of the error correction information is as follows:

  • feeAmountValue (transactionType = default): 0
  • feeCurrency (transactionType = default): JPY
  • taxFeeAmountValue (transactionType = default): 3
  • taxFeeCurrency (transactionType = default): JPY
  • settlementAmountValue (transactionType = default): 3
  • settlementCurrency (transactionType = default): JPY

where, the values of feeAmountValue and taxFeeAmountValue are respectively 0 and 3. The total settlement amount after the calculation is three yen, with settlementAmountValue of 3 and settlementCurrency of JPY. This indicates that there is a difference of three yen in the settlement amount calculated by Hundsun and Antom.

Sample 3 (Interchange++ pricing model)

The following settlement details report is an example of when the Interchange++ pricing model is used. The settlement report contains four transactions that occurred on January 6, 2023, and the error correction information of previous transactions returned by the acquirer. The error correction information is displayed on the second-to-last line of the report.

copy
settlementBatchId,customerId,acquirer,acquirerReferenceNo,referenceMerchantId,referenceStoreId,transactionId,originalTransactionId,transactionRequestId,referenceTransactionId,paymentMethodType,pspName,transactionType,paymentTime,settlementTime,productCode,transactionAmountValue,transactionCurrency,settlementAmountValue,settlementCurrency,quoteCurrencyPair,quotePrice,feeAmountValue,feeCurrency,taxFeeAmountValue,taxFeeCurrency,processingFeeAmountValue,processingFeeCurrency,nonGuaranteeCouponValue,nonGuaranteeCouponCurrency,disputeHandlingFee, disputeHandlingFeeCurrency, disputeReverseFee, disputeReverseFeeCurrency,originalTransactionRequestId,installmentsNum,issuingCountry,cardBrand,funding,interchangeFeeAmountValue,interchangeFeeCurrency,schemeFeeAmountValue,schemeFeeCurrency,acquirerMarkupAmountValue,acquirerMarkupCurrency,refundFeeAmountValue,refundFeeCurrency,region
2C2PXXXXXX0101,Oxxxx742,2C2P_SG,2023XXXX000,,,2023XXXX0000,,request_id_2023XXXX_1111,reference_id_2023XXXX_5555,CARD,,AUTHORIZATION,2023-01-06T11:26:54+08:00,2023-01-09T02:45:29+08:00,CASHIER_PAYMENT,0,HKD,-3,HKD,,,,,,,-1,HKD,,,,,,,,,SG,VISA,CREDIT,,,-2,HKD,,,,,
2C2PXXXXXX0101,Oxxxx742,2C2P_SG,2023XXXX001,,,2023XXXX0011,2023XXXX0000,request_id_2023XXXX_2222,reference_id_2023XXXX_6666,CARD,,CAPTURE,2023-01-06T11:27:54+08:00,2023-01-09T02:45:29+08:00,CASHIER_PAYMENT,100,HKD,95,HKD,,,,,-1,HKD,-1,HKD,,,,,,,request_id_2023XXXX_1111,,SG,VISA,CREDIT,,,-2,HKD,-1,HKD,,,
2C2PXXXXXX0101,Oxxxx742,2C2P_SG,2023XXXX003,,,2023XXXX0033,2023XXXX0001,request_id_2023XXXX_3333,reference_id_2023XXXX_7777,CARD,,CAPTURE,2023-01-03T11:28:54+08:00,2023-01-09T02:45:29+08:00,CASHIER_PAYMENT,0,HKD,-4,HKD,,,,,,,,,,,,,,,request_id_2023XXXX_1112,,SG,VISA,CREDIT,-4,HKD,,,,,,,
2C2PXXXXXX0101,Oxxxx742,2C2P_SG,2023XXXX002,,,2023XXXX0022,2023XXXX0000,request_id_2023XXXX_4444,reference_id_2023XXXX_8888,CARD,,REFUND,2023-01-06T11:35:54+08:00,2023-01-09T02:45:29+08:00,CASHIER_PAYMENT,-100,HKD,-99,HKD,,,,,,,-1,HKD,,,,,,,request_id_2023XXXX_1111,,SG,VISA,CREDIT,4,HKD,-2,HKD,,,,,
2C2PXXXXXX0101,Oxxxx742,2C2P_SG,default,default,default,default,default,default,default,default,default,default,,2023-01-09T02:45:29+08:00,default,0,HKD,-500,HKD,,,-500,HKD,,,,,,,,,,,,,,,,,,,,,,,,
<END>

📎Settlement details report-sample 3.csv

In this example, for the capture that occurred on January 3, 2023, there is a supplementary charge of the fee that was charged by the issuing bank in this settlement batch. The value of interchangeFeeAmountValue is 4 and the value of interchangeFeeCurrency is HKD, which means that you need to pay an additional fee of 4 HKD to the issuing bank. It is noteworthy that the value of transactionAmountValue of this capture in this report is 0 because the transaction amount had already been settled in a previous batch. This batch settlement only involves the supplementary charge for the interchange fee of this capture.

The processing fee and currency in the error correction line are as follows:

  • feeAmountValue (summaryType = default): -500
  • feeCurrency (summaryType = default): SGD

where, the values of feeAmountValue and feeCurrency are -500 and SGD respectively, which indicates that you need to pay the acquirer an additional fee of 500 SGD.

Note: In the same settlement batch, the error correction amounts in the settlement details report and the settlement summary report are the same.

Sample 4 (No transaction)

copy
settlementBatchId,acquirer,customerId,acquirerReferenceNo,referenceMerchantId,referenceStoreId,transactionId,originalTransactionId,transactionRequestId,referenceTransactionId,paymentMethodType,pspName,transactionType,paymentTime,settlementTime,productCode,transactionAmountValue,transactionCurrency,settlementAmountValue,settlementCurrency,quoteCurrencyPair,quotePrice,feeAmountValue,feeCurrency,processingFeeAmountValue,processingFeeCurrency,nonGuaranteeCouponValue,nonGuaranteeCouponCurrency,originalTransactionRequestId,disputeHandlingFee,disputeHandlingFeeCurrency,disputeReverseFee,disputeReverseFeeCurrency,installmentNum,issuingCountry,cardBrand,funding,interchangeFeeAmountValue,interchangeFeeCurrency,schemeFeeAmountValue,schemeFeeCurrency,acquirerMarkupAmountValue,acquirerMarkupCurrency,refundFeeAmountValue,refundFeeCurrency,region
<END>

📎Settlement details report-Sample 4.csv

Note: When there is no transaction, the SFTP server and Antom Merchant Portal will not generate transaction details reports. If you need the empty report that has no transaction, you can contact Antom Merchant Service technical support (AlipayGlobalTechService@service.alipay.com)  to configure it in the SFTP server.