Keep your POS. Connect Drip & Bake.
Drip & Bake is designed to work alongside the payment infrastructure already operating inside cafés and bakeries. Existing POS systems, payment providers, terminals, cash payments and counter service all continue serving their purpose.
Find your connection
Card, Apple Pay or Google Pay, before the order is made.
01 / An extension of your business
Our goal.
Drip & Bake adds another layer to that environment: an online storefront, mobile ordering, scheduled orders, customer accounts, loyalty and fulfilment through Service.
Our goal isn't to replace the systems a business already depends on, but to integrate with them—giving customers who prefer mobile ordering or ordering ahead another way to interact with the same business.
Our goal is to be the online storefront and ordering layer for the physical business.
For established businesses, that means integrating with the payment and POS infrastructure they already use.
For new businesses, Drip & Bake can be the starting point. They can establish their online storefront and payment infrastructure first, then expand into a physical storefront with systems capable of supporting both environments.
Our goal isn't to create a gap between the online and physical storefront, but to bridge it. We work as an extension of these systems, not a replacement for them.
Your infrastructure. Connected.
Currently supported payment providers.
Drip & Bake currently supports Stripe and Square, but our integration network isn't stopping there.
We're working to integrate more payment providers with the help of our team and the merchants looking to connect their existing systems with Drip & Bake.
Use a provider we don't currently support?
Your online
payment connection.
Connect your Stripe account for payments through your Drip & Bake storefront.
Online today.
A counter tomorrow.
A payment relationship that can grow with your business, online and in person.
Explore the path02 / A clear division of care
The payment.
And everything around it.
Your provider / The money
What the payment provider handles.
Payment processing is specialized financial infrastructure.
Established providers maintain systems specifically designed to authorize transactions, process payment credentials, manage settlement, operate fraud and risk systems and maintain the financial relationship between the provider and merchant.
Depending on the provider and integration, this includes:
- payment processing
- transaction authorization
- settlement and payouts
- payment credential security
- provider-level fraud and risk systems
- provider transaction records
- the merchant's financial account with that provider
Those responsibilities remain with the payment provider.
Drip & Bake doesn't recreate that infrastructure. We connect to it.
Drip & Bake / The context
What Drip & Bake handles.
Drip & Bake handles the context surrounding the transaction.
We connect payment activity to the correct:
- business
- location
- order
- customer
- receipt
- Service workflow
- loyalty activity
- refund state
- transaction history
Someone didn't simply spend $12. They placed a particular order, through a particular storefront, belonging to a particular business, for a particular method of fulfilment.
That is the information Drip & Bake is built to understand.
The provider processes the money. Drip & Bake understands the transaction inside the business.
From your first order
to your front door.
Start where you are
Starting online first.
Drip & Bake can also be the starting point for a new business establishing its online presence before opening a physical storefront.
Starting with Drip & Bake gives the business an online storefront, ordering system and a pathway for establishing payment processing without having to design the entire payment environment from scratch.
When the business is ready to expand into a physical location, the payment infrastructure established online can grow with it.
A path with Square
Our suggested provider for online to physical — Square.
For businesses starting online with Drip & Bake and planning to expand into a physical storefront, we suggest Square.
A business can connect Square to Drip & Bake for online payment processing while using Drip & Bake as its online storefront and ordering system.
When that business moves into a physical storefront, Square can continue with it through its POS software, payment terminals, registers and other hardware for in-person transactions.
There is no need to establish one payment relationship online and start over when the doors open.
Drip & Bake runs the online storefront and ordering experience. Square provides the payment infrastructure that can grow from online payments into the physical POS environment.
Connected does not mean identical
Do both systems need to sync?
No.
A business doesn't need to use the same provider for its online and physical payment infrastructure.
For example, Stripe can handle payments made through the Drip & Bake storefront while another POS provider, such as Lightspeed, handles counter transactions, cash payments and the physical store environment.
The two systems can serve different parts of the same business.
Drip & Bake doesn't require a business to rebuild its entire payment infrastructure around one provider simply to connect its online storefront.
03 / Built on trust
Payment security.
Payment security is an important part of a business's financial infrastructure, and we take our responsibility within that environment seriously.
Drip & Bake is structured so established payment providers remain responsible for the sensitive payment-processing infrastructure they are designed to operate. Payment credentials and financial transactions are processed through the connected provider rather than Drip & Bake attempting to recreate that infrastructure.
On our side, Drip & Bake protects the application around that transaction: merchant connections, store and tenant boundaries, payment-to-order relationships, authorization around business data and the integrity of the information received from connected payment providers.
We also verify provider communications before using them to update payment and order records inside Drip & Bake.
The payment provider secures the payment infrastructure. Drip & Bake secures the application and the connection around it.
Every transaction. Considered.
How each payment is protected.
01Card details never reach Drip & Bake.
When a customer pays by card, the card field on your storefront belongs to your payment provider. Card details travel from the customer's device directly to Stripe or Square. Drip & Bake receives a payment reference and, afterwards, the card brand and last four digits for the receipt—never the full card number.
02The money goes to your account.
Payments are made on your own Stripe or Square account and paid out to your bank by your provider. Drip & Bake never holds your sales money. Connecting or changing a payment provider is a protected action: if you've turned on two-step sign-in, we ask for your authenticator code first.
03Your menu sets the price.
The amount charged for an order is calculated by Drip & Bake's servers from your menu—your prices, your modifiers, your tax settings. A customer's device can choose what to order and how much to tip, but it can't change what an order costs.
04An order is paid only when the provider says so.
A customer's phone can't tell us it paid. An order becomes paid in one of two ways only: a signed message from Stripe or Square—checked on arrival, with anything forged, altered or replayed later refused—or our server asking the provider directly. Until then the order stays unpaid, and the loyalty points, memberships and anything else that depends on payment wait for it.
05A customer is charged once.
Each order carries one payment reference. If a customer taps pay twice, or their connection drops and retries, the provider treats it as the same charge. An order that has been paid can't be paid again, and a cancelled order can't be charged at all. Providers sometimes deliver the same message more than once; we record each one the first time and ignore the repeats.
06Refunds follow your rules.
You decide who on your team can refund and how much. Refunds above a staff member's limit need a manager's or owner's approval. Before any money moves, the refund is checked against what the provider actually holds for that payment, so it can never exceed what was charged, and a retried refund is never sent twice.
07Customer balances stay with your business.
A customer's stored balance can only be changed by Drip & Bake's servers, never by the customer's own device. It belongs to your business and can't be spent at an unrelated shop on the platform. Two purchases at the same moment can't both spend the same balance, and every change is written to a permanent ledger.
08Test payments never mix with real ones.
Every message from a provider says whether it came from test or live mode. If that doesn't match the mode your store is running in, we refuse it, so a practice payment can never mark a real order as paid.
Familiar at checkout
Supported payments for customers.
The payment methods available to a customer are determined by the connected payment provider, the merchant's configuration, the customer's device and regional availability.
Depending on those factors, supported methods can include major credit and debit cards such as Visa, Mastercard and American Express, along with supported digital wallets such as Apple Pay and Google Pay.
This allows customers to use familiar payment methods while the merchant continues processing those payments through their connected provider.
More than the morning coffee
What customers can pay for.
Payments inside Drip & Bake extend beyond a standard menu order.
Customers can make payments across the storefront for:
- menu orders
- scheduled and bake-ahead orders
- event tickets
- memberships and subscriptions
Customers who hold a balance with your business can also pay from it at checkout.
Each payment remains connected to what the customer purchased and the Drip & Bake system responsible for it.
04 / Get comfortable before going live
Simulated payments.
Before a payment provider is connected—or any time you want to rehearse—Drip & Bake uses simulated payments to help businesses understand how their store functions without processing a real payment.
A business can experience the transaction from both sides: completing checkout as a customer, receiving notifications, seeing the order enter Service and completing the fulfilment process as staff.
Simulated payments are switched on from your dashboard and appear directly in checkout, with clear indicators shown on both the customer and fulfilment sides so they aren't mistaken for real transactions.
A simulated order runs through Service like any other, but it never reaches your sales records, stock counts, loyalty points or refunds, and a real order can never be turned into a simulated one.
It allows the complete payment and order experience to be tested before a real payment ever needs to be processed.
One switch in Operations → Checkout, with a warning to turn it off before going live.
The next connection starts with you
Tell us what you use.
Our payment integrations should reflect the systems cafés and bakeries actually use.
If Drip & Bake doesn't currently support your payment provider, tell us which provider you use and what you need from the integration.
Our team can investigate the provider, its infrastructure and how it could work with Drip & Bake. These requests also help us decide which integrations should be supported next based on the businesses actually using the platform.
A request doesn't guarantee an integration, but it gives us something much more useful than an assumption: what our merchants actually need.
Your business.
More ways to be there.