Payment processing flows

The table below illustrates how different payment processing flows handle data and influence user experience. Depending on the payment method, data may be entered manually, automatically populated, or processed through secure systems.

Each approach affects how the user interacts with the payment process, whether through a redirected page, embedded form, or in-person terminal. Choosing the right payment flow involves considering how data is managed and how it impacts the overall user experience.

Payment Flow	Data Handling	Connection
Gateway redirect	Manual Data Entry: Full details entered by payer.	Manual data entry is crucial for both Gateway Redirect and Embedded Payment, where the payer inputs all required details.
Payment-Based Checkout	Automatic Data Population: Auto-filled details.	Automatic data population enhances the experience by reducing manual input, relevant in both Gateway Redirect and Embedded Payment.
Card not present	Manual or Integrator-Provided Data: Card details entered by the payer or supplied by the integrator system.	Card-not-present transactions are processed via Gateway Redirect or Embedded Payment, without the physical presence of the card.
In-Person Payments	Terminal-Based Input: Data entered via terminal.	Terminal-based data handling is essential for In-Person Payments (Cloud), involving physical or digital terminals for transaction processing.
Embedded payment flow	Direct Data Capture: Secure processing of credit card info.	Direct data capture is specific to Embedded Payment, where credit card details are processed directly on the merchant’s site.
SoftPoS	Terminal-Based Input: Data entered via terminal or via another APP	Terminal-based data handling is essential for SoftPos Payments (Cloud), involving physical or digital terminals for transaction processing.
Giftcards & Vouchers	Code Redemption: Unique code verification.	Code redemption is handled through Gateway Redirect or Embedded Payment, where the payer enters or applies gift card/voucher codes.
Phone Pincode Check	Phone-Based Verification: PIN code sent for confirmation.	Phone-based verification involves entering a PIN code in either Gateway Redirect or Embedded Payment methods, integrating phone verification into the transaction process.
Banktransfer Initiated (DBT)	IBAN‑Oriented Transaction Handling: Payments received on Virtual or Private IBANs are captured and mapped to transaction objects; details include payer and collector IBAN data.	Secure server‑to‑server webhook/exchange model delivers DBT events (credit or debit) to your system to reconcile bank–initiated transfers with order entries.
Direct Debit & Mandates	Mandate-Based Data Capture: Bank account details and mandate information provided by the payer or integrator system.	Direct debit transactions are initiated via API using an approved mandate, with mandate creation and usage handled through backend integrations.
Recurring Payments	Token‑Based Payment Details: Cardholder details are securely tokenized after initial payment. The token can be reused for subsequent transactions.	Recurring payments are triggered via API based on a predefined schedule or event, without payer interaction at the time of execution.
Payouts	Programmatic Data Submission: Payout details provided by the Integrator.	Payouts are created via a direct API connection, where payout details are submitted server-to-server without payer interaction..