FAQFor payment, integration, and operations teams

Answers for the teams running modern payments

Quick answers about integrations, uptime, routing, settlement, tokenization, and launch support so your team can move from questions to implementation with less friction.

Support hub
Integrations

APIs, SDKs, and hosted paths

Understand how host-to-host, embedded SDKs, payment links, and hosted checkout fit different launch shapes.

Operations

Reliability, settlement, and orchestration

Get clarity on uptime targets, settlement windows, routing decisions, and the operating rhythm behind the platform.

Support

Go-live guidance and next steps

See how a55 helps teams map the right integration path, issue test keys, and move from evaluation to production.

Data Only Integration

Telemetry-only feeds for headless flows.

Full Purchase Info

Line items, amounts, and richer context.

3DS

Optional or required auth challenges.

Apple/Google Pay

Wallet tokens with network controls.

Smart Retry

Routing-aware retries by issuer.

Risk Signals

AF scoring and external signals.

Common questions

What teams usually want to know before they launch.

These are the questions that come up most often around integration shape, trust controls, observability, recurring readiness, and operational support.

Still deciding?

Read the docs or talk with the a55 team.

Some questions are best answered by reviewing the technical docs first. Others are easier to solve with context about your volume, integration shape, and operating model.