FAQ

Questions before you build.

Answers about Paysation’s card payment infrastructure, orchestration, decisioning, merchant services and demo portal.

Platform and payments

Start with the payment layer.

These answers are for general information. Commercial availability, configuration and pricing depend on your business model, markets, integration scope and approval requirements.

01Platform

What is Paysation?

Paysation provides card payment infrastructure for merchants: acquiring support, hosted checkout and payment links, recurring payment flows, orchestration, routing, risk controls, alerting services and operational visibility.

02Infrastructure

Is Paysation only a payment gateway?

No. Paysation is positioned as an infrastructure and decision layer around card payments, combining acceptance with routing, fraud controls, alerting services and transaction-level decisioning.

03Payments

What payment flows are supported?

The website focuses on card payments, hosted checkout, payment links and recurring card payment flows. Final availability depends on the merchant setup, integration model and approval requirements.

04Routing

What is payment orchestration?

Payment orchestration routes transactions across acquiring connections and can support cascading or failover logic when a connection degrades or a transaction needs another eligible path.

05Decisioning

What is predictive decisioning?

Predictive decisioning uses ML-based scoring to inform payment decisions such as authorization quality, retry probability, fraud risk and repeat-payment optimization. Configuration depends on the integration.

06Demo

Is the merchant portal live data?

The public merchant portal preview is a demo environment. It shows the type of operational visibility Paysation can provide and is not connected to live merchant production data.

Integration and operations

Integration questions, without the noise.

Compliance, 3DS, alerting, pricing and first steps — grouped around how merchants actually evaluate payment infrastructure.

01API

How do merchants integrate?

Merchants can discuss the right integration model with Paysation. Developer documentation is available for the payment API surface and integration guidance.

02PCI DSS

Does Paysation help with PCI DSS scope?

Paysation provides PCI DSS support and payment-flow options that can help merchants understand, reduce and manage PCI DSS scope around card payment acceptance.

033DS

Does Paysation support 3DS?

Paysation describes intelligent 3DS as part of the card payment infrastructure, applying authentication where it helps based on risk signals and payment requirements.

04Alerts

What are RDR and Ethoca alerts?

RDR and Ethoca are alerting services that can surface dispute or fraud signals earlier and connect them into structured operational workflows.

05Pricing

How is pricing handled?

Paysation pricing is quote-based. It depends on integration scope, payment flows, markets, merchant requirements and operational needs rather than fixed public tiers.

06Sales

How do I start?

Use the Talk to sales form and describe your payment flows, markets, transaction profile, integration needs and timeline. Paysation can then scope the right setup.

Recommended next step

Still comparing options?

The best answer depends on your payment flows, markets, transaction profile and operational requirements.

Need a specific answer?

Scope the answer around your payment operation.

If your question depends on your business model, markets, volumes or integration scope, contact the Paysation team for a scoped response.