嵌入式結帳
Cardflo 的嵌入式結帳可將支付處理直接無縫整合到您的網站或應用程式中。 此解決方案提供安全的、符合 PCI 標準的支付表單，該表單會顯示在您現有的頁面中，從而消除重定向並保持一致的用戶體驗。
它專為尋求直接整合而又不犧牲控制或品牌形象的商戶而設計。
- 類別
- 結帳
- 功能數
- 10
- 適用於
- 所有方案
概覽
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.
運作方式
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.
為何重要
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.
應用案例
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.
數據概覽
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.
相關術語
Talk to our team about a live rollout on your acquiring stack.
What you get with 嵌入式結帳
- 安全、符合 PCI 標準的支付字段直接嵌入到您的網站。
- 沒有重定向，讓客戶在整個結帳過程中留在您的網域。
- 可定制的樣式以符合您的品牌美學。
- 與完全定制相比，減少了開發工作。
- 針對移動和桌面響應性進行了優化。
- 透過保持一致的用戶界面來增強客戶信任。
- 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 嵌入式結帳
嵌入式結帳和自訂結帳之間有什麼區別？
嵌入式結帳提供預建的、安全的支付字段，您可以對其進行樣式設置並放置在您的網站上。 自訂結帳則提供對支付表單和流程的每個元素的完全控制，需要更多的開發。
嵌入式結帳實施起來更快，而自訂結帳則為定制需求提供最大的靈活性。
嵌入式結帳是否符合 PCI 標準？
是的，Cardflo 的嵌入式結帳旨在符合 PCI 標準。 敏感的卡數據由 Cardflo 的安全基礎設施直接處理，從而減輕您的 PCI 負擔。
與直接處理原始卡數據相比，整合嵌入式解決方案的商戶可以更輕鬆地實現合規性。
我是否仍然可以在嵌入式結帳中使用智能路由和拒絕恢復？
是的，Cardflo 的核心協調功能，例如智能路由、拒絕恢復和 3DS 優化，在嵌入式結帳背景下無縫運行。 嵌入式解決方案處理前端支付捕獲，而我們的平台管理交易處理邏輯以最大程度地提高批准率。
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.