Power Your Software Testing with AI Agents and Cloud
The Native AI-Agentic Cloud Platform to Supercharge Quality Engineering. Test Intelligently and Ship Faster.
- TestMu AI (Formerly LambdaTest)
- /
- Use Cases
- /
- Test a pay in four schedule shown before confirming
Test a pay in four schedule shown before confirming
Four dates, four amounts and a stated zero interest, all visible before the shopper commits to anything.
Published on:
Buy now pay later is a credit agreement presented as a checkout option. The schedule a shopper is shown before confirming is the disclosure that makes it legal in most markets, not a design flourish.
This use case runs the pay in four path on the Klarnah checkout and asserts the whole schedule before the confirm button.
The checks that matter
The schedule has four dates and four amounts, and a test that checks only the total misses the errors that actually reach a shopper.
| What is shown | What the test asserts |
|---|---|
| Approval state | A badge reading approved for four interest-free payments |
| Each instalment | Four payments of $45.00 on four specific dates, fortnightly |
| The total | $180.00, matching the order |
| The cost of credit | Interest of $0.00, stated rather than implied |
Asserting the interest line explicitly is worth the extra clause. Zero interest is the entire product claim, and a schedule that adds a fee while the four payments still sum correctly is a different agreement than the one advertised.
Note: Asserting every date and amount in one instruction keeps a regulated disclosure covered without turning the file into twelve separate steps. Start on TestMu AI. Start for free
The flow as a test file
The eligibility check uses a specific last four digits, which is what determines the approval outcome. A different value produces a decline, which is covered by its own file.
---
mode: testing
url: https://my-testing-repo-main.vercel.app/klarna-clone-app/checkout?reset=true
max_steps: 45
tags: [klarna, payments, bnpl]
---
# Klarnah 14.1: Pay in 4
Catalog objective: choose Klarnah at checkout and complete the pay-in-4 signup.
Key assertion: the instalment schedule is shown before confirming.
## Choose Klarnah
Verify the page subtitle reads "Studio Lamps · $180.00" and "Pay in 4 with Klarnah" is selected.
## Complete the quick check
Type "Priya Nair" into "Full name", type "4417" into "Last 4 of ID number", set "Date of birth" to "1992-04-18", and click "Continue with Klarnah".
## Verify the schedule appears before you confirm
Verify a badge reads "Approved - 4 interest-free payments" and the schedule table shows four payments of "$45.00" due "2026-09-15", "2026-09-29", "2026-10-13" and "2026-10-27", with "Total" of "$180.00" and "Interest" of "$0.00".
## Confirm the order
Click "Confirm and pay $45.00 today" and verify a green banner titled "Order placed" names order "KL-3301".The order is the substance here: the schedule is asserted before the confirm button is pressed, because disclosure after commitment is not disclosure.
Step by step coverage
Four steps that move from selection through approval to the schedule and only then to the order.
| Step | What it proves |
|---|---|
| Choose Klarnah | The pay in four option is presented for the right order and amount |
| Complete the quick check | Identity details are accepted and a decision is reached |
| Verify the schedule appears before you confirm | All four dates, all four amounts, the total and the interest |
| Confirm the order | The order is placed and named, with the first payment taken today |
The first payment being taken today, and the remaining three being scheduled, is the detail that distinguishes pay in four from a deferred payment. It is worth having in the file.
Adding it to a suite
kane-cli testmd run tests/klarna/pay-in-4_test.mdDates in the schedule move with the order date, so this file is the version pinned to seeded data. For a live environment, assert the intervals rather than the absolute dates.
Regulated disclosures are the strongest case for deriving tests from a written requirement. From a PRD to evidence covers building a suite that way, and generating the variants covers producing the approval and decline pair together.
Author
Bhawana is a Community Evangelist at TestMu AI with over 3 years of experience creating technically accurate, strategy-driven content in software testing. She has authored 50+ blogs on test automation, cross-browser testing, mobile testing, and real device testing. She also serves as Product Marketing Manager for Kane CLI, the command-line tool that runs browser automation from the terminal using natural-language flows in a real Chrome browser. Bhawana is certified in KaneAI, Selenium, Appium, Playwright, and Cypress, reflecting her hands-on knowledge of modern automation practices. On LinkedIn, she is followed by 6000+ QA engineers, testers, AI automation testers, and tech leaders.
Pay in Four FAQs
Did you find this page helpful?
TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance
- Advanced access controls
- Advanced data retention rules
- Advanced Local Testing
- Premium Support options
- Early access to beta features
- Private Slack Channel
- Unlimited Manual Accessibility DevTools Tests




