Projects

Payment Gateways: 10 Essential Checks for a Safer Store

Payment Gateways – Payment Gateways Explained: Stripe, PayPal and More

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.

How payment gateways work

Key players in an online card payment:

  • Customer — pays with a card or wallet.
  • Merchant — you.
  • Payment gateway — securely captures and transmits payment data from your website.
  • Payment processor — routes the transaction between banks and card networks.
  • Card networks — Visa, Mastercard, etc.
  • Issuing bank — the customer’s bank that approves or declines.
  • Acquiring bank — your bank (or the provider’s banking partner) that receives funds.

The flow:

  1. Customer enters payment details at checkout.
  2. The gateway encrypts and sends them to the processor.
  3. The card network forwards the request to the issuing bank.
  4. The bank approves or declines (checking funds and fraud signals, sometimes asking for 3D Secure verification).
  5. The integration receives the relevant state; some methods remain pending or require further action.
  6. Settlement and payout are later stages governed by the provider and applicable payment method; they are not identical to browser confirmation.

Many modern providers (like Stripe and PayPal) combine gateway, processor, and merchant account into one service.

Popular gateways compared

Stripe

  • Developer-friendly, supports cards, wallets (Apple Pay, Google Pay), and many local payment methods.
  • Review the exact supported product for subscriptions, platforms or a custom integration.
  • Available in many countries (check yours).

PayPal

  • Review the merchant and customer methods supported by the actual PayPal product and market.
  • International availability and settlement need to be checked for the actual business.

Square

  • Strong for businesses with both physical and online sales (POS integration).

Adyen, Checkout.com, and enterprise processors

  • Suitable for larger businesses with high volume and global needs.

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

  • Shopify Payments and WooPayments integrate directly into their platforms.

Fees and payouts

Common fee types:

  • Per-transaction fee: percentage of the transaction plus a fixed amount (varies by provider and country).
  • International card and currency conversion fees.
  • Chargeback fees when customers dispute payments.
  • Monthly or setup fees (less common with modern providers, but some enterprise or regional gateways charge them).
  • Payout fees for certain transfer methods.

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.

Security and compliance

  • PCI DSS: security standards for handling card data. The integration affects scope, but outsourcing does not eliminate merchant responsibilities. Review the actual implementation with the responsible compliance-accepting entity.
  • SSL/HTTPS: mandatory — see What Is SSL?.
  • 3D Secure / Strong Customer Authentication: authentication mechanisms and requirements that depend on the transaction, region and provider; do not assume every flow carries the same liability treatment.
  • Fraud tools: risk scoring, address verification, and rules to block suspicious transactions.
  • Tokenization: uses provider-managed references in supported integrations; review the actual storage and access boundaries.

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.

Choosing for your market

Ask these questions:

  1. Is the gateway available for businesses in your country, and can it pay out to your bank?
  2. Which payment methods do your customers prefer? Local cards and wallets, international cards, PayPal, bank transfers, buy-now-pay-later, or cash on delivery?
  3. Does it integrate with your platform (WooCommerce, Shopify, custom app)?
  4. Does it support your business model — subscriptions, marketplaces, digital goods?
  5. Currencies: can you charge and settle in the currencies you need?
  6. Fees and payout speed for your transaction profile.
  7. Support quality and documentation.

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

Key Takeaways: Payment Gateways

  • Payment gateways securely connect your checkout to banks and card networks.
  • Stripe and PayPal are popular global options; local gateways matter for local customers.
  • Compare fees, payout schedules, and supported methods for your market.
  • Use hosted checkout fields to reduce PCI burden and enable 3D Secure.
  • Offer the payment methods your customers actually use.

10 essential payment integration checks

1. Confirm merchant eligibility before comparing fees

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.

2. Define the payment lifecycle

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.

3. Choose the supported integration boundary

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.

4. Keep test and live environments separate

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.

5. Verify backend evidence before fulfillment

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.

6. Handle retries and repeated events safely

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.

7. Verify event authenticity and protect secrets

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.

8. Evaluate security scope without claiming automatic compliance

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.

9. Compare actual fee and payout scenarios

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.

10. Test failures and reconcile records

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.

A hypothetical checkout incident

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.

Relevant implementation help

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.

Payment: distinguish the lifecycle stages
Payment: distinguish the lifecycle stages. Original explanatory diagram.
Payment: verify the integration evidence
Payment: verify the integration evidence. Original explanatory diagram.
Payment: retain merchant responsibilities
Payment: retain merchant responsibilities. Original explanatory diagram.

Prepare a test record that another developer can review

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.

Investigate a reported duplicate carefully

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.

Keep a clear handover boundary

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.

Z
zasma171

Writes for Hostreta about the topics covered in this article.

Comments (0)

Your email address will not be published. Required fields are marked *

Ad
Affiliate links
Tools we recommend
Protect Your Website with Automated Daily Backups
$2.09
Get it
the easiest way to manage all of your social media accounts
$29
Get it
Starter Website Get online, properly
$249
Get it
google workspace Business Starter
$3.75
Get it
Nord Vpn Cybersecurity. Built for Everyday Use
$8.99
Get it
More hosting options · affiliate
AI SiteBuilder
View plans
AI Application Hosting
View plans
Shared Hosting
View plans
Reseller Hosting
View plans
Managed WordPress · Rocket.net
View plans
Unmanaged VPS Hosting
View plans
Managed VPS Hosting
View plans
Virtual Dedicated Servers
View plans

We may earn a commission on purchases made through these links, at no extra cost to you.

Ad
Ad

$ top hosting picks

affiliate
★★★★★

KAWEDMA Website Services

See optionsCheck current plans and terms
  • Explore website setup services
  • Choose a scope that fits your project
  • Confirm features with KAWEDMA
Explore KAWEDMA →
affiliate link · we may earn a commission
★★★★★

Managed WordPress Hosting

See plansCurrent terms on provider website
  • Managed hosting for WordPress
  • Powered by Rocket.net
  • Compare current plan specifications
View WordPress plans →
affiliate link · we may earn a commission
★★★★★

AI SiteBuilder

See plansCheck current offer and renewal terms
  • Explore AI-assisted website creation
  • Review included tools and features
  • Choose a plan for your project
Explore SiteBuilder →
affiliate link · we may earn a commission

Never miss a new article

Join thousands of developers and builders getting a weekly digest of the best tech articles.