A payment module is the code that plugs a payment method into your shop's checkout. It creates the charge, sends the customer to pay, and tells your store when the money has arrived. It is not a payment processor: the module is software you install, while the processor is the licensed party that moves the money. For bitcoin you can skip the processor entirely and point the module at a node you control.
TL;DR:
- A payment module is checkout software, not a financial institution. A processor, gateway and module are three separate layers, and you can usually buy only the one you need.
- Building a payment processor means bank sponsorship, compliance audits and licensing. Building a module for one platform is a few weeks of developer work.
- Procure-to-pay tools like Coupa Pay are buyer-side systems for paying supplier invoices. They are a different category from a storefront payment module.
- Payment plans (deposits, installments, subscriptions, milestones) each demand different things from a module. Bitcoin is push-based, so plan around one invoice per payment.
- A self-hosted bitcoin module has no percentage fee, but refunds are manual and you carry the wallet backup. A flat-fee managed host removes the server work, not those responsibilities.
Table of Contents
- What Is a Payment Module? Module, Gateway and Processor Compared
- How to Create a New Payment Processor, and Why You Probably Want a Module Instead
- Building a Payment Module for Your Shop: Five Parts That Decide Whether It Works
- How Coupa Pay Works, and Why It Is a Different Kind of Payment Module
- Payment Plan Examples, and What Each One Demands From Your Module
- What a Bitcoin Payment Module Changes: Confirmations, Fees and Finality
- Choosing a Payment Module: Five Checks Before You Install
- Get Bitcoin Checkout Wired Into Your Shop Without Running a Server
- Frequently Asked Questions
- Sources
What Is a Payment Module? Module, Gateway and Processor Compared
"Payment module" is the term PrestaShop and WHMCS use for a piece of software that adds a payment method to a store. WooCommerce calls the same thing a gateway plugin, and Magento calls it a payment method extension. The job is identical across all of them: show the option at checkout, create a charge or invoice, hand the customer off to pay, and update the order when payment is confirmed.
Confusion starts because three different layers get called "the payment thing." Here is how they separate:
| Layer | What it does | Who runs it | Example |
|---|---|---|---|
| Payment module | Adds the method to checkout, creates invoices, updates order status | You install it in your shop | A gateway plugin or a PrestaShop payment module |
| Payment gateway | Securely passes transaction data between your shop and the processor | A provider, via API | A hosted card payment page |
| Payment processor | Moves funds through card networks and banks | A licensed financial institution | An acquiring bank or its technical partner |
| Bitcoin node and invoice server | Does the gateway job and checks payments against the blockchain itself | You or a host you pay | BTCPay Server |
The practical consequence: when someone says "we need a payment module," ask which layer they mean. Installing a module changes your checkout. It does not change who holds your money, who approves you, or who can freeze your balance. Those are properties of the layer behind it.
How to Create a New Payment Processor, and Why You Probably Want a Module Instead
You can create a new payment processor, but it is a financial-services project, not a software project. For card payments you need sponsorship from an acquiring bank, registration with the card networks, and validation against the PCI Security Standards Council's PCI DSS, which applies to any entity that stores, processes or transmits cardholder data. In the United States, moving money for others also triggers money-transmitter licensing that varies by state. Expect that work to be measured in many months and a legal budget, before a single transaction clears.
That is why the obvious answer is usually wrong. If your goal is "accept payments in my shop," you do not need to create a processor. You need one of three cheaper things:
- A module on top of an existing processor. Fastest route, but you inherit that processor's percentage fee, approval process and ability to hold funds.
- A custom module for your own platform. Right when no existing module handles your workflow, such as a deposit-plus-balance flow or an unusual order lifecycle.
- A bitcoin node with a module. The Bitcoin network is the settlement layer, so there is no processor to create or apply to. Your software watches the chain and marks invoices paid.
I would pick the third for any merchant whose customers already hold bitcoin, and the first for everyone else. Building a processor only makes sense if payments are your product.
Building a Payment Module for Your Shop: Five Parts That Decide Whether It Works

