In this guide: Payment gateways explained: how online payments work, popular gateways like Stripe and PayPal compared, fees and payouts, security and compliance, and…
When a customer clicks “Pay Now,” several distinct processes can occur: payment details are handled, authentication or authorization may be required, the transaction is processed and funds may later become available for payout. A payment gateway makes this possible. Choosing the right one affects your fees, conversions, and which customers can pay you.
Note: gateway availability, fees, and features vary by country and change over time. Always check current details for your business location.
Key players in an online card payment:
The flow:
Many modern providers (like Stripe and PayPal) combine gateway, processor, and merchant account into one service.
Stripe
PayPal
Square
Adyen, Checkout.com, and enterprise processors
Regional gateways
Many markets have strong local providers and payment methods — for example, in the Middle East, gateways supporting local cards and wallets (such as mada in Saudi Arabia, and providers like Moyasar, Tap Payments, HyperPay, PayTabs, and others). Local methods can be relevant, but any conversion effect requires evidence from the actual audience.
Platform gateways
Common fee types:
Payout schedules range from daily to weekly, with initial holding periods for new accounts. Some providers hold reserves for high-risk businesses.
Compare fees using your actual expected transaction sizes and customer locations.
Never store raw card numbers on your website. Protect your admin accounts with 2FA, and keep your store updated — card skimming malware targets outdated sites.
Ask these questions:
Many stores offer two or three options: a local gateway for local cards, an international card processor, and PayPal for international customers.
See how payment choices affect sales in Conversion Rate Optimization: 15 Quick Wins and set up your store with How to Build an Online Store With WooCommerce.
Further reading: OWASP Top 10 web security risks
Check the business location, entity, product category and supported settlement route with the provider. Customer country and merchant country are different conditions. A payment method that appears in a demonstration may not be available to your business or for the product you sell.
Record the official eligibility source and what remains unverified. Do not invent an address or change the business description to bypass restrictions. A rejected or unavailable provider is a constraint to handle through supported options, not a reason to misrepresent the merchant.
Authorization, capture, processing, success, settlement, payout, refund and dispute describe different stages. The exact states depend on the provider and method. A bank approving an authorization is not proof that funds have reached the merchant’s bank account, and a pending payment is not necessarily a failure.
Stripe’s payment lifecycle documentation explains relevant state transitions. PayPal separately documents authorization and capture. Use the actual integration’s model instead of applying one simplified card sequence to every payment method.
Use the provider’s current supported checkout, fields or platform extension rather than collecting sensitive card data through an ordinary custom form. Identify which components the merchant hosts and which the provider operates. A plugin logo in a directory does not establish that the installed version is supported or correctly configured.
Review compatibility with the store, checkout type and required methods. A custom implementation needs its own scoped design and maintenance owner. The WooCommerce launch guide covers the broader store journey, while payment verification remains a distinct responsibility.
Use the provider’s supported sandbox or test mode with controlled credentials and test details. Verify which environment the storefront and integration actually use before submitting a test. A label in a project note is not evidence that the active checkout cannot create a live transaction.
Do not charge real customers, issue refunds or alter payout settings merely to complete a tutorial. Financial actions require their own authorization. Record the cases tested and the environment so that a later reviewer does not mistake a successful sandbox payment for a live settlement result.
A customer can close a browser tab before returning to the store, and some methods complete later. Do not base fulfillment only on reaching a thank-you page. Stripe’s post-payment guidance describes handling payment events rather than relying solely on the browser return.
PayPal’s webhook overview likewise describes event notifications. Map the verified provider event to the intended order and fulfillment behavior. A public success URL that anybody can open is not proof that an order was paid.
A timeout does not necessarily mean that a payment operation failed. Repeating an operation without checking its state can create unintended duplicate work. Use the provider’s supported retry and idempotency design rather than repeatedly pressing the live payment action.
Stripe documents idempotent requests for supported operations. Webhook processing also needs to account for repeat delivery and the intended business state. Keep event identifiers and order relationships in a protected operational record rather than inventing a second order whenever a notification reappears.
Follow the provider’s supported verification process for incoming notifications. An endpoint receiving a message that says paid should not trust that claim merely because the payload looks plausible. Check the relevant signature, environment and account association through the official integration instructions.
The Stripe webhook documentation covers endpoint handling and verification. Keep secret keys and signing material out of public code, screenshots and general support conversations. Use appropriate access control and a maintained update process for the actual integration.
A hosted payment interface can change the merchant’s technical scope, but it does not remove every responsibility. The PCI Security Standards Council outsourcing FAQ explains that merchants retain duties when processing is outsourced. Review the actual implementation and required validation with the organization responsible for the compliance program.
Do not label a website PCI compliant merely because it has HTTPS or a familiar gateway plugin. Protect administrative access, maintain the site and understand shared responsibilities. This article provides implementation questions and sources; it does not perform an assessment or certify a business.
Use current official pricing for the merchant market, methods, transaction sizes and settlement currency. Separate processing, platform, conversion, cross-border, dispute and payout charges where applicable. A headline percentage cannot describe every transaction or the complete cost of an order.
Record pending availability, payout timing and any relevant reserve conditions from the actual provider. Do not treat an approved payment as cash already in the bank. A refund or dispute can change the commercial outcome, and fee treatment needs to be checked rather than guessed.
Exercise supported test cases for a decline, required authentication, pending method and delayed notification. Check the customer message, order state, stock, email and fulfillment consequences. A successful happy-path test does not establish that failure handling is safe or understandable.
Reconcile the store and provider records using appropriate transaction references. If they disagree, investigate the specific event and state rather than changing several statuses blindly. The website review guide provides complementary operating checks without replacing payment-provider evidence.
Imagine a buyer completes a supported payment flow but closes the tab before returning to the shop. This is an illustrative scenario, not a real Hostreta transaction. A store that relies only on the return page can miss its fulfillment trigger even though the provider later reports the relevant successful state.
The team inspects the protected provider and store records, verifies the notification and follows the integration’s supported recovery path. It does not ask the buyer to pay again before understanding the first transaction. The incident record separates payment state, order state and actual fulfillment.
In another test, a delayed method remains pending. The store displays an accurate next step and does not promise immediate delivery unless the business has deliberately chosen that risk. When the supported completion event arrives, the integration applies the intended state transition once rather than creating duplicate fulfillment.
Promotional recommendation: KAWEDMA website and store development services may be relevant for a scoped payment integration project. Confirm the exact supported gateway, test deliverables, account ownership, secret handling and handover. This recommendation does not claim that KAWEDMA is the payment processor or guarantees merchant approval, settlement or compliance.
No hosting affiliate purchase is required to understand payment gateways. If infrastructure becomes a separate project requirement, evaluate it independently. Keep payment credentials, financial decisions and transaction authorization within the responsible merchant’s controlled process.
Use a row for each scenario with the environment, expected state, actual observation and responsible owner. Include the integration version and the relevant provider documentation. Keep transaction references in an appropriately protected record, and remove sensitive customer details from general project notes or screenshots.
A useful first row covers the ordinary supported success path. Check the displayed amount and currency, the correct merchant account, the store order and the intended confirmation. Record the fact that a test environment was used. Do not label this result as proof of real funds arriving in a bank account.
A second row covers a supported decline or failed authentication. The customer should receive an understandable message and the store should avoid presenting the order as fulfilled. Verify the actual behavior rather than assuming that a gateway extension automatically provides a useful explanation for every error.
A third row covers a delayed result or interrupted browser return. Check the supported backend event and the reconciliation process. Record whether the store can reach the intended final state without asking for a second charge. Avoid creating a live failure merely to reproduce a tutorial scenario.
A customer can see a pending authorization and a captured transaction that need explanation, while a store can also accidentally create genuinely separate operations. Review the provider records and their definitions before describing either situation as a duplicate charge. Do not rely only on the wording of a screenshot or an application notification.
Use the merchant’s supported investigation and support process, with the appropriate authorization for any financial remedy. This guide does not issue refunds, void authorizations or alter bank details. The editorial lesson is to establish the actual state before taking another consequential action.
Name who owns the merchant account, integration configuration, operational monitoring and customer communication. A developer may maintain the code without controlling settlement decisions. A hosting provider may operate infrastructure without being responsible for approving merchant eligibility or resolving disputes.
Document where current integration instructions and protected credentials are maintained. Record how secrets are rotated through the authorized process and how an incident is escalated. Do not put live keys in a handover document that is shared more broadly than the systems they control.
Review the setup after a material checkout, gateway, extension or infrastructure change. Retest the affected journeys in the appropriate environment and record the observations. A previously successful test is useful history, not a permanent guarantee that every later configuration is correct.
Finally, keep the public description of the store accurate. Do not display an accepted-method logo before the actual supported checkout route is available. A familiar logo can create an expectation that the customer can use a method; the implementation should match the promise rather than relying on a decorative trust signal.
Keep unresolved issues visible at launch review. If an essential case cannot be verified, record the constraint and the owner’s decision instead of marking the whole integration complete. The final evidence should distinguish the customer interface, provider state, order state and actual fulfillment. That separation helps the next responsible person investigate a problem without assuming that every successful-looking page represents a completed commercial result.
We may earn a commission on purchases made through these links, at no extra cost to you.
Don’t miss the chance to participate in the biggest giveaway of this year.