What Is a Payment Gateway? Provider Types, 2D/3D, Fees, and How to Identify One

Payment gateway basics: what it is and who uses it

A payment gateway is the link between a shop, a bank, and the card networks. It sends a payment ask and then waits for an answer. This helps your checkout stay fast and safe.

It acts like a traffic guard. It takes payment data, runs rules, and forwards it. Then it brings back “yes” or “no” for each charge.

Many teams use a gateway for more than routing. Some gateways also handle token use and fraud checks. That reduces risk and speeds up repeat payments.

• It sends a payment ask for approval.
• It returns the approval or decline result.
• It may add token use and fraud checks.
• It helps keep the checkout flow steady.

Payment gateway provider vs payment gateway company

A payment gateway provider is the firm that sells the gateway service. They offer tools, keys, and APIs. They may also offer a hosted pay page.

A payment gateway company is often the same thing. It can mean the firm that runs the gateway platform. Still, some firms wrap the gateway inside a bigger service.

So the key is the setup model. Ask if they give you a direct API, a hosted page, or both. Then ask who handles fraud work and claim work.

Term	What it usually means
Payment gateway provider	The firm that gives the gateway service
Payment gateway company	The firm that runs the gateway platform
Payment gateway account	Your merchant setup for that platform

What is a payment gateway account?

A payment gateway account is how you join a gateway to take pay. It holds your merchant setup and access keys. It also sets which pay types you allow.

Without that account, your checkout can’t talk to the gateway. You also can’t use a hosted pay page in live mode. You usually must pass a review step first.

After go-live, you manage jobs like refunds and status checks. You also watch logs for auth success and fail rates. That is where teams find why a pay went wrong.

1. Send business docs and set up your merchant profile.
2. Connect your checkout in test mode with test keys.
3. Switch to live mode after your review.
4. Track auth, capture, and settle status.

2D gateway vs 3D gateway: what they are and why they exist

A “2D gateway” can mean a two step security flow. In many setups, it handles domain level routing. Still, the exact meaning can vary by vendor.

A “3D gateway” usually points to 3D Secure. 3D Secure is an extra check for card pay. It often asks the buyer to prove they own the card.

During checkout, the gateway may start the 3D flow. The buyer then completes a challenge. After that, the gateway sends the result back.

• 3D gateway: usually 3D Secure extra buyer check.
• 2D gateway: vendor dependent two step security routing.
• Both aim to cut fraud and raise clean approvals.

Test edge cases like buyer closes the check window. Also test timeouts and failed steps. Then fix your UI for those paths.

How to find out what payment gateway a website uses

You can often spot a gateway by checking checkout page calls. Look at script hosts and outside domains in network calls. Focus on where payment asks are sent.

In most card flows, the browser sends calls to a gateway host. Open developer tools and watch requests around the pay step. Filter for words like “authorize” or “payment.”

If the page redirects to a third party pay page, that host is a clue. You can also scan page source for gateway scripts. Use both views to avoid false hits.

1. Start a pay attempt on the checkout page.
2. Open developer tools and go to Network.
3. Filter for payment, authorize, or 3ds calls.
4. Find the external host in the request URL.
5. Match that host to a known gateway vendor.

For proof, ask the shop team or check their terms. Some list the processor or the gateway in policies.

Payment gateway fees: what you pay and how it is billed

A payment gateway fee is what the provider charges to use the link. Fees can be flat, per charge, or both. Some are a percent of the sale.

There may also be extra fees for tools. This can include risk rules and hosted pay pages. Some plans bill for each auth even if it fails.

To plan your costs, request a full fee list. Then build a cost model using your real order size. Also check currency fees and claim fees.

Fee type	What it usually means
Per charge	A fee for each payment attempt or settle
Percent of sale	A variable fee based on the order value
Setup fee	A one time charge for account and setup
Tool add ons	Extra fees for risk, hosted pages, or retries

Compute an effective rate. Use your approval rate and average basket. That shows your true cost per good sale.

AuthNet gateway billing, AuthNet gateway, Airpay, and BillDesk payments

AuthNet gateway billing means how AuthNet charges for pay work. Plans can split fees by auth and settle steps. Your exact bill depends on your plan terms.

AuthNet gateway means a gateway service for card pay. It sends pay asks and gets auth results. Some setups also run 3D Secure, based on your setup.

Airpay payment usually means Airpay pay services for merchants. What is airpay payment gateway? It means the Airpay gateway you plug in for pay. Like others, it offers keys, routing, and status pages.

BillDesk payment usually points to BillDesk pay services. It is often used for bill pay and collections. The meaning depends on whether you use their hosted flow or an API.

No matter the brand, ask clear billing questions. What fees hit auth, and what fees hit settle? Do you pay for failed tries? How are chargebacks and disputes priced?

Choosing the right gateway provider for your use case

The best provider fits your checkout plan and risk needs. If you want quick setup, hosted pay can help. If you need custom UI, an API can fit better.

For fraud work, check what signals they use. Some rely on 3D Secure steps and rules. Others add device data and score models. Then ask how you can tune those rules.

For scale, test burst load in sandbox mode. Check webhook timing and retry logic. Also test what happens after timeouts and network dips.

• Pick hosted page or direct API to match your UI needs.
• Confirm security support for 3D Secure flows.
• Review fees and your cost per good sale.
• Test retry, webhooks, and timeout behavior.

When your gateway and risk steps match, payments fail less. That cuts support work and boosts buyer trust.