Download both files from Google Drive and import them into Postman:
the collection file
the TEST environment file
In Postman, select the Adyen JWE - TEST environment from the environment dropdown before sending any request.
For this walkthrough, "Forge" means the TEST/development instance at develop.araspayment.com.
📸 [Screenshot: Forge → Store → Integration → Adyen Integration Details]
Three of the four environment values live on one page:
Store → Integration → Adyen Integration Details
Environment variable
What to look for
| Labeled API Key on that page |
| Labeled Store ID — starts with |
| Labeled Public key — a long string in the format |
Copy each value into the matching row of the Adyen JWE - TEST environment in Postman.
Leave
adyenCseJwkblank. It's not needed for this walkthrough — the collection uses the Public key directly. You'll only need to generate a JWK once you move to writing your own code; see From Postman to your own implementation.
Open 0. Setup & sanity → 0.1 Get payment methods and click Send.
A successful response includes a paymentMethods array containing an entry with "type": "scheme" — that confirms your API key, store ID, and merchant account are all valid together. If this fails, don't move on to the next step yet — see Troubleshooting below.
Open 1. JWE payment flow → 1.1 Cert check - zero-value auth and click Send.
This sends a test card, encrypted with your Public key, as a $0 verification rather than a real charge. A response containing a resultCode — even Refused — confirms your Public key is correctly set up: it means Adyen successfully decrypted what Postman encrypted. Look for additionalData.cardSummary in the response; it should show the last four digits of the test card Postman used.
This is the milestone. Once 1.1 returns a resultCode, you've confirmed everything you need to start building this into your own application. Continue to From Postman to your own implementation, or explore the collection further — 1.2 Authorise runs the same flow as a full payment.
Symptom
Likely cause
0.1 fails / no | Check the API key and store ID against Forge — they may not match, or cards may not be enabled for this store |
1.1 fails with a message about the card | Check that the Public key was copied in full — it's several hundred characters, and it's easy to copy only part of it |
1.1 fails with a message about the store | The store ID may be for a different environment (TEST vs LIVE) — double-check which Forge page you copied it from |
Adyen's API-only card integration guide
Adyen's Checkout API /payments reference — see the paymentMethod.encryptedCard field
