Integration paths that bring payment orchestration, AF/3DS, and recurring coverage to any stack

Choose APIs, checkout iframe, payment links, host-to-host, POS, or data-only feeds backed by production test keys, tokenization, zero-auth verification, and observability so engineers can orchestrate direct networks and keep conversion climbing while testing against the live stack with flagged credentials.

View docs

Host-to-host orchestration

Certified host-to-host and POS flows keep routing, AF/3DS, and tokenization benchmarks aligned while data-only telemetry mirrors every decision so direct networks behave like the rest of your stack.

Host-to-host certification

Direct connections with checklists, sample payloads, and observability so you can pass certification faster.

POS + terminals

Extend the same token vault, zero-auth verification, and AF/3DS enforcement to in-store volumes.

Data-only mirroring

Stream data-only payloads from every host-to-host touchpoint to keep telemetry and reconciliations synced.

SDK experiences

Drop-in web and mobile SDKs expose wallet, Pix, card, AF/3DS, tokenization, and zero-auth controls that stream the same data-only benchmarks into the orchestration engine.

Review SDK docs

Web & mobile SDKs

Embeddable SDKs abstract payment methods while surfacing routing metadata and decisioning context.

AF & 3DS hooks

Trigger AF challenges or 3DS flows through callbacks, observability, and policy controls.

Zero-auth & token vault

SDK calls to POST /tokenize and zero-auth drop cards into the shared vault and reduce PCI scope.

Hosted checkout page

The checkout iframe and hosted checkout page pair with payment links so ops, sales, or product teams can launch experiences quickly while sharing AF/3DS benchmarks with SDKs and host-to-host flows.

See checkout demo

Checkout iframe

Hosted checkout page with branding controls, PCI-light scope, and built-in 3DS prompts.

Payment links

Generate branded links with preset amounts, metadata, and observability so non-technical teams can sell faster.

Branding & compliance

Configure expiry, allowed methods, AF/3DS requirements, and routing rules per hosted flow.

Integration benchmark matrix

Compare the host-to-host, SDK, and hosted checkout page paths—each shares AF/3DS orchestration, tokenization, zero-auth, and recurring benchmarks while streaming the same data-only telemetry.

Capability	Host-to-host	SDK	Checkout page
3DS & AF orchestration	Routing rules follow every host-to-host and POS payload with data-only mirroring across direct networks.	SDK callbacks surface AF scores and trigger 3DS so headless or embedded flows match API behavior.	Hosted checkout pages and payment links enforce AF/3DS per experience with routing + expiry controls.
Tokenization & vaulting	POS, marketplaces, and host-to-host flows point to the same token vault with lifecycle governance.	SDK calls to tokenize and zero-auth cards instantly sync to the shared vault and comply with PCI.	Hosted checkout and payment links tokenize automatically so cards can be reused for subscriptions or invoicing.
Zero-auth verification	Host-to-host endpoints and POS triggers log zero-auth events alongside settlement telemetry.	SDK hooks run zero-auth before storing credentials, mirroring API behavior.	Checkout pages auto-run zero-amount checks when collecting cards for later charges.
Recurring / subscription readiness	Direct integrations share schedules, retries, and dunning hooks with the orchestration engine.	SDK metadata carries scheduling, retry, and dunning signals into your own workflows.	Hosted experiences tie into webhook automation so payment links and checkout pages launch recurring plans quickly.
Payment experience & ownership	Own the full UX (or expose data-only feeds) while streaming telemetry across direct networks.	Choose embedded components while still controlling the UI shell and analytics.	Hand ops and GTM teams a hosted UI with branding controls, PCI-light scope, and shared observability.

Build with our docs and production test keys.

Start with production test keys—traffic is flagged as test on the live stack—review the docs, and pick the integration path that fits your architecture—API, checkout iframe, payment links, data-only, or POS.

View docs

Frequently asked questions

Integration-focused FAQs.