Create a defined transaction path
Map the supported checkout request to an agreed payment endpoint and return a consistent operating reference.
Payments
Global Payment Gateway
Connect supported online payment requests to contracted endpoints and return the statuses and events that checkout and operations need.
For PSPs, fintech platforms, merchants and digital businesses evaluating payment messaging, endpoint connectivity and transaction visibility.
Transaction messagingEndpoint connectivityStatus visibilityRisk handoffs
Service outcomes
Keep payment messages and returned statuses connected.
These are operating goals, not performance guarantees. Results depend on scope, participants, implementation and customer operations.
Track statuses and exceptions
Relate request, provider response, timeout, reversal and other supported events to the same transaction context.
Place risk handoffs deliberately
Define where separately scoped authentication, screening, fraud or dispute events enter the payment workflow.
Coverage & fit
Confirm the endpoints, channels and data needed for the gateway flow.
Gateway availability depends on the proposed provider relationships, transaction types, markets, currencies, credentials and technical interfaces.
Online checkout
Supported web, app, marketplace, booking or platform journeys defined during technical design.
Payment endpoints
Compatible processor, PSP, acquirer or other contracted endpoints available to the customer.
Transaction events
Requests, responses, timeouts, failures, reversals, refunds or other agreed status transitions.
Adjacent services
Payment Orchestration, 3D Secure, screening and dispute workflows where contracted separately.
Gateway is not acquiring
Gateway connectivity does not by itself make Vellfi the acquirer, processor, issuer, settlement party or custodian, and it does not determine authorization.
Priority use cases
Use a gateway where checkout needs a supported payment message path.
Fintech payment acceptance
A platform needs agreed request, endpoint and event handling behind its customer experience.
Marketplace checkout
A marketplace wants consistent transaction references and clearer handoffs to risk and dispute operations.
Travel and reservations
A booking flow needs visibility across authorization attempts, cancellations, reversals and refunds.
Gateway modernization
A business wants to replace a legacy integration in controlled stages without confusing gateway and orchestration responsibilities.
Core capabilities
Define the payment message, endpoint and operating model.
The signed scope identifies the exact messages, fields, endpoints, events and exception behavior supported by the deployment.
Request validation
Check agreed required fields, identifiers and formatting before sending an eligible request.
Endpoint connectivity
Connect to supported payment endpoints under the customer’s applicable commercial arrangements.
Status mapping
Return normalized status categories while retaining provider detail required for investigation.
Timeout and exception handling
Define behavior for delayed, failed, duplicated, unknown or incomplete outcomes.
Event notifications
Deliver agreed callbacks or webhooks for downstream checkout, operations and reconciliation.
Risk-service handoffs
Coordinate separately scoped 3D Secure or risk events at the agreed point in the payment flow.
Integration & deployment
Integrate the gateway around the customer’s checkout and endpoint contracts.
Technical scoping covers API or component ownership, credentials, request IDs, idempotency, event delivery, test cases and operational support.
Request technical documentation →API integration
Map supported requests and responses to the customer’s existing checkout or platform services.
Hosted or embedded path
Evaluate supported components or redirects where required by the payment and data model.
Webhook and callback design
Define authentication, retries, ordering, duplication and reconciliation for asynchronous events.
Test and cutover
Exercise approved and failure paths in available test environments before controlled production release.
How it works
Carry an eligible transaction through the agreed gateway path.
The path returns payment information; it does not replace the authorization decision made by the relevant participant.
- 1
Accept. Receive a supported payment request from checkout or platform services.
- 2
Validate. Check agreed fields, identifiers and eligibility for the endpoint.
- 3
Send. Transmit the message to the contracted supported endpoint.
- 4
Return. Provide the response and any subsequent supported status events.
- 5
Reconcile. Relate identifiers and exceptions to the customer’s downstream operating records.
Illustrative scenario—not a customer case study
An online platform has different status handling for each payment endpoint.
Context
Checkout, support and finance teams use different identifiers and interpretations for failures and delayed responses.
ChallengeA payment can become difficult to trace between the customer experience, provider response and post-transaction operations.
Possible approach
Vellfi scopes a supported gateway message model, consistent transaction references, event delivery and exception handling for the contracted endpoints.
Potential operating effectTeams can follow the transaction, returned status and exception handoffs in one operating trail. Authorization, settlement speed and performance remain participant-dependent.
Responsibilities & availability
Keep checkout, gateway and regulated roles separate.
Customer
Owns checkout disclosures, lawful processing, endpoint contracts and its downstream use of payment results.
Vellfi
Provides the supported gateway integration, message handling and event behavior included in scope.
Endpoint participant
Performs its contracted processing, acquiring, authorization, settlement or other payment role.
Deployment scope
Confirms interfaces, fields, transaction types, markets, credentials, data roles, support and availability.
No universal endpoint or approval coverage
A gateway integration is available only for confirmed endpoints and does not guarantee that a transaction will be authorized, settled or free from fraud and disputes.
Next step
Review your checkout-to-endpoint message path.
Share the checkout channel, contracted endpoints, required events and current exception points without sending credentials or live card data.
FAQ
Global Payment Gateway: common questions
What does the Global Payment Gateway do?
It coordinates supported payment transaction messages between an agreed checkout or platform integration and contracted endpoints, then returns the supported statuses and events.
How is a gateway different from orchestration?
The gateway supplies endpoint connectivity and messaging. Orchestration applies policy across supported paths. They can be used separately or together.
Does Vellfi act as the acquirer or processor?
Not by virtue of this gateway page. Regulated and payment-participant roles depend on the deployment parties and their agreements.
Are hosted fields or redirects available?
Only where the proposed endpoint and technical scope support them. The integration model is confirmed during design.
How are delayed or unknown outcomes handled?
The deployment defines status mapping, timeouts, event delivery, reconciliation identifiers and the customer’s operational response.
Can 3D Secure be connected?
Potentially, as a separately scoped service where the gateway, channel, participants and 3D Secure deployment are compatible.
What is useful before a technical discussion?
Checkout channels, endpoint contracts, message formats, event requirements, transaction types, current errors and available test access are useful inputs.