Supported Payment
In simple words
Kitchen365 connects to the payment providers you already use — Authorize.Net, Stripe, PayPal, QuickBooks Payments, Square, NMI and Clover — and also supports Cash On Delivery, Money Order, Bank Transfer and Split Payment. You enter your own gateway account once, choose where each method is offered, and customers pay on your website or your staff take payment on a quote or order. When a bank (ACH) payment settles or bounces days later, the order updates by itself.
The problem it solves
Taking a payment is easy. Knowing it really arrived is not. Card payments live in one gateway, bank payments take days to clear, offline payments arrive by post, and someone has to match all of it back to orders. Without one place that knows which methods are offered, to whom, and what each payment's status is, money is chased by email and orders wait on guesswork.
What happens without it
| If payments are handled outside the Console | What it means for your business |
|---|---|
| Staff take card details by phone and key them into a gateway | Slow, error-prone, and a card-data risk |
| ACH payments are checked by logging in to the bank or gateway | Orders sit unshipped, or ship before the money clears |
| A returned ACH payment is noticed weeks later | Goods are already delivered and unpaid |
| Every customer sees every payment option | Trade-only terms like Money Order are offered to the public |
| Card fees are absorbed silently | Margin disappears on every card order |
| Payment status lives in someone's inbox | Nobody can answer "has this customer paid?" quickly |
Time you save
| Task | The manual way | With Supported Payment | You save |
|---|---|---|---|
| Take a card payment | Phone the customer, key it into the gateway, note it on the order — 5–10 min | Customer pays at checkout, or staff charge it on the order | 5–10 min per payment |
| Confirm an ACH payment | Log in to the gateway every day until it clears — 10 min per order | The gateway's webhook updates the order automatically | 10 min per order, every day it is pending |
| Catch a returned ACH payment | Found at month-end reconciliation | Order moves back to Pending Payment the day it is returned | Unpaid shipments avoided |
| Offer a method only to trade customers | Tell staff who may use Money Order | Customer Apply limits it to selected groups | Mistakes avoided |
| Recover card processing costs | Absorbed, or added by hand | A Payment Fee is added automatically | Margin protected on every card order |
| Switch gateway | Rebuild checkout | Add the new method and enter its keys | Days of development avoided |
Your process, before and after
Payments are taken in different tools, bank payments are checked by hand, and staff remember which customers may pay which way.
Each method is set up once with your own gateway account. Customers see only the methods meant for them, and every payment — including late ACH settlements and returns — updates its order by itself.
Payment settings affect live checkout. Test with your provider's sandbox keys first, then switch to live keys and URLs together.
Who uses it
- Admin — adds payment methods and enters gateway credentials
- Accounts team — watches payment status, fees and returned payments
- Sales team — takes payment on quotes and orders in the Console
- Business head — decides which methods, fees and customer restrictions to offer
When to use it
- Before you start taking payments online
- When you change or add a payment provider
- When you start accepting ACH / bank payments and want orders to update automatically
- When you want to pass card processing costs on as a payment fee
- When a payment method should be offered only to certain customers (for example trade accounts)
- When you move from test (sandbox) to live payments
What each part does for you
| Supported option | How it helps you |
|---|---|
| Authorize.Net — card and ACH | Use your existing Authorize.Net merchant account for cards and eChecks |
| Stripe — card and ACH | Fast card checkout and US bank payments, with automatic status updates |
| PayPal | Let customers pay with their PayPal account |
| QuickBooks Payments — card and ACH | Payments land straight in your QuickBooks-connected account |
| Square — card and ACH | Use your Square account online as well as in store |
| NMI — card and ACH | Work with NMI-based processors, including ACH updates |
| Clover — card | Use your Clover merchant account for online card payments |
| Cash On Delivery, Money Order, Bank Transfer | Offline options with instructions and reference fields for the customer |
| Split Payment | Let a large order be paid in installments through your card gateway |
| Customer Apply | Offer a method only to the customer groups or customers you choose |
| Payment Fee | Add a fixed or percentage surcharge for a method |
| Webhooks | Orders update by themselves when a payment settles, fails, is returned or is refunded |
Step-by-step guide
See Supported Payment in the Console Guide for every provider's setup steps and fields, and Configuration › Payment Methods for the screen itself.
Related pages
- Configuration — all store-level rules
- Supported Shipping
- Supported Tax
- QuickBooks Settings — connect QuickBooks for QuickBooks Payments
- Order Management