Capture the initial decline and begin the recovery record while the subscription relationship is still fresh.
Sample CSV workflow
Learn Zahlen with the Four Retry Rule
The Zahlen sample CSV package lets a merchant see how failed subscription payments move through the canonical recovery cycle: Day 1, Day 2, Day 6, and Day 16. The files are PII-free training data, designed to show how Payment Intelligence turns ordinary payment events into retry timing, customer-contact guidance, and quick Recovery Intelligence insight.
Why the Four Retry Rule matters
A failed subscription payment should not immediately become a cancellation problem. Many declines are temporary, issuer-driven, timing-driven, or processor-response dependent. The Four Retry Rule gives the merchant a structured recovery path that is easy to understand and consistent enough to operate at scale.
Zahlen uses the Day 1, Day 2, Day 6, and Day 16 sequence to create a clear recovery window. Early retries preserve momentum while the customer is still active. Later retries create space for account funding, issuer state changes, and customer resolution. The final stage helps the business decide when to stop retrying and when customer contact becomes the better experience.
Submit the first fast retry for cases where the failure may have been temporary or timing-related.
Retry after a longer pause, giving customer funding and issuer conditions time to change.
Run the final retry decision and identify records where customer contact or stop-retry handling is appropriate.
The benefit for merchants
Instead of treating every decline the same, the merchant gets a repeatable recovery workflow that balances revenue recovery,
processor discipline, and customer satisfaction.
What is inside each 10,000-record CSV file
The ZIP contains four CSV files. Each file represents one stage of the retry sequence and includes 10,000 payment-event records. Together, the package gives a 40,000-record view of how a realistic merchant population can move through the Zahlen recovery lifecycle.
4CSV files
10,000records per file
40,000total payment events
16columns per record
01_day1_initial_decline_realistic_merchants.csvInitial decline records for Day 1.
02_day2_first_retry_realistic_merchants.csvFirst retry records for Day 2.
03_day6_second_retry_realistic_merchants.csvSecond retry records for Day 6.
04_day16_final_retry_realistic_merchants.csvFinal retry records for Day 16.
Shared schema
Each file uses the same column layout, so the merchant can upload the files consistently and compare recovery behavior across retry days without changing the data format.
order_idcustomer_idsubscription_idmerchant
merchant_idevent_timestampamountcurrency
bankbincountrycard_brand
response_codeauthorization_idauthorization_latency_msmerchant_category_code
How to upload the sample file
The upload process is intentionally simple. A merchant can begin with one file, review the results, and then upload the remaining retry-day files to see how the recovery picture changes as the sequence progresses.
Download the ZIP package.
Use the download link on this page and unzip the package on your computer.
Open the Zahlen Home page.
From the header or login flow, go to the main upload area where merchant CSV files are submitted.
Select one CSV file.
Start with the Day 1 file to establish the initial decline population, then continue with Day 2, Day 6, and Day 16.
Submit the upload and wait for processing.
Zahlen will process the file and make the resulting payment intelligence available for review.
Recommended learning path
Upload the files in retry order. That mirrors the real merchant journey and makes the Recovery Intelligence page easier
to understand as each retry day adds more evidence.
Go to Recovery Intelligence for quick insight
After the sample data is uploaded, the fastest way to understand what happened is to open the Recovery Intelligence page. That page is where the merchant can review retry status, payment status, response codes, contact-customer guidance, and the recovery state associated with each order.
Recovery Intelligence turns the CSV records into an operational view. Instead of reading thousands of rows manually, the merchant can quickly see which orders are still active, which retry stage they are in, and which records may require customer contact instead of another processor attempt.
Download the sample CSV package
Use the link below to download the complete four-file sample package. This is the same package referenced by the Zahlen sample workflow and can be used for demonstrations, onboarding, and recovery workflow education.
Download link
Zahlen_sample_csv_files.zip