Supported Payment Methods & Settlement Markdown Table Template
A payment methods table answers two different audiences, and it helps to decide which one you are writing for before filling it in. Customers at checkout want to know which methods they can use, in which currencies, and how long until their order or subscription is confirmed. Internal readers — finance, ops, and the engineers integrating a processor — want fees, settlement timing, and reversal risk so they can forecast cash flow and decide which methods to switch on.
Edit This Template
Edit cells, add rows, or sort — the Markdown updates livePaste cells from Excel or Google Sheets into the first header to replace the table · Tab / Enter / arrows move · Shift+F10 opens row & column actions
When to Use This Table
Every number in this table comes from a processor’s price list or a bank’s terms, and those change. Card rates differ by country, card type, and whether a card is domestic or international; direct-debit pricing varies between providers; wire fees are charged by the banks on both ends, not just by you. Treat the template’s figures as placeholders, copy current numbers from your own processor’s pricing page, and date the table so nobody reads a two-year-old rate as today’s.
The most common confusion is in the timing column. Card authorization happens in seconds, but the money reaches your bank account days later as a payout, and direct debits can take several business days to confirm and can still be reversed weeks afterwards. A good table separates “customer sees success” from “funds are in our account” and notes how long each method stays reversible, because that is what drives fulfilment decisions.
What Goes in Each Column
| Column | Alignment | What to put here |
|---|---|---|
| Payment Method | left :--- | The method customers recognise, grouped by rail: cards, wallets, bank debits, transfers. List card brands in brackets only if you accept them all. Left-aligned. Wallets like Apple Pay ride on card rails, which is worth stating in a note. |
| Supported Currencies | left :--- | The currencies you actually price and charge in, not the processor’s marketing maximum. Some rails are single-currency by design: SEPA Direct Debit is euro-only and US ACH is USD-only. Use ISO 4217 codes (EUR, GBP) for precision. |
| Processing Fee | right ---: | Your negotiated or published rate from the processor’s pricing page, written exactly as they quote it (2.9% + $0.30, or a flat fee with any cap). Right-aligned. Add a footnote with the source and date checked, and omit this column entirely on customer-facing pages. |
| Settlement Speed | center :---: | Be specific about which event you mean: authorization, confirmation, or payout to your bank. Centered. Instant auth; payout in 2 business days is more useful than Instant, and avoids promising customers or finance something the rail does not do. |
| Availability | left :--- | Where the method works, from both sides: which customer countries and which of your merchant entities can accept it. Left-aligned. Include eligibility rules here too, such as “Invoices over $1,000 only” for wire transfers. |
How to Fill It In
- 1List the methods enabled in your processor dashboard and on each checkout surface (web, mobile, invoices). Methods enabled in the dashboard but hidden in checkout confuse support teams later.
- 2Copy fees from the processor’s current pricing page or your signed rate card, note the URL and date, and check whether international cards or currency conversion add a surcharge.
- 3Confirm timings from the processor’s documentation for each rail: time to confirmation, payout schedule for your account, and the window during which a payment can be disputed or returned.
- 4Check currency and country coverage against your own entity setup, not just the processor’s list. A processor may support a currency your account is not configured to settle.
- 5Publish two versions if needed: an internal table with fees and risk, and a customer table with methods, regions, and confirmation time. The Markdown to HTML converter helps if the customer version goes into a CMS.
Ready-to-Paste Variations
Customer-facing checkout FAQ
Drops fees, which are a merchant cost, and tells customers what they care about: where they can pay this way and when their order is confirmed.
| Method | Where you can use it | Order confirmed |
| :--- | :--- | :---: |
| Credit or debit card | Most countries | Immediately |
| Apple Pay / Google Pay | Supported devices and browsers | Immediately |
| SEPA Direct Debit | Bank accounts in SEPA countries (EUR) | After the debit clears, usually several business days |
| Bank transfer | Business accounts on invoice billing | When funds arrive |Reversal and dispute risk (internal)
For finance and fulfilment. Return windows follow scheme rules; confirm the exact figures for your processor and region before relying on them.
| Method | Can the payer reverse it? | Typical window | Fulfilment advice |
| :--- | :--- | :--- | :--- |
| Cards | Yes, via chargeback | Set by card network rules | Use 3-D Secure where available |
| SEPA Direct Debit (Core) | Yes, no-questions refund | 8 weeks; up to 13 months if unauthorised | Delay high-value fulfilment |
| US ACH debit (consumer) | Yes, via return | Up to 60 days if unauthorised | Verify the account before first debit |
| Wire transfer | Rarely; recalls need bank cooperation | — | Ship on receipt of funds |Common Mistakes
Presenting one processor’s fees as universal facts.
Fees vary by processor, country, card type, and contract. Cite the source, add the date checked, and recheck at least whenever the processor announces pricing changes.
Labelling card settlement as “Instant”.
Authorization is instant; payouts are not. Show both, so finance does not plan cash flow around money that arrives days later.
Describing SEPA as “Eurozone only”.
SEPA is wider than the euro area and includes non-euro countries such as Switzerland, Norway, and the UK. SEPA Direct Debit payments are in euro, so the right qualifier is “SEPA countries, EUR accounts”.
Ignoring reversibility when deciding when to fulfil.
Add a dispute or return window for each method. Direct debits can be pulled back weeks after they appear successful, which matters for digital goods delivered instantly.
Related Markdown Table Templates
Browse all 50 templatesCloud Infrastructure & AWS Monthly Cost Estimate
Itemized cloud infrastructure cost estimate covering compute, managed databases, storage, edge, and NAT networking, priced as a dated snapshot of list rates.
Technical SEO Audit & Meta Tags Matrix
Technical SEO spreadsheet matrix recording URL routes, target search keywords, title tag lengths, meta descriptions, and indexation status.
Competitor & Product SWOT Analysis Matrix
Strategic SWOT analysis matrix mapping internal strengths, operational weaknesses, market opportunities, and competitive threats.
Supported Payment Methods & Settlement: Frequently Asked Questions
Should I show processing fees to customers?
Usually not. Fees are your cost, and showing them invites questions you cannot answer at checkout. Surcharging card payments is restricted or banned in some regions and governed by card network rules, so check before passing fees on.
Are Apple Pay and Google Pay separate payment methods?
For customers, yes. For your processor they are card payments with a device token, so they generally follow card pricing, currencies, and dispute rules. List them separately because customers look for them by name.
What is the difference between authorization, capture, and payout?
Authorization checks the card and reserves funds. Capture actually charges the reserved amount. Payout is the processor sending collected funds to your bank account on its schedule. Each happens at a different time, and each belongs in a different part of the timing column.
Why does a SEPA or ACH payment take days to confirm?
Bank debits are processed in batches between banks and can be returned for insufficient funds or a closed account. Processors usually mark them pending until the return window for those reasons passes, which is why confirmation is not immediate.