Payment gateway
A payment gateway is the technical interface that receives and passes payment information between a business’s checkout and payment infrastructure. A provider may bundle it with processing and acquiring, but an approved authorisation is different from settled funds.
Prepared with AIContent updated
Gateway, processor and acquirer
The gateway passes payment details and results. The processor handles transaction messaging across the payment network, while the acquirer provides the merchant’s card-acquiring relationship. A single provider can combine these roles.
From gross payment to net receipt
Illustrative price: 2% plus £0.10 per payment, with no other fees.
All amounts use the same currency. Processing costs do not by themselves change the agreed subscription price or MRR.
From authorisation to settlement
For a card payment, a request is routed to the issuer for approval or decline. Authorisation can reserve funds. Capture, clearing and settlement are subsequent stages; use current provider status and bank reconciliation before concluding that money has been received.
Different payment methods have different lifecycles. A bank transfer does not necessarily follow the card-specific sequence.
Recurring payments and security
Subscriptions require a valid agreement and a correctly configured payment flow. Tokenisation can limit exposure to raw card data. Customer authentication, exemptions and subsequent-charge requirements depend on payment method, jurisdiction and provider configuration.
An external gateway does not remove the business’s responsibility for its integration and applicable security requirements. Use provider documentation to establish responsibilities and the actual PCI DSS scope.
Compare fees on the same basis
Compare percentage charges, fixed transaction fees, subscriptions, currency conversion, chargebacks and settlement terms. The example below uses chosen figures and is not a provider price list.
Payment fees are operating costs affecting margins and net receipts. They are not normally deducted from the subscription price in MRR, and are not automatically customer acquisition costs.
Declines need follow-up
Retries and messages can help where supported and where the decline reason permits another attempt. A failed payment is not automatically a cancellation. Track payment status, access and active subscription value separately.
Test the whole integration
Test initial payments, renewals, customer authentication, declines, refunds and repeated events. Use stable references and protection against duplicate charging. Reconcile gross payments, fees and net settlement so an integration fault is not hidden inside an MRR report.
Questions and answers
Is an authorised payment settled?
Not necessarily. Authorisation, capture and settlement are different stages. Check provider status and reconciliation.
Can a gateway prevent churn?
It can support collections and follow-up, but cannot guarantee retention. Measure failure reasons and actual subscription termination separately.
How much does a gateway cost?
Prices depend on the agreement, payment method, card type and market. Use current pricing and calculate the total for your own payment mix.
