Use the same Postman collection from before, but import the LIVE environment file this time instead of TEST. Select Adyen JWE - LIVE from the environment dropdown before sending any request.
The base URL is already filled in for you in that file — unlike your API key, store ID, and Public key, it's the same for every store and doesn't need to be looked up in Forge.
For LIVE, "Forge" means the production instance at pay.araspayment.com — not the TEST/development instance at develop.araspayment.com used earlier.
📸 [Screenshot: Forge (production) → Store → Integration → Adyen Integration Details]
Same three fields as TEST — API Key, Store ID, Public key — but now the LIVE values. These are separate from, and different than, your TEST values.
Your LIVE Public key is a different key from your TEST Public key. Copy it fresh from the production Forge page rather than reusing the TEST value — see Set up your Adyen TEST environment in Postman for what it should look like.
Leave adyenCseJwk blank here too, for the same reason as in TEST.
LIVE only accepts real cards — test card numbers will be declined, and the collection blocks them from being sent here at all.
Use 1.1 Cert check - zero-value auth with a real card, not 1.2 Authorise. This is the same milestone as TEST: a response containing a resultCode confirms your LIVE key and store ID are correct, without moving any money.
TEST
LIVE
Forge instance |
|
|
Cards | Adyen's test card numbers | Real cards only |
Safe way to validate | 1.1 or 1.2 | 1.1 only |
Public key | TEST key | A different, LIVE-specific key |
The same causes from Set up your Adyen TEST environment in Postman apply here. If something that worked in TEST fails in LIVE, check first that every value in the LIVE environment actually came from the production Forge instance — a TEST value pasted into the LIVE environment is the most common cause.
