When you buy something online, how does your card info get to the bank? There are basically two ways:
The first way is via a hosted payment page – you’re on a shop’s website, click “pay,” and suddenly you’re on a different website – let’s say PayPal or Google Pay – to type in your credentials. Then you are sent back to the original shopping website after paying.
The host-to-host payment page, a second option, works differently: you never leave the shop’s website. The customer stays on the merchant’s website, and the payment form appears fully integrated into the checkout experience. You type your card details into a form that looks like part of the shop – because it is. Behind the scenes, the shop’s server automatically sends your card data directly to the bank’s server. You just see “payment successful.”
Why does it matter?
Imagine you’re running an online store. Every day, thousands of customers fill their carts, hit checkout, and enter their card details. That moment – those few seconds between “pay now” and “order confirmed” – is where you either keep the customers or lose them.
The regular hosted payment page is completely fine; this is how many newcomers operate – not many people know your website, and redirecting to PayPal, Google Pay, or any big payment provider’s checkout page makes you seem more reliable.
On the other side of the story: the more scale and transaction volume, the more viable the host-to-host payment page becomes. Want to know why? Read on to find out!
Open an account
in Genome online
The mechanics: how host-to-host (H2H) works
At its core, an H2H payment integration eliminates the client-side redirect that defines the traditional hosted payment page model. In other words, a host-to-host payment page requires a company’s backend infrastructure for its implementation.
The data flow looks like this:
The customer enters payment details – card number, expiry, CVV – directly into a form rendered within the merchant’s own front-end environment.
Upon submission, the merchant’s server captures this data and transmits it to the payment provider’s server via a secure payment API using encrypted, server-to-server communication.
The payment provider processes the transaction, applies fraud screening, communicates with the card network and issuing bank, and returns an authorization response, all in real time.
The customer experiences a seamless, uninterrupted checkout. They never leave the merchant’s URL. There is no redirect, no loading screen on a third-party domain, no visual discontinuity.
Such an uninterrupted transaction model distinguishes a host-to-host payment page from a hosted payment page and from every redirect-based alternative. The merchant’s server acts as a transparent conduit between the customer-facing form and the payment provider’s processing infrastructure. The result is a checkout experience that is indistinguishable from any other interaction on the merchant’s platform.
The H2H payment integration relies on well-documented API endpoints, typically RESTful, that handle tokenisation, 3DS authentication, authorisation, capture, and refund operations.
You could take a look at our host-to-host API integration code examples for a general understanding of how it would work.
Host-to-host vs. hosted payment page (HPP)
Understanding the structural differences between H2H vs. hosted payment pages would help you select the option you need:
Host-to-host | Hosted payment page | |
User experience | Seamless. The customer doesn’t leave the merchant website | Redirect-based. The customer briefly leaves the website |
PCI DSS scope | High. The merchant is responsible for cardholder data security | Low. The provider handles the compliance burden |
Checkout customisation for e-commerce | Full control. The complete checkout customisation for e-commerce companies | Usually template-based. There are limited branding options |
Integration complexity | High. It requires dedicated technical resources and secure API setup | Low. Allows rapid deployment with minimal development effort |
Conversion optimisation | High. It eliminates redirect abandonment entirely | Moderate. The redirect can introduce friction at the critical moment |
Best fit | High-volume merchants with technical teams and bespoke UX requirements | SMBs or merchants prioritising a fast launch |
The distinction is not simply technical, it is strategic. A hosted payment page is purpose-built for speed of deployment and minimal compliance overhead for merchants. PCI DSS obligations for merchants using a hosted payment page are significantly reduced because the payment provider handles it.
For merchants launching quickly, testing new markets, or operating at modest transaction volumes, a hosted payment page is usually the first choice. It is simpler to handle.
For example, Genome merchant services currently include a robust hosted payment page designed for businesses that want a reliable payment environment without managing the extensive PCI DSS compliance requirements.
However, as transaction volumes grow and the cost of suboptimal conversion rates compound, the architectural limitations become a burden, and the time for the H2H vs. hosted payment page decision will eventually come.
Why high-volume merchants prefer host-to-host
The business case for the host-to-host payment page model is grounded in three interconnected advantages that scale in proportion to transaction volume:
Conversion rate optimisation (CRO)
Every redirect introduces friction. Research across e-commerce sectors consistently shows that checkout abandonment rates spike at the point of redirection to the payment provider. It is a moment when the customer is suddenly confronted with an unfamiliar URL, a different visual design, or simply the cognitive disruption of leaving a trusted environment. For a merchant processing 50,000 transactions per month, even a 2% reduction in abandonment represents thousands of recovered transactions.
Host-to-host payment page reduces this friction significantly. The payment form is native to the merchant’s environment. There is no redirect, no domain change, no visual discontinuity. High-volume payment processing at enterprise scale demands that every percentage point of conversion is engineered, not assumed.
Brand consistency and checkout customisation for e-commerce
Ask yourself: would you buy something on Amazon if you were redirected to another page after pressing the ‘pay’ button? The bigger the company is, or the bigger it wants to be, the higher the expectations towards it.
With a host-to-host payment page, the merchant retains 100% control over the UI and UX of the payment experience. Typography, colour palette, layout, error messaging, field validation behaviour, progressive disclosure patterns: every element remains within the merchant’s design system. This is not merely an aesthetic preference. Brand consistency at the point of payment directly influences customer trust, which in turn influences completion rates.
Even the most flexible hosted page is still someone else’s template. For enterprise brands where the checkout experience is an extension of the product itself, this constraint is architecturally unacceptable. Another thing that companies that deal with high-volume payment processing need to consider.
Advanced data analytics and behavioural insight
Because the payment form exists within the merchant’s environment, H2H payment integrations enable merchants to observe user behaviour throughout the transaction flow. Event tracking, field-level interaction analysis, drop-off attribution, session recording, A/B testing of form layouts: all of these capabilities are natively available to merchants using the H2H model.
Plus, with an HPP, the redirect can sever the analytics chain. You can measure that a customer reached the payment page, but you usually cannot measure how they behaved on it.
High-volume payment processing demands visibility at every stage of the funnel, and H2H integration provides it.
The compliance hurdle: PCI DSS for H2H
The most consequential trade-off of the H2H model is its requirement for PCI DSS compliance. Because the merchant’s servers handle raw cardholder data – even momentarily, even in transit – they fall within the scope of the Payment Card Industry Data Security Standard at a higher level than redirect-based integrations.
PCI DSS compliance for merchants using HPP is not entirely a problem. It’s serviceable, and this is not a reason to avoid H2H. In addition, you need to select a PCI DSS-compliant payment service provider.
Genome provides secure payment API environments specifically designed to handle this data safely, with encrypted transaction protocols, tokenisation capabilities, and infrastructure that supports merchant compliance programs. The goal is not to eliminate the merchant’s PCI DSS obligations if they use host-to-host integration, but to provide the security foundations that will help you deliver the best and safest customer experience. Not to mention, Genome’s very own host-to-host payment pages will be available soon.
Genome’s evolving merchant ecosystem
Genome merchant services are built around the principle that payment infrastructure should scale with the businesses that depend on it. Just see for yourself:
Business wallets. Our business wallets include multi-currency accounts that allow you to hold 12 currencies: EUR, USD, GBP, PLN, CHF, JPY, CAD, CZK, HUF, SEK, AUD, and DKK. Exchange these currencies between accounts, use them for international transfers (SWIFT), and link most of these currencies to your Genome-issued virtual and physical Visa cards. Additionally, once our card payment processing is available, you will be able to accept payments from customers in EUR, USD, and GBP.
IBANs. We offer a dedicated IBAN issuance for business accounts, enabling professional-grade financial operations and easy access to SEPA zone-based transfers and payments.
SEPA Instant and Credit Transfers. Both of these transfer options are available inside Genome. What’s more, you can also accept direct A2A payments from customers via SEPA. All thanks to our instant bank payments feature, which uses Open Banking capabilities to allow customers to use Pay by Bank. The feature is crucial for European merchants requiring same-day (and even instant with SEPA Inst) settlement and cash flow optimisation.
Hosted payment page. Genome’s current checkout solution provides a fast-deployment, low-compliance-overhead payment page with professional reliability and conversion-optimised design.
These capabilities form a coherent stack for merchants at various stages of their payment infrastructure maturity. For many businesses, Genome’s HPP remains the optimal solution, delivering high-quality checkout experiences without the compliance complexity of a full H2H deployment.
However, for merchants who have outgrown standard redirect solutions and require total architectural freedom over their checkout environment, Genome is developing an advanced host-to-host payment page solution.
This upcoming H2H integration is designed to be the final piece for enterprise-scale operators, offering a secure payment API connectivity, deep customisation capability, and a secure environment for PCI DSS-compliant cardholder data handling.
With the host-to-host payment page in the works, Genome merchant services are set to become a complete solution for high-volume payment processing at every level of technical sophistication.
Open an account
in Genome online
Is H2H right for your business?
The host-to-host model is not universally appropriate, and the decision to invest in H2H payment integration should be grounded in an assessment of three criteria:
Transaction volume. The host-to-host payment page delivers the highest ROI at scale. The conversion improvements, analytics capabilities, and brand consistency advantages compound as transaction volumes increase. For merchants processing fewer than 1,000 transactions per month, the complex investment may not yet be proportionate to the return.
Beyond 50,000 monthly transactions – the economic case for H2H becomes increasingly compelling. The high-volume payment processing requires this precision.
Technical resources. A H2H payment integration is a significant engineering undertaking. It requires a team with experience in secure API development, payment protocol compliance, tokenisation architecture, and ongoing maintenance of the integration layer.
Organizations without dedicated technical teams may prefer hosted payment solutions.
Checkout customization for e-commerce. If your business requires deep checkout customization for e-commerce, H2H provides the flexibility to build payment flows tailored to specific product experiences.
If the payment form is expected to be indistinguishable from the rest of your product, then H2H is the only model that delivers this without compromise.
For businesses where e-commerce checkout customisation is a strategic priority, and the analytics chain must remain unbroken throughout the payment flow, the H2H model is architecturally the correct choice.
Conclusion
As online businesses scale, their payment infrastructure often needs to evolve alongside them.
H2H vs. hosted payment page is not a dilemma but a stage of business growth – many companies start with a hosted payment page due to its simplicity and cost.
A host-to-host payment page provides maximum control over the checkout experience, deeper data visibility, and the ability to optimize high-volume payment processing environments. At the same time, it introduces additional technical and compliance responsibilities, particularly around PCI DSS compliance for merchants.
For many organizations, the transition from hosted payment pages to H2H payment integration becomes a natural step once operational scale and technical capacity increase. Not to mention, the need for checkout customization for e-commerce.
Scale your payments with a partner that grows with you. Explore Genome merchant services today and stay tuned for upcoming advanced host-to-host integration capabilities designed for high-volume merchants.
