FlowAlp

Testing for developers

July 30, 2026

How FlowAlp Pay test mode works: simulate payments without moving real money, what to test before go-live, and how to keep test data separate.

FlowAlp Pay lets you exercise the complete payment flow — checkout, redirects, webhooks, refunds — without moving real money. Test mode is a setting on the payment methods of your account, not a separate system: you keep the same instance, the same API credentials, and the same endpoints.

How test mode works

  • You switch a payment method (or its provider configuration) from Live to Test in the dashboard.
  • While test mode is active, the checkout labels the affected methods as TEST and displays usable test cards directly on the payment page.
  • Transactions created this way are recorded as test transactions: no money moves and nothing is settled to your bank account.
  • Test payments can be refunded, so you can rehearse your refund handling too.

Test mode availability per payment method depends on your account configuration. Some methods, such as TWINT and PostFinance, always complete with a confirmed status in test mode — simulate declined outcomes with test cards instead.

What to test before going live

  • Credentials: SignatureCheck succeeds with the credentials your production system will use.
  • Gateway creation with realistic amounts in minor units and a unique referenceId per order (First API request).
  • One payment per outcome: confirmed, declined, and cancelled — including the matching success, failed, and cancel redirect URLs (Test cards and scenarios).
  • Webhook reception, signature verification, and idempotent processing of repeated deliveries (Configure webhooks).
  • A refund of a test payment, end to end.
  • Reconciliation: retrieving the transaction via the API returns the status your system recorded (List and retrieve Transactions).

Simulating outcomes

Card test numbers let you trigger both confirmed and declined payments deterministically. The numbers, together with scenarios for TWINT, wallets, and refunds, are collected in Test cards and scenarios.

Keep test and live apart

  • Point redirect URLs at your staging environment while testing.
  • Never use production API Secrets in public or automated test setups — see API credentials.
  • In the dashboard, transactions carry their mode, so you can filter the list to live payments only.
  • Test transactions cannot be deleted — filtering is the supported way to hide them.

Test plan complete? Continue with Test cards and scenarios for concrete card numbers, then work through the go-live checklist.