Hosted checkout
Use supported hosted elements or payment pages where they fit the experience.
ExplorePayment gateway
Connect checkout decisions to the systems that fulfill and reconcile them.
Plan the gateway around customer experience, security scope, transaction data, refunds, recurring use, and downstream operations.
Core capabilities
A payment flow built around the work behind it
Tokenization
Reference stored payment credentials without exposing raw account data to every system.
ExploreWebhooks and reporting
Connect payment status to fulfillment, support, and finance workflows.
ExploreHow it fits
Start with the operating model
Northbridge’s fictional consulting approach begins with sales channels, transaction types, settlement needs, reporting ownership, and exception handling. The right configuration depends on those inputs.
01
Map browser, server, gateway, and processor responsibilities.
02
Define success, decline, timeout, and duplicate-submission states.
03
Document identifiers shared across systems.
04
Test refunds, disputes, and recurring use after launch.
Questions merchants ask
Before you compare providers
Is a gateway the same as a processor?
They play different roles, although a provider may package both. Ask who authorizes, routes, settles, stores tokens, reports transactions, and supports each part of the flow.
Should checkout depend entirely on client-side JavaScript?
Primary content and error states should remain accessible, while sensitive payment entry should follow the selected provider’s supported integration pattern.
Are integrations shown here available?
No. This is a fictional demonstration website and names no live product integrations.