Payment & business solution
Connect ecommerce, invoice, recurring, mobile, or virtual-terminal payment entry to a compatible processor with clear token, security, reporting, and support behavior. Compare merchant fit, implementation steps, limitations, and complete-cost variables before selecting a provider.
Plain-language definition
A payment gateway securely transmits payment requests and responses between a checkout application and compatible payment services.
Day-to-day workflow
The checkout collects payment through the approved interface, the gateway tokenizes or transmits it, returns authorization state, and supplies identifiers used for capture, void, refund, recurring activity, and reconciliation.
Implementation
The implementation requirement is specific: processor compatibility, hosted versus direct collection, token portability, recurring billing, fraud controls, supported payment types, webhooks, virtual terminal, reporting, user permissions, and support. AMP can document dependencies and questions, but the merchant and applicable providers must confirm compatibility, account approval, responsibilities, testing, training, and support in writing.
Complete cost
gateway monthly and per-transaction fees; processing; token or account updater services; fraud tools, development, devices, support, chargebacks, and termination Compare recurring, transaction-based, one-time, optional, and exit costs separately. A proposal is incomplete if it omits equipment ownership, software term, support scope, or cancellation obligations.
Failure planning
A gateway can authorize a transaction while the order system misses the response; token lock-in, duplicate retries, weak permissions, hidden card updater fees, or separate support teams can create operational gaps.
Decision guide
Compare gateway and processor as a complete pair. A lower gateway price may not support required tokens, connectors, payment types, or reporting; an all-in-one platform may simplify support but reduce portability.
Know before you decide
Complete-cost view
Only a written proposal and agreement can establish actual pricing and terms.
Owner questions
Confirm account and processor compatibility, supported payment types, capture and settlement behavior, tokens, recurring billing, refunds, webhooks, virtual terminal, fraud tools, reporting identifiers, permissions, environments, and support ownership.
The order system may miss the response, fail capture, or store an ambiguous state. Reconcile authoritative gateway and processor records, use idempotent recovery, and test webhook delay or loss before production.
Tokens may be provider-specific and migration can require consent, technical work, or may not be available. Ask who owns stored customer references, what exports exist, and how recurring payments continue during transition.
Monthly and per-transaction fees, account updater, token vault, fraud tools, virtual-terminal users, development, certification, support, chargebacks, processing, and termination can matter. Compare the gateway and processor as one operating stack.
Published 2026-08-03 · Modified
Primary standards-body background for merchant payment-data security responsibilities. Source reviewed .
Primary nonprofit standards project for API threat and control review. Source reviewed .
Approved first-party discovery guide for technical and commercial integration scope. Source reviewed .
Share the current process, the constraint you need to remove, and the systems that must remain. AMP can return a scoped next step without treating a headline rate or feature list as a complete recommendation.