Online payments
Three ways to take a card-not-present payment, by how much card data your server handles.
Hosted Payment PageSAQ A
Redirect to a kepa-hosted page. Least code, least risk.→Kepa ElementsSAQ A
Card fields, wallets, and APMs rendered in your own checkout. The card input is a kepa iframe, so you stay in SAQ A.→Server-sideSAQ D / A-EP
Send the card from your server — a PAN from a PCI-L1 source, a vault token, or a saved card for rebills.→The shape is always the same
Whichever method, your server creates a payment intent with a secret key and gets back a client secret. Where the card is entered is the only thing that changes: a hosted page, your page via Elements, or your server. Fulfil on the webhook, never the browser callback.
Reuse a card
Set setupFutureUsage on the intent to save the card as a payment method. Charge it later from your server for rebills, or put it on a subscription for recurring billing.
Orchestration is automatic
Retries, cascading, and failover across acquirers happen for you — a soft decline is retried, a down acquirer is routed around. There is nothing to wire up; it runs behind every charge.