Valpay uses Adyen as its underlying payment platform, so you build your online payments directly against Adyen's APIs and client-side libraries, using the account and credentials Valpay provisions for you. This page explains how an online payments integration fits together before you start building.
What you can accept
With an online payments integration you can accept cards, digital wallets, and local payment methods on your website and mobile app, across web, iOS, Android, React Native, and Flutter. A single Adyen Checkout API processes all payment methods. The same integration supports a range of transaction types, including one-off payments, subscriptions, bookings, and top-ups.
Integration architecture
A complete online payments integration is made up of three parts:
Payments server: makes requests to Adyen's Checkout API and receives the responses.
Client website or app: collects payment details from the shopper (using Adyen's Drop-in or Components) and passes them to your server.
Webhook server: receives webhooks from Adyen about payment status and other payment activity.
Choosing a server-side flow
Adyen offers two server-side flows. You choose one based on how much control you need:
Sessions flow (recommended default): your server makes a single Checkout API request to
/sessions, and Adyen handles most of the flow. This is the lightest to build and covers most integrations.Advanced flow: your server makes three Checkout API requests (
/paymentMethods,/payments, and/payments/details). It requires more effort but supports additional use cases, such as Apple Pay and Google Pay express checkout and reordering payment methods per transaction.
Choosing an integration method
You also choose how the payment form is presented to the shopper: Hosted Checkout, Drop-in, Components, or a direct API integration. Each trades off effort against customization. Valpay's current reference integration uses the Adyen Web Drop-in. See Integration Methods for details on each.
What Valpay provides
A Valpay-provisioned Adyen account: test first, then live. Do not create an Adyen account directly.
Credentials: an API key, your merchant account, and (for Drop-in/Components) a client key.
A Store ID, which is required on all transactions.
Before you go live
Build and validate everything in the test environment first. Test transactions do not reach the card networks. When you are ready, switch to the live environment to process real payments. See Environments.