Paiement intégré
Le paiement intégré de Cardflo intègre de manière transparente le traitement des paiements directement dans votre site Web ou application.
Cette solution fournit un formulaire de paiement sécurisé et conforme PCI qui apparaît sur votre page existante, éliminant les redirections et maintenant une expérience utilisateur cohérente.
Il est conçu pour les marchands recherchant une intégration simple sans sacrifier le contrôle ou la présence de la marque.
- Catégorie
- Paiement
- Capacités
- 10
- Disponible sur
- Tous les plans
L'aperçu
Embedded checkout functions as a client-side integration method where payment input fields are hosted by the Service Provider (PSP) but rendered within the merchant's existing web architecture.
Unlike hosted payment pages that require a browser redirect to an external domain, this model utilises iFrames or hosted fields to maintain the user's presence on the primary site.
The data flow ensures that sensitive Primary Account Number (PAN) data never touches the merchant's server, as the input fields communicate directly with the acquirer's gateway.
This mechanism significantly reduces the scope of PCI-DSS compliance, typically allowing merchants to qualify for the simpler SAQ A or SAQ A-EP assessments.
By retaining control over the DOM around the secure fields, businesses can manage the visual layout and user journey while delegating the cryptographic security and tokenisation processes to the infrastructure layer of the payment stack.
This approach balances branding requirements with robust risk management and technical security.
Comment ça marche
Client-side Script Initialisation
The integration begins by loading a JavaScript library from the payment provider onto the merchant's checkout page.
This script creates secure containers within specific DIV elements, ensuring that the critical payment inputs remain isolated from the rest of the page's code to prevent cross-site scripting vulnerabilities or data interference.
Secure Field Rendering
The provider renders individual iFrames for the card number, expiry date, and CVV. These fields are hosted on a PCI-compliant environment but appear as part of the merchant's form.
This separation ensures that the merchant handles only non-sensitive metadata, while the actual cardholder data is transmitted directly to the gateway.
Tokenisation and Validation
When the customer enters their details, the system performs real-time validation for LUHN checks and BIN identification. Upon submission, the sensitive data is exchanged for a secure vault token.
This token represents the payment instrument and is the only credential passed to the merchant's backend for the authorisation request.
Transaction Authorisation
The merchant sends the token to their server, which then initiates an authorisation call to the acquirer. The acquirer forwards this to the card schemes and the issuer.
The issuer returns a response, such as an approval or a decline code, which the merchant then displays to the user.
Pourquoi c'est important
Conversion Rate Optimisation
Redirects often introduce friction and latency, which are primary drivers of basket abandonment. By keeping the customer within the merchant's domain throughout the entire transaction, the payment process feels like a continuous part of the user journey.
This consistency helps maintain trust, particularly during high-value transactions where a sudden change in URL might cause users to suspect a phishing attempt or a technical fault.
Security and Compliance Burden
Managing raw card data requires extensive security protocols and rigorous yearly audits under PCI-DSS Level 1 criteria. An embedded model bypasses these requirements by ensuring the merchant server never sees, processes, or stores sensitive PAN data.
This shift reduces the operational overhead and liability associated with data breaches, as the security burden is transferred to the service provider whose systems are purpose-built for data protection.
Cas d'usage
SaaS Platform Subscriptions
Software providers use embedded fields to collect payment details during account setup. This allows them to capture a payment method and store it as a network token for recurring billing without disrupting the onboarding flow or introducing external site redirects.
High-Volume E-commerce Sites
Retailers with high traffic levels use embedded checkouts to maintain brand integrity and minimise the steps to completion. This is particularly effective for mobile commerce, where redirecting between apps and browsers can lead to session timeouts or loading errors.
Enterprise Marketplaces
Marketplaces involving multiple vendors use embedded fields to standardise the payment experience across their platform. This ensures that regardless of the specific vendor, the payment infrastructure remains secure and consistent, facilitating complex split-settlement workflows at the backend.
En chiffres
Industry research suggests that removing redirects can lead to a significant decrease in cart abandonment, as customers are less likely to encounter technical friction or trust issues during the payment phase.
Using hosted fields can reduce the number of security controls a merchant must audit annually by a substantial margin compared to handling raw card data, according to standard PCI-DSS assessment benchmarks.
Optimised embedded fields that trigger native keyboards and provide real-time validation typically facilitate faster completion times for mobile users compared to traditional non-responsive form layouts.
Termes associés
Talk to our team about a live rollout on your acquiring stack.
What you get with Paiement intégré
- Champs de paiement sécurisés et conformes PCI intégrés directement sur votre site.
- Aucune redirection, gardant les clients sur votre domaine tout au long du paiement.
- Style personnalisable pour correspondre à l'esthétique de votre marque.
- Effort de développement réduit par rapport à une personnalisation complète.
- Optimisé pour la réactivité mobile et desktop.
- Confiance client renforcée en maintenant une interface utilisateur cohérente.
- Support for 3-D Secure authentication directly within the embedded flow for SCA compliance.
- Automatic BIN detection to identify card type and apply relevant processing logic immediately.
- Compatibility with modern JavaScript frameworks including React, Vue, and Angular for structured integration.
- Localised language support for checkout fields to cater to a global customer base.
A short scoping call, then a written plan for your MIDs.
Questions about Paiement intégré
Quelle est la différence entre le paiement intégré et le paiement personnalisé ?
Le paiement intégré fournit des champs de paiement pré-construits et sécurisés que vous pouvez styliser et placer sur votre site. Le paiement personnalisé offre un contrôle complet sur chaque élément du formulaire et du flux de paiement, nécessitant plus de développement.
L'intégration est plus rapide à mettre en œuvre tandis que le personnalisé offre une flexibilité maximale pour les besoins sur mesure.
Le paiement intégré est-il conforme PCI ?
Oui, le paiement intégré de Cardflo est conçu pour être conforme PCI. Les données sensibles de la carte sont traitées directement par l'infrastructure sécurisée de Cardflo, réduisant votre charge PCI.
Les marchands intégrant la solution intégrée peuvent atteindre la conformité plus facilement que s'ils traitaient directement les données brutes de la carte.
Puis-je toujours utiliser le routage intelligent et la récupération des refus avec le paiement intégré ?
Oui, les fonctionnalités d'orchestration principales de Cardflo telles que le routage intelligent, la récupération des refus et l'optimisation 3DS fonctionnent de manière transparente en arrière-plan avec le paiement intégré.
La solution intégrée gère la capture des paiements front-end, tandis que notre plateforme gère la logique de traitement des transactions pour maximiser les taux d'approbation.
What happens if a customer’s card requires 3-D Secure authentication?
When 3-D Secure is required for Strong Customer Authentication (SCA), the embedded library will typically trigger a modal or an overlay. The customer completes the challenge within this window, and once authorised, the focus returns to the merchant's checkout page.
This process happens without a full page redirect, maintaining the session and reducing the risk of the customer closing the tab during the authentication process.
Is the embedded checkout optimised for mobile devices?
Industry-standard embedded checkout components are designed to be responsive. They utilise media queries to adjust the size and layout of input fields based on the device's screen dimensions.
Furthermore, they are configured to trigger the correct numeric keypads on mobile operating systems, which improves the speed and accuracy of data entry for the customer, leading to higher completion rates on handheld devices.
Does the embedded checkout support alternative payment methods like digital wallets?
Embedded checkouts can often be configured to display digital wallet buttons, such as Apple Pay or Google Pay, alongside traditional card inputs. These methods often bypass the card entry fields entirely, using the wallet's stored credentials to authorise the transaction via a secure token.
This multi-modal approach ensures that the checkout remains flexible for various consumer preferences while maintaining a singular integration point.
Prêt à accélérer ?
Parlez-nous de votre activité. Nous vous mettrons en relation avec les bons partenaires acquéreurs et la bonne route, généralement en moins d'une semaine.