Test and go live

Test your integration

Build and test on the test host with your test credentials. It works like production, but no real money moves.

Test and production have separate credentials. Never use real cards in test, and never use test cards in production. See Environments.

Test these flows

• A payment that succeeds, fails and is cancelled by the shopper, with the right return page for each
• Your server confirms each payment with a notification or Get payment status, not the return URL
• Capture: full, partial and, if you use split shipment, several partial captures
• Cancel and refund: full and partial
• Retries: a timed-out request sent again with the same idempotency-key doesn't create a second payment
• A new idempotency-key for every new operation
• Your access token is renewed before it expires
• Each payment method you'll offer
• If you embed the checkout: steps that leave your page, such as 3-D Secure and Vipps MobilePay
• If you save cards or use recurring payments: save, list, pre-select, delete, and a recurring charge

Check your setup

A payment method shows up only when it is set up for your merchant account.

What works also depends on the acquirer's capabilities, the scheme rules and your merchant configuration.

Go live

1. Ask for production credentials. See Get access.
2. Change the hosts to production.
3. Make sure your system looks up Aera's host addresses again at least every 60 seconds (DNS cache time 60 seconds or less). See Environments.
4. Make a first real payment with a small amount, and refund it.