Guides
Testing with the sandbox
A complete environment with fictitious affiliations and test cards, to try everything without real money.
The sandbox mirrors production with test providers: no payment is real there, no card is charged.
Environments
| Environment | API v2 | Use |
|---|---|---|
| Sandbox | https://api.preprod.konnect.network | Integration, tests, demos. |
| Production | https://api.konnect.network | Real payments, after the going-live checklist. |
Each environment has its own accounts, organisations, API keys and Wallet IDs. A sandbox key is refused in production (401), and the other way round: it is the first thing to check when you get a 401.
Open a sandbox account
- Sign up on the sandbox dashboard and create an organisation.
- Add a test affiliation for each provider you want to try: test credentials are prefilled, no contract is needed.
- Generate an API key and note the Wallet ID.
Test cards
Test cards depend on the test provider (ClicToPay, Flouci, IZI...). They are shown on the sandbox payment page and will be listed here with the providers' sandbox credentials (lot 1.5); none works in production.
Never a real card in the sandbox
Never use a real card or real customer data in the sandbox, even for a quick try. Names, e-mails and numbers in the examples are fictitious.
Scenarios to cover before production
- Successful payment: the order becomes paid once, even when the webhook arrives twice.
- Declined payment: the buyer lands on
failUrland can try again. - Expired payment: nothing is delivered after
lifespan. - Amount changed: a gap between the payment and the order blocks delivery.
- Invalid key: your site shows a clear error without exposing the key.