Payment and money-flow testing

Scripted cases through provider sandboxes: declines, refunds, chargebacks, partial captures, currency.

Mandatory for 17 of 46 product types. Usually run by a QA engineer.

What it catches

• wrong amounts
• double charges
• orphan orders
• failed refunds

What it misses

• provider outages

Which product types need it and why

Done conditions used on playbook pages

Each mandatory cell has its own done condition, written for that product type.

• buy now pay later service (Fintech): In the sandbox, a full refund from the merchant cancels all unpaid instalments and a partial refund reduces them, with no further autopay charge.
• dating app (Consumer apps): A sandbox premium purchase, renewal, refund and bank dispute each leave the member's premium status and charge history matching the store receipt.
• ecommerce store (Commerce): A declined card, a 3-D Secure challenge, a partial refund and a full cancellation each leave exactly one matching entry on the test card statement and in the admin order.
• EV charging app (Infrastructure and developer products): A session stopped early, a session the charger aborts and a declined card each end with one charge matching the energy delivered and no held amount left on the test card.
• expense management tool (Fintech): In the card sandbox, a frozen card declines the next purchase, a merchant-category block declines a blocked purchase, and a spend limit declines the first charge above it.
• grocery delivery app (Commerce): A test order with a weighed item and a substitute, reported as delivered after its chilled slot ended, is refunded in full to the original test card in the sandbox when the guarantee promises a refund, not paid as a credit toward the next basket.
• insurance app (Fintech): In the sandbox, a mid-term cancellation refunds the unearned premium once to the original card, and a declined renewal payment does not mark the policy as paid.
• kids app (Education): In the store sandbox, each purchase asks for a fresh parent approval and produces one charge, and a second tap within a minute does not buy again.
• language learning app (Education): In the store sandbox, a trial converts, renews, is cancelled in the app and is restored on a second device, and each step shows the right plan with one charge or none.
• lending platform (Fintech): In the payment sandbox, an autopay debit pulls only from the account the borrower authorized, and a granted extension cancels the debit scheduled for that date.
• loyalty program app (Commerce): A stored value top-up and spend each show once on the member statement and in the sandbox, and the stored value card cannot be moved to another account without signing in again.
• mental health app (Healthcare): After a test user cancels in the app, the store or payment sandbox shows the subscription ended and no charge on the next renewal date.
• mobile game (Consumer apps): No sandbox purchase can start from a loading screen, sleep wake or item preview, and every purchase asks for a confirmation that names the item and price.
• subscription box service (Commerce): A renewal, a failed card with retries, a plan change mid-cycle and a cancellation before the billing date each leave the expected charges, and only those, on the test card statement.
• telemedicine app (Healthcare): After a test patient cancels the membership in the app, the payment sandbox shows no further charge on the next billing date.
• stock trading app (Fintech): In the sandbox, a deposit whose ACH pull is returned removes the instant buying power, freezes withdrawal and flags the account for review.
• travel booking app (Commerce): A test flight cancelled by the supplier sandbox produces a refund to the original test card, shown on the traveller's trip page.

Tools

Alphabetical. Not recommendations.