Introduction

How VenPays works

VenPays separates dashboard management from payment execution.

Request path

Merchant Application
        │
        ▼
Merchant Backend
        │
        ▼
VenPays Payment API
        │
        ▼
Payment Provider

Use the Payment Engine with X-API-KEY for payment integrations. The dashboard is for merchant operations (keys, webhooks, reporting, links) and is separate from the Payment Engine contract.

Environments

Environment	Payment Engine
Sandbox	`https://init-vpay.venlabs.link`
Live	`https://merchant.venpays.com`

Each merchant has profiles for Sandbox or Live. Live access requires VenPays approval. Checkout links come back in API responses (payment_url / redirect_url).

Outcomes

Synchronous API response (for example a payment_url or native session)
Customer completes authentication on hosted checkout or Apple Pay
Final payment status is available to your systems
Optional webhook to your HTTPS endpoint
You confirm with payment status and your own order system

Source of truth

Fulfill orders from your backend using webhooks and/or authenticated status checks. Do not rely only on browser redirects.