Direct Integration
Your checkout. Your design.
Build a payment interface that matches your platform, with greater control over its layout and customer journey.
CHOOSING YOUR INTEGRATION
Two ways to accept payments. Choose what fits your platform.
Use Herepay's ready-made checkout with Payment Link, or build your own payment interface with Direct Integration. The right choice depends on how much control you need and how much you want to build.
Payment Link
Ready-made checkout. Less to build.
Create a payment link through the API and send customers to Herepay's hosted checkout.
Both options use APIs. Payment Link means Herepay provides the checkout page, so your team has less interface work to do.
What's the difference?
Payment interface
Direct Integration
Your own UI, built within your website or app
Payment Link
Standard Herepay-hosted checkout template
Design and branding
Direct Integration
Greater control over layout, styling, and how payment fits your brand
Payment Link
Checkout follows Herepay's template and available settings
Customer journey
Direct Integration
Design the steps before payment and connect them closely to your platform
Payment Link
Prepare the payment in your system, then redirect customers to Herepay's checkout
Checkout development
Direct Integration
Your team builds and maintains the payment interface
Payment Link
Herepay provides the hosted payment interface
API implementation
Direct Integration
Connect your custom checkout to the relevant payment APIs
Payment Link
Call the Payment Link API and use the returned checkout URL
Business workflow
Direct Integration
Suitable for closely connecting checkout to your own registration, membership, or ordering flow
Payment Link
Suitable when your existing flow can hand over to a hosted checkout
Development effort
Direct Integration
More implementation and testing
Payment Link
Less checkout development, with integration testing still required
Best fit
Direct Integration
Platforms needing a tailored checkout experience
Payment Link
Teams wanting a straightforward hosted checkout
DIRECT INTEGRATION
Direct Integration: a checkout designed around your platform
In this example, the membership details, amount, and bank selection are presented in SAHOCA's own interface. The payment experience follows the organisation's design and membership journey.
- Present payment within your own branded interface.
- Arrange customer details and payment steps around your workflow.
- Take responsibility for building and maintaining the checkout UI.
- 1Customer reviews payment in your interface.
- 2Your backend initiates payment through Herepay.
- 3Customer completes the required bank or provider authorisation.
- 4Your system confirms the payment result.
A custom checkout can still redirect customers to their bank or payment provider for authorisation.
PAYMENT LINK
Payment Link: let Herepay handle the checkout page
Your system prepares the payment details and requests a payment link. Customers open the returned URL and complete the checkout using Herepay's standard interface.
- Generate checkout URLs through the API.
- Use Herepay's ready-made payment interface.
- Build less checkout UI while connecting payment results to your system.
- 1Your backend requests a payment link.
- 2Herepay returns the checkout URL.
- 3Customer opens Herepay's checkout and completes payment.
- 4Your system confirms the payment result.
Both options require payment-result handling
Whichever integration you choose, confirm every payment according to the documentation. A customer returning to a page is not proof of payment on its own — rely on the server-side result your system receives and verifies. Keep credentials and authenticated payment requests on your backend, never in the browser.
Which should you choose?
Choose Direct Integration if…
You need a checkout that follows your own design and workflow, and your team can build and maintain it.
Choose Payment Link if…
You want a ready-made checkout and prefer to spend less development time building the payment interface.
Start with the experience your customers need, then choose the integration that supports it.