Test an autopay mandate and the cap that limits it

The checks that matter

The rule under test is that the cap has to cover the debit, and a mandate that violates it fails every month rather than once.

Testing the refusal first is what proves the validation exists. A mandate created with an adequate cap says nothing about whether an inadequate one would also have been created and then failed silently on the first debit.

The flow as a test file

The service selection is asserted for both its debit amount and its frequency, since a mandate is defined by both and a monthly cap against a weekly debit is a different agreement.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/phonepe-clone-app/autopay?reset=true
max_steps: 45
tags: [phonepe, fintech, mandates]
---

# PhonePey 21.2: Autopay mandate

Catalog objective: create a UPI autopay mandate for a service.
Key assertion: the mandate is active with its cap amount.

## Choose the service
Select "StreamFlix Premium" in "Service" and verify "Debit amount" reads "₹649.00" and "Frequency" reads "Monthly".

## Verify the cap must cover the debit
Type "500" into "Maximum limit per debit", type "4321" into "UPI PIN", click "Approve mandate", and verify an error says the limit must be at least ₹649.00.

## Set a valid cap and approve
Replace "Maximum limit per debit" with "1000", type "4321" into "UPI PIN", and click "Approve mandate".

## Verify the mandate is active with its cap
Verify a green banner titled "Mandate created" names the mandate for StreamFlix Premium at "₹649.00" monthly with a first debit of "2026-10-15", and the mandate list shows it with "Max ₹1,000.00" and an active status.

The final assertion includes the first debit date, which is the value that tells the customer when the standing permission first takes effect.

Step by step coverage

A service, a refusal, an approval and a record.

Both the confirmation and the mandate list are asserted. A mandate that confirms but does not appear in the list is permission the customer cannot review or revoke.

Adding it to a suite

kane-cli testmd run tests/phonepe/autopay-mandate_test.md

Add a revocation variant, since a mandate that cannot be cancelled is a considerably worse defect than one that cannot be created.

Standing permissions outlive the release that created them. Evidence based QA covers retaining proof, and generating the revocation case covers the other half of the pair.