Adyen offers two ways to collect card details without your server ever touching a raw card number:
Adyen's hosted fields (Drop-in / Components). Card number, expiry, and CVC are entered into fields that Adyen hosts inside your page. Adyen documents this as the default approach for most merchants, and it keeps you in the simplest PCI compliance tier.
Your own card form, encrypted client-side (what this collection covers). You build the input fields yourself and encrypt the values in the browser before they go anywhere. This gives you full control over the checkout UI, but it also means raw card data passes through your own JavaScript, which puts you in a higher PCI compliance tier than the hosted-fields option.
If you don't have a specific reason to build a custom card form, talk to your SwipeAras contact before choosing this path — Adyen's hosted fields solve the same problem with less compliance overhead. Adyen's own guidance on this trade-off is in their API-only card integration guide.
Four values, all specific to your store:
Value
Where it comes from
API key | Forge → your store → Integration → Adyen Integration Details |
Store ID | Same page |
Public key | Same page |
A JWK (JSON Web Key) version of the Public key | You generate this yourself, only once you move past Postman — see the "custom code" articles below |
The first three are values you copy. The fourth is something your own code produces from the Public key — you don't need it to complete the Postman walkthrough in this collection.
Download the Postman collection — a ready-made set of API requests that let you confirm your values are correct before writing any code: Download from Google Drive
Set up your TEST environment in Postman and get a successful response — see Set up your Adyen TEST environment in Postman.
Move to LIVE when you're ready — see Moving to Adyen LIVE.
Build the encryption step into your own application — see From Postman to your own implementation and the articles after it.
Set up your Adyen TEST environment in Postman — where each value comes from, and how to get a working test response
Moving to Adyen LIVE — what changes between TEST and LIVE
From Postman to your own implementation — how the pieces map onto real application code
Example: converting your Public key into a JWK (TypeScript)
Adyen's own documentation covers the cryptography — what a JWE is, which algorithm to use, how to structure the request. See their Card encryption with JWE guide and the Checkout API /payments reference for that. This collection doesn't repeat any of it — it links to the specific sections you need. What it adds is the part Adyen's docs can't cover: exactly where in Forge each value lives for your store, and how those values fit together in practice.
