Card Checkout (Bundled UI)
Use the drop-in CardPay builder to render EdfaPay's themeable Compose Multiplatform card-input flow, complete with 3-D Secure 2 handling. Configure the order, payer, design, and language — or pass a card to bypass the input form entirely.
Overview
CardPay is a fluent builder that renders the bundled checkout surface. Because card data is captured inside the SDK's Compose surface and sent via TLS directly to EdfaPay, your app stays out of PCI scope. The result returns through onTransactionSuccess / onTransactionFailure; 3-D Secure 2 challenges are rendered full-screen by the SDK automatically.
Single-use instances
Each CardPay instance is single-use — create a new one per checkout. On iOS the bundled UI is a @Composable, so embed it via a ComposeUIViewController in your shared KMP module and present it from SwiftUI with UIViewControllerRepresentable.
The CardPay Builder
Set the order and payer, pick a design and language, optionally flag pre-auth (setAuth) or hosted MIT enrolment (setRecurring), wire the result URLs, and attach the success / failure callbacks. Then start the flow — initialize(onDismiss) on native, start() on Flutter.
Loading...Designs & Languages
Three pre-built card-input designs and two languages are available. Set them with setDesignType and setLanguage.
| Setter | Values | Notes |
|---|---|---|
| setDesignType | EdfaPayDesignType.ONE / TWO / THREE (Flutter: one / two / three) | Selects one of three pre-built card-input layouts. |
| setLanguage | EdfaPayLanguage.en / ar | English or Arabic (RTL) checkout copy. |
| setAuth | false (sale) / true (pre-auth) | true holds funds for a later capture(). |
| setRecurring | channelId, enabled | Enrols the card for hosted merchant-initiated (MIT) charges. |
Bypass the Input Form
Pass an EdfaPgCard and the SDK skips the design 1/2/3 input UI, jumping straight to the sale plus the 3-D Secure WebView. Useful for stored-credential flows where your app already collected the card.
Loading...PCI scope
Collecting the card yourself makes your app PCI-relevant (scope to SAQ-A-EP). Prefer the bundled input form unless you already handle card data under your own compliance program.
On this page
Downloads
Coming SoonSample apps, release bundles, and more content will be available here soon.