Only relevant if Adyen has approved raw card handling for your account.
You collect the card number, expiry, and security code in your own inputs, encrypt them client-side into a JWE token using Adyen's public key, and place the result in paymentMethod with "type": "scheme". Follow Adyen's JWE documentation for the current encryption procedure and field names.
Beyond encryption, you are responsible for everything Drop-in would otherwise do:
browserInfo — collect and send it, or 3DS will fail in ways that are hard to diagnose.- — when the response contains an
action with a redirect, perform it yourself and handle the return. - — render the challenge and submit the result to
payment-details yourself. - — every one you add is a new front-end implementation.
Note that you can mix approaches. Using raw fields for cards does not prevent you from mounting Components for iDEAL, Klarna, and wallets, and doing so avoids reimplementing their redirect flows by hand.