Writing a module is mostly plumbing, and the plumbing is where bugs cost money. Each platform has its own entry point: WooCommerce extends its WC_Payment_Gateway class, and PrestaShop modules extend PaymentModule. Whatever the platform, five parts need to be right:
- Checkout presentation. The method must appear with a clear label, and only when it applies (currency, cart total, country).
- Charge or invoice creation. The module calls your payment backend with the order total, currency and a unique order reference.
- Customer hand-off. Redirect to a hosted payment page, or embed one. Hosted pages keep sensitive data off your server, which is why PCI guidance favors them for cards.
- Callback handling. The backend notifies your shop when status changes. Verify the signature on every callback, and make the handler idempotent, because the same notification can arrive twice.
- Order state and refunds. Map each payment status (pending, paid, expired, underpaid) to an order status, and decide what a refund actually does.
Platform specifics matter more than people expect. If you are on WooCommerce, our WooCommerce setup walkthrough covers the configuration order. On Magento, check the Magento 2 plugin buyer's guide before installing anything. Shopify handles custom payment methods differently from open-source carts, which is covered in the Shopify integration for bitcoin article.
How Coupa Pay Works, and Why It Is a Different Kind of Payment Module
Many people searching "payment module" land on procure-to-pay software, so here is the short version. Procure-to-pay is the buyer-side sequence of requisition, approval, purchase order, goods receipt, invoice approval and payment. Coupa is a spend-management platform that runs that sequence, and Coupa Pay is its payments capability: once a buyer approves a supplier invoice, the platform can pay it by methods such as virtual card, bank transfer or check, depending on how the buyer has set it up.
Suppliers interact through the Coupa Supplier Portal, which is where you see purchase orders, submit invoices and check invoice status. If you are a supplier looking for Coupa payment status, login help or a phone number, use the link in your buyer's invitation email or the support pages on coupa.com. Do not call numbers from third-party listings. Fake "payment support" lines are a known route for invoice fraud.
The distinction that matters: Coupa Pay pays out bills for a company. A storefront payment module collects money from customers. Different direction, different user, different risk. If you sell to large buyers, you may end up with both: a storefront module for retail and a supplier portal account for enterprise invoices.
Payment Plan Examples, and What Each One Demands From Your Module
Payment plans are where simple modules break. Here are the common structures and what each needs:
| Plan | How it works | What the module must support | Bitcoin note |
|---|---|---|---|
| Pay in full | One charge at checkout | Basic invoice and callback | Works natively |
| Deposit plus balance | e.g., 30% now, 70% before shipping | Two invoices tied to one order | Works well; each payment is a separate invoice |
| Fixed installments | e.g., four payments, two weeks apart | Scheduled invoice generation, partial order status | Customer must approve each payment manually |
| Subscription | Charge every cycle | Stored credentials or recurring invoices | Bitcoin is push-based, so you send a fresh invoice each cycle |
| Milestone payments | Pay as project stages complete | Manual invoice triggers, API access | Good fit with API-created invoices |
| Net-30 terms | Deliver now, invoice later | Invoice records, reminders | Invoice generation works; credit risk is yours |
The last column is the honest trade-off. A card on file lets a merchant pull money without the customer doing anything. Bitcoin does not work that way: the customer has to send each payment. That makes bitcoin a poor fit for "set and forget" subscriptions and a strong fit for deposits, milestones and one-off orders. I would design a bitcoin payment plan around deposit-plus-balance and leave auto-billing to cards.
What a Bitcoin Payment Module Changes: Confirmations, Fees and Finality

A bitcoin module behaves differently from a card module in three ways you should know before choosing.
Settlement is on-chain. The Bitcoin developer documentation covers how merchants should treat confirmations, and the key number is time:
Bitcoin blocks arrive about every 10 minutes on average, so six confirmations means roughly an hour of waiting.
Most shops do not wait an hour. Low-value orders are commonly released at zero or one confirmation, and Lightning payments settle in seconds. Higher-value orders deserve more confirmations. A good module lets you set this per store or per product.
The fee model is flat or zero. BTCPay Server is free, open-source software that takes no cut of your sales. Compare that with a typical 2.9% plus 30 cents card rate: on a $50 order that is $1.75. The math on a flat hosting fee is simple:
At 2.9%, a $29 monthly flat fee equals the card fee on about $1,000 in sales, so every dollar above that is margin you keep.
Our breakdown of percentage fees on bitcoin payments shows how this changes at higher volumes, including hidden spreads on custodial services.
Payments are final. There are no chargebacks, which protects you from friendly fraud. It also means refunds are a manual decision: you send bitcoin back, and the customer's refund address is on you to collect. Bitcoin invoices carry no cardholder data, so PCI scope does not apply to that payment method, but you are responsible for wallet security instead.
Choosing a Payment Module: Five Checks Before You Install

