How HellOOpass Payments Work
The three systems and lifecycle of a HellOOpass payment.
Every HellOOpass payment spans your backend, HellOOpass, and your customer — and always ends with server-side verification.
The three systems
Your backendHolds your secret API key, initializes payments, and verifies results.
HellOOpassPayment API and hosted checkout; notifies your backend by signed webhook.
Your customerPays in your app or via hosted checkout, then returns to your product.
Community context
In community deployments, members onboard with digital wallets and complete KYC verification before transacting with each other.
Payment lifecycle
Every payment follows the same sequence:
- Register your business and create a project.
- Get approved and access the Dashboard for your API credentials.
- Customer chooses to pay inside your app.
- Your backend initializes the payment and receives checkout details.
- Customer completes payment via hosted or in-app checkout.
- HellOOpass sends a signed webhook to your backend.
- You verify server-side; funds settle to your bank account.
Why server-side verification matters
Verify every payment server-side
Redirects can be spoofed — anyone can land on a success page without paying. Fulfill orders only after a verified webhook or a verification API call.
Environments
| Environment | Purpose | Base URL |
|---|---|---|
| Sandbox | Development and testing with simulated payments | https://sandbox-api.helloopass.example |
| Production | Live payments settled to your bank account | https://api.helloopass.example |