Adyen payment integration for ecommerce

Most card schemes allow 7-30 days between auth and capture. iWeb typically designs auth-on-checkout and capture-on-dispatch, keeping the window tight. If you need longer holds (e.g. made-to-order items), Adyen can extend the window, but your team must trigger captures before expiry or funds are released.

If capture fails, the authorisation still holds but funds are not settled. Your OMS should flag the order as 'capture pending' and retry. If retries fail, your payments team investigates with Adyen to see if the transaction expired or if there was a scheme rejection. iWeb builds retry queues and escalation alerts.

Adyen detects when 3DS is required based on scheme rules and shopper risk profile. If needed, Adyen returns a challenge URL and your checkout redirects the shopper to the issuing bank's challenge page. Once the shopper completes the challenge, your checkout polls Adyen for the result and completes the auth. iWeb implements the redirect, polling and timeout logic.

Yes. Adyen tokenises cards on first purchase if the shopper opts in. On repeat visits, your checkout loads the saved token and uses it for auth without re-entry. iWeb ensures tokens are stored securely and expired tokens are refreshed or removed from the saved list.

Your OMS sends a refund request to Adyen with the original transaction reference and refund amount. Adyen validates the refund and sends it to the customer's issuing bank. Most refunds appear in 3-5 business days. iWeb tracks refund status in your order record and alerts your team if a refund is declined.

Adyen settles captured transactions on a daily or weekly schedule depending on your contract and risk profile. Settlement arrives 1-3 days after capture. Adyen's daily settlement report tells you which transactions settled and which fees were deducted. Your ERP team matches the report to bank deposits.

A chargeback happens when a customer disputes a charge with their bank, typically weeks or months after the transaction. Adyen notifies you via email and includes the chargeback in your settlement report. Your team must investigate the original order and provide evidence to Adyen or accept the chargeback loss. iWeb links chargebacks back to orders in your system.

Adyen has 99.99% uptime, but outages happen. Most commerce platforms can fall back to an alternative payment gateway or offer a pay-by-invoice option. iWeb helps you design a fallback flow (e.g. email invoice with payment instructions) so orders don't fail silently.

Adyen publishes a daily settlement report listing transactions, refunds, chargebacks and fees. Your ERP finance team imports this report and posts a single GL entry for the net settlement amount. Refunds and chargebacks post as customer credits. iWeb automates the import and matching logic.

Yes. iWeb configures your checkout to route payments to the correct merchant account based on brand, currency or customer location. Each account has its own settlement, reporting and reconciliation. Your team must monitor each account separately.

Tokens are locked to the merchant account they were created in. If you switch accounts, old tokens become invalid and returning shoppers must re-enter card details. iWeb helps you plan token migration strategies (e.g. pre-migrate tokens to the new account before go-live) to minimise disruption.

iWeb builds dashboards showing auth success rates, capture lag, refund status and exception volumes. Failed captures and chargebacks trigger alerts so your team responds before customer impact. Logs and payment records are retained for audit and chargeback investigations.

Adyen handles all raw card data, so your commerce platform scope shrinks dramatically. You still need basic PCI controls (encrypted checkout, HTTPS, secure token handling), but full SAQ-D certification is not required. Adyen's hosting and tokenisation reduce your compliance burden significantly.

Adyen returns a decline reason (insufficient funds, blocked by issuer, expired card, etc.). Your checkout displays the reason to the shopper and offers retry or alternative payment method. iWeb logs decline reasons for fraud analysis and customer service.