Contents
Affirm is making enhancements to settlement reporting and will be rolling out enhancements in the coming months. If you have not received communication regarding updated settlement reporting, please visit the Reading and reconciling your settlement reports: Legacy reporting page. Please reach out to merchantcare@affirm.com or your account representative directly with any questions.
Reading your settlement report
If you choose to receive your settlement reports via email or by SFTP, you will receive a detailed report file (.csv) by default, and a summary file upon request. The summary report provides totals for a quick snapshot of performance, while the detailed report breaks down each individual event, offering a comprehensive view of all activities.
Opening up a detailed report may resemble the example below:
Example report columns
Example columns cont'd
For your reference, you can download a sample settlement report here.
Standard settlement reports feature a variety of details, with the format column being particularly beneficial for developers seeking greater control over the data. The data will be presented in the report following the specified column order, and opting out of optional columns will not alter this sequence.
Note: Any optional fields currently configured will remain available in your settlement report. Additional default fields listed below will be appended to your current configuration. Please refer to our Legacy Settlement Reporting page for more details.
If you have additional needs not represented in this report, please contact our Merchant Care team at merchanthelp@affirm.com
| Name | Example | Format | Description |
| date | 2023-03-14 | String | The date that the settlement was disbursed. |
| charge_created_date | 2023-01-27 | String | The date that the specific transaction event took place or loan creation date. |
| charge_id | 0WFN-6CD5 | String (9 alphanumeric characters) | Affirm's persistent transaction identifier. The Charge ID remains even after you refund a charge. |
| transaction_id | S6oeY2fC8dUHCw | String (16 alphanumeric characters) | An Affirm generated unique value is created for each charge transaction. Capturing a charge and then voiding the charge will create 2 different Transaction IDs. |
| order_id | ST153631529 | String (128 alphanumeric characters maximum) |
Merchant generated identifiers are typically used in their own internal system to track the order. This is an optional value that you provide in the checkout object. Note:
|
| event_type |
loan_captured loan_refunded |
String |
This is the current state of the charge. Possible values are:
|
| sales |
543.15 0.0 |
Float (USD dollars) |
This is the amount of the sales transaction and may be positive or zero. When you capture the loan or win a dispute, “sales” is the positive value of that transaction. When a customer opens a dispute, “sales” is zero and the negative value of that transaction is reflected under “refunds.” Note: If the transaction is settled through a card network, sales will be 0, and original_loan_amount can be referenced to confirm the purchase amount. |
| refunds | -1185.4 | Float (USD dollars) | This is the amount of the refund and may be a negative value or zero. When you refund a loan, “refunds” are the negative value of the refund. In all other cases, “refunds” are zero. |
| fees | -216.98 | Float (USD dollars) | This is the fee that Affirm charges for this transaction and may be positive or negative. When you capture a loan or a dispute is resolved in your favor, refundable fees will be a negative value. If you refund a loan or if a customer opens a dispute, refundable fees are a positive value. |
| total_settled | 3067.26 | Float (USD dollars) | This is the total amount deposited into your bank account. It is the sum of all “sales”, “refunds”, “fees”, and “txn_fees”. This value can either be positive or negative. |
|
txn_fees If applicable, this field will be required |
-0.3 | Float (USD dollars) | This is a transaction fee that is charged by Affirm for processing a loan (Not to be confused with “fees” as this is charged outside of that). |
| deposit_id |
THRWFW92 E2PSZYH |
String (15 alphanumeric characters) | Affirm assigns this random string related to a single deposit to every charge in a settlement. Each charge with the same “deposit_id” was deposited on the same day. For any given day you’ll have a “deposit_id” per lending partner that was involved in a charge for that day. |
| merchant_ari | AYNHPZKHX9E0VOKX | String | Unique identifier of the merchant. |
| city | IRVING | String | Store’s city where the order was made, obtained directly from card rails (externally controlled). |
| store | SOLSTICE.COM | String | Store’s name where the order was made, obtained directly from card rails (externally controlled). |
| card_last_four | 1392 | String | Last four digits of the payment instrument (FPAN). |
| original_loan_amount | 4342.26 | Float (USD dollars) | Original order total. |
| mdr_rate | 0.049900 | Float (Percentage) | Fee (in percentage) for the given transaction. |
| channel | Affirm Direct | String |
Channel where an Affirm checkout was initiated. Possible values are:
|
|
dispute_fee Optional |
-15.0 0.0 |
Float (USD dollars) | Flat dispute fee for each disputed transaction where Affirm needs to adjudicate the case and the merchant is at fault. |
Reconciling your settlements
For straightforward reconciliation, you have the option to filter out or hide additional information, allowing you to focus on key fields such as ‘total_settled’ and ‘channel’.
Example report columns
Example columns cont'd.
- The ‘date’ of the settlement file is the date Affirm initiated the ACH transfer to your bank account, which is a different date than when the charge was processed.
- Take the sum of all the amounts in the ‘total_settled’ column that have the same Deposit ID. This sum should equal the amount of a deposit made into your bank account. You may have multiple deposits each day (one per lending partner).
- If you provide Affirm with an Order ID at checkout, we will echo it in your settlement file. Take the sum of all the amounts with the same ‘order_id’ across different reports to calculate the final state of that order.
- Use the ‘channel’ column to note the sales channel of a given transaction. For example, Affirm Direct (POS), Google Pay, Affirm Card, etc.
- For Digital Wallets and Affirm Card transactions, we suggest using the following fields to support your reconciliation: ‘charge_created_date’, ‘city’, ‘store’, ‘card_last_four’, ’original_loan_amount’
- Note: ‘card_last_four’ displays the FPAN suffix. This corresponds to digital wallet data emitted at time of checkout.
- Important: Affirm will settle fees associated with Digital Wallets and Affirm Card transactions in this report; total sales on these channels will be settled via your payment processors.
- For Digital Wallets and Affirm Card transactions, we suggest using the following fields to support your reconciliation: ‘charge_created_date’, ‘city’, ‘store’, ‘card_last_four’, ’original_loan_amount’