PaymentKits guide · 5 min read
Test refund states with synthetic payment events
Model refund pending, partial and successful outcomes without copying a customer payment payload.
Keep refund separate
A successful payment does not imply a successful refund. Store and test refund state independently.
Use minor units
Keep fixture amounts as integer minor units and use an explicit currency.
Exercise delayed outcomes
Use a pending refund fixture before the final success fixture to prove the UI does not guess.