A clear message path from checkout to endpoint.
Connect online payment requests to your contracted endpoints. Get back consistent statuses, references and events, so checkout, support and finance can follow every transaction.
Connections
What you get
Keep payment messages and statuses connected.
A defined transaction path
Map each checkout request to an agreed endpoint and return one consistent operating reference.
Clear status tracking
Link requests, responses, timeouts and reversals to the same transaction context.
Planned risk handoffs
Decide where authentication, screening, fraud and dispute events enter the payment flow.
How it works
Five steps from checkout to reconciliation.
Accept
Receive a payment request from checkout or platform services.
Validate
Check required fields and identifiers for the endpoint.
Send
Transmit the message to the contracted endpoint.
Return
Deliver the response and any later status events.
Reconcile
Match identifiers and exceptions to your downstream records.
Capabilities
Message, endpoint and operations, defined up front.
Request validation
Check required fields, identifiers and formatting before a request goes out.
Endpoint connectivity
Connect to processors, PSPs and acquirers under your own commercial agreements.
Status mapping
Normalized status categories that keep the provider detail you need for investigation.
Timeouts and exceptions
Defined behavior for delayed, failed, duplicated, unknown or incomplete outcomes.
Event notifications
Callbacks and webhooks for your checkout, operations and reconciliation systems.
Risk handoffs
Connect 3D Secure or risk events at the agreed point in the flow.
Use cases
Where teams use the gateway.
Fintech payment acceptance
Agreed request, endpoint and event handling behind your own customer experience.
Marketplace checkout
Consistent transaction references and cleaner handoffs to risk and dispute teams.
Travel and reservations
Track authorization attempts, cancellations, reversals and refunds across each booking.
Gateway modernization
Replace a legacy integration in controlled stages, with gateway and orchestration roles kept clear.
FAQ
Common questions.
A gateway is not an acquirer. Vellfi carries the payment messages. The issuer decides authorization, and acquiring, processing, settlement and custody stay with your contracted endpoint providers.
How is a gateway different from orchestration?
The gateway connects to endpoints and carries the messages. Orchestration applies routing policy across several paths. You can use either one, or both together.
Which endpoints can the gateway connect to?
Compatible processors, PSPs, acquirers and other endpoints you hold contracts with. We confirm each endpoint, market, currency and transaction type during scoping.
Are hosted fields or redirects available?
Where your endpoint and technical scope support them. We choose between API, hosted and embedded paths during technical design.
How are delayed or unknown outcomes handled?
The deployment defines status mapping, timeouts, event delivery and reconciliation identifiers, plus how your team responds to each exception.
Can 3D Secure be connected?
It can, as a separate Vellfi service, where your gateway, checkout channel and 3D Secure setup are compatible.
Related services
Works well with.
Review your checkout-to-endpoint path.
Share your checkout channels, endpoint contracts, required events and current exceptions. We will map the gateway flow. No live card data needed.