Whatever you pick, run these five checks:
- Custody. Does money land in your wallet or in someone else's account first? If it passes through a third party, you have a custodial service with a module on top. The non-custodial crypto payment gateway guide shows how to tell the difference.
- Fee structure. Percentage, flat, or free? Calculate your own break-even using monthly sales and average order value, not the vendor's example.
- Settlement controls. Can you set confirmation thresholds, invoice expiry and underpayment tolerance? If not, you will be explaining stuck orders to customers.
- Platform and version fit. A module built for last year's checkout can silently fail after an update. Check the supported version list against yours.
- Maintenance owner. Someone has to update the software, keep the node synced and watch for failures. If that is you, budget the hours. If it is the vendor, get it in writing.
Pro Tip: Before going live, pay your own store a tiny real invoice, then deliberately underpay a second one and let a third expire. Most failures hide in those edge cases: the shop never receives the "paid" callback, or an expired invoice gets paid late and nobody reconciles it. Ten minutes of testing beats finding out from a customer.
Get Bitcoin Checkout Wired Into Your Shop Without Running a Server
The problem this article described is that a good payment module still needs something behind it, and for bitcoin that something is a synced node you have to keep alive. Myntli takes that part off your plate. For $29 a month, you get a BTCPay Server store on Myntli's node, wired into WooCommerce, Shopify, Ghost, Magento, PrestaShop, Drupal Commerce, Invoice Ninja or ReplaPay, with monitoring, updates and sync maintenance handled. Payments go straight to your own wallet, with no percentage taken and no custody of your funds. If you would rather own the hardware, a full node installed on your server is a one-time $449.
One limit to know: Myntli cannot recover a lost wallet or reverse a payment. If you do not have a self-custody wallet yet, we will walk you through setting one up, but the seed phrase backup is yours to keep safe. Also confirm your platform and version against our integration list before you commit, because custom checkouts sometimes need API work. Myntli provides API access for exactly that case.
Frequently Asked Questions
What is a payment module?
A payment module is software that adds a payment method to an online store's checkout. It creates the charge or invoice, sends the customer to pay, and updates the order when payment arrives. It is distinct from a payment processor, which is the licensed institution that actually moves the money.
How is a payment module different from a payment gateway?
The module lives inside your shop and controls checkout and order status. The gateway is the secure connection between your shop and the processor or payment network. Some products bundle both, which is why the terms get mixed up.
How do I create a new payment processor?
For cards, you need acquiring-bank sponsorship, card-network registration, PCI DSS validation and, in many jurisdictions, money-transmission licensing. It is a long, expensive regulatory project. Most merchants are better served by building or installing a module on an existing backend, or by running their own bitcoin node.
How does Coupa Pay work?
Coupa Pay is a buyer-side payments feature inside a procure-to-pay platform. After a company approves a supplier invoice, it can pay through methods such as virtual card, bank transfer or check, depending on its configuration. Suppliers track invoices and status in the Coupa Supplier Portal.
Can you give examples of payment plans?
Common plans are pay in full, deposit plus balance, fixed installments, subscriptions, milestone payments and net-30 invoice terms. Card-based shops can automate recurring charges. Bitcoin shops usually do best with deposits and milestones, since each bitcoin payment must be sent by the customer.
Does a bitcoin payment module take a percentage of each sale?
Not if it is built on self-hosted BTCPay Server, which is free open-source software. You pay for hosting or your own server, and the customer pays the network fee. Custodial services behave differently, so check how they charge before you install.
Sources
- BTCPay Server Documentation | BTCPay Server Project
- BTCPay Server source repository | BTCPay Server Project (GitHub)
- PCI Security Standards | PCI Security Standards Council
- Bitcoin Developer Guide: Payment Processing | Bitcoin Project
- Coupa Business Spend Management | Coupa Software
