Questions, answered honestly.

Sign up and you get a sandbox workspace immediately. Onboarding captures your company profile, payment needs, regions, currencies, risk category, and support requirements so FlowAcq can route you to the right review and pricing path.

Start onboarding

Yes. Sandbox is self-serve. You can create an account, complete onboarding, request provider recommendations, generate sandbox keys, and open support cases without a demo call. Live processing stays locked until KYB, provider approval, and fee agreement.

Choose None yet. Current PSPs are only migration context: they tell FlowAcq whether you need help moving from Stripe, Adyen, PayPal, a local acquirer, or a direct bank or wallet setup. Not having a provider does not block onboarding.

No. Tell FlowAcq what your business needs to accept, route, settle, or pay out. You can choose payment methods, countries, currencies, high-risk or crypto needs, payout needs, and urgency. Specific provider interest is optional; the connector catalog is FlowAcq's job to maintain.

FlowAcq is a payment orchestration platform. It sits above PSPs, acquirers, wallets, bank rails, and future crypto or stablecoin providers. FlowAcq gives merchants one integration, one dashboard, normalized webhooks, routing, auditability, and provider lifecycle controls. Underlying live rails still require provider contracts, credentials, compliance approval, and the right legal posture.

FlowAcq gives you one API, one set of signed webhooks, and one operations console across many provider paths. The platform helps select and operate providers, but it does not pretend every cataloged provider is live for every merchant.

Each charge is screened and sent through the configured live path today. Health, cost, eligibility, BIN, geography, currency, and risk-rule signals are routing foundations for approved future providers.

FlowAcq is designed to support health-aware routing and failover after approved secondary providers and compatible tokens are available. True universal cross-PSP card-token failover requires a token vault, which is not live yet.

Send an Idempotency-Key on state-changing requests. Retrying with the same key returns the original result instead of creating a duplicate charge.

Live processing turns on only after business profile completion, KYB document review, risk review, provider approval, live terms acceptance, and a fee agreement. Until then, sandbox is available and live mode remains locked.

Payments move people's money. FlowAcq must verify the business, understand the risk model, confirm provider eligibility, and assign pricing before live rails can be enabled.

Common requirements include company registration, proof of business address, director or beneficial-owner ID, processing history, website or product review details, and extra licenses or ownership documents for high-risk, crypto, or iGaming cases.

Yes, while the file is still in the uploaded state. The dashboard shows uploaded filename, size, and status, and lets you delete or replace the file before submitting it for review. Once submitted or under review, the file is locked for auditability.

They are reviewed case by case. FlowAcq can collect high-risk, iGaming, crypto, payouts, and cross-border needs during onboarding, but live approval depends on KYB, legal and compliance review, provider contracts, reserves, and the rails your business requires.

They can start sandbox onboarding and describe the crypto or stablecoin use case. Live support depends on jurisdiction, risk posture, wallet or settlement requirements, provider availability, and a signed fee agreement.

FlowAcq is designed for global merchant intake, but live processing is not the same as a global promise. Tell us every country, region, and currency you need. FlowAcq maps that to provider coverage, compliance review, settlement options, and pricing.

Not live today. China wallets and QR methods are planned and partner-dependent.

Coverage

Stripe is the currently live connector. Other names in the catalog are staged, coming-soon, or planned unless their badge says live.

It means FlowAcq maintains a provider library across card acquiring, wallets, bank rails, B2B settlement, FX, payouts, and crypto or stablecoins. It does not mean every connector is enabled for live traffic today. Provider names are honestly badged on Coverage.

Coverage

The right provider path changes by market. Cards, wallets, open banking, bank transfer, crypto, payouts, settlement, and local APMs all have different coverage and approval requirements. The intake helps FlowAcq recommend the right path without forcing you to know every connector name.

Your exact fees are set at approval through a fee agreement. They can include FlowAcq platform fees, provider pass-through or markup, monthly minimums, refund or dispute fees, FX, reserves, risk surcharges, and payout terms.

You can see plan structure and rough expectations, but exact live fees depend on business review, volume, risk, methods, provider availability, and final approval.

Yes, depending on the method and agreement. Some methods can be pass-through, interchange-plus, flat-fee, or fee-free from FlowAcq while still carrying provider or network costs.

Plans are on the Pricing page. Final live pricing is confirmed during KYB, provider approval, and fee-agreement assignment.

Pricing

Open a support case from your dashboard. Cases are threaded, SLA-tracked, and tied to the right environment and resource when possible.

Yes. Many dashboard pages open support with context already attached: transactions, customers, webhooks, KYB documents, PSP credentials, payouts, settlements, billing, and provider catalog questions.

Include the environment, transaction or webhook IDs, screenshots or attachments when useful, what you expected, what happened, and timestamps. The more context you give, the faster FlowAcq can resolve it.

FlowAcq is PCI-aware and designed to avoid storing raw card numbers. Hosted checkout, token vault, and provider-specific flows still require the correct PCI or SAQ decision before live payment collection.

Every event is signed with HMAC-SHA256 and delivered with a FlowAcq signature header. Deliveries are logged, observable, and replayable from the dashboard.