Overview

FlexFactor uses this data to generate a forecast report for your business. The report is built from your prior authorization declines, which allows FlexFactor to provide an estimated cure rate for your specific traffic.

Your data is uploaded through the FlexFactor portal. If you need portal access, request it from your Account Executive or submit a request to [email protected].

What data to include

This file should contain only the following:

Authorization declines that were NOT rescued during your existing dunning/recovery process
USD (US Dollar) and US entity traffic only
Visa/Mastercard traffic only — no digital wallets or Alternative Payment Methods (APMs)

If your export includes data outside this scope, that's OK — we will filter it out on our side.

How to submit your data

❗️
Before you send your file
Data can ONLY be submitted by logging into portal.flexfactor.io and navigating to the Files Center (max file size: 5 GB). The Document Center is for underwriting files only and has a 20 MB per-file limit — do not use it for forecast data.
Do NOT:

❌ Send files via email

❌ Send files via a download link

❌ Include any PII or PCI data — no emails, phone numbers, names, full card numbers, or any other personally identifiable or cardholder data

If a field in your export could contain sensitive information, mask it using SHA-256 hashing before sending. Files containing unmasked PII or PCI data will be rejected.

Send one row per declined transaction, straight from your processor export (.csv or .xlsx). More fields mean more precise cure rate projections.

For the purpose of a business case, two months of data will suffice.

Don't worry about exact column names — we handle the mapping. Export from Braintree, Adyen, Stripe, Chase, NMI, or any processor portal.

Fields

The required fields are the minimum we need, recommended fields give better projections, and optional fields add further precision if you have them.

Field	Type	Required	Description	Example
Decline Code	string	required	Raw decline/response code returned by the processor	`5`
Decline Reason	string	required	Human-readable decline reason from the processor	`Do not honor`
CIT/MIT	string	required	Whether the transaction was customer-initiated (CIT) or merchant-initiated (MIT)	`CIT`
Order ID	string	required *	Unique order/transaction identifier	`123456789`
Currency	string	required **	Currency code of the transaction amount	`USD`
TXN Date	datetime	recommended	Date/time of the transaction. Full timestamp preferred; date-only is acceptable	`01/01/2025`
TXN Type	string	recommended	Type of transaction	`Authorization`
Result	string	recommended	Result of the transaction	`Declined`
Amount	decimal	recommended	Transaction amount (USD, unless a Currency column is included)	`45.00`
Scheme	string	recommended	Card scheme	`Visa`
Card Type	string	recommended	Card type (credit or debit)	`Debit`
BIN	string	recommended	Bank identification number — the first 6 (or 8) digits of the card	`411111`
Issuer	string	recommended	Issuing bank of the card	`Wells Fargo`
PSP	string	optional	Payment service provider / gateway the transaction was processed through	`Stripe`
MID	string	optional	Merchant ID (MID) the transaction was processed under	`MID-001234`
MID Descriptor	string	optional	Billing descriptor associated with the MID	`ACME COMMERCE`
MCC	string	optional	Merchant category code (MCC) for the transaction	`5411`

* Order ID is needed only when duplicate retries exist, so retries of the same order can be grouped.

** Currency is required only if multiple currencies are present in the report.