Get paid · Roadmap
RoadmapGet paid at pickup with a pay link or a QR code
The customer scans a code on your screen, or taps the link in their text, and pays by card on their own phone. This is on the Service roadmap (phase P7); here is how it will work.
On the Service roadmap — this page explains how it will work. See what is live today.
INV-1187 · from WO-2291
Invoice
Pay link + QR
on the roadmap
How a customer will pay
Payments in Service will run through Stripe (decision D3), with a Stripe Connect account for your shop. That means the money goes to your Stripe account and then to your bank, and Stripe handles the card processing, the payouts and the compliance that comes with them.
At the counter, the invoice will be shown on your screen with a QR code. The customer points their phone camera at it, opens a secure Stripe page and pays with their card or a wallet on their own phone. The same invoice can go out as a text or email with a payment link, so a customer who dropped off on Saturday can pay on Monday before they come in, and just pick up the bike.
If the customer would rather hand you a card, the plan includes typed card entry. That is the full set for card-present payment: link, QR or card entry.
Why there is no Tap to Pay
Tap to Pay on a phone and Bluetooth card readers need a native app. The Service field app is deliberately web only (decision D5): an installable app you add to the home screen, which works offline and uses the camera and signature pad through the browser. That choice keeps the app on every phone without an app store, but it rules out tapping a card on the phone.
For a bike shop that is less of a loss than it sounds. Almost every customer carries a phone that can scan a QR code, and paying on their own screen is quicker than passing a card across the counter. For a mobile repair van, the QR code on the tech's phone works at the curb with no hardware to charge or pair.
We would rather tell you this now than have you find out when you go looking for the reader settings.
What the payments design covers
Planned capabilities from Service parity section 13.
Record payments by hand
Money received recorded against a sent invoice, with part payments and a Paid status. Admin only.
Payment link
A Stripe link on the invoice, sent by email or text, paid on the customer's own phone.
QR code at the counter or van
The invoice as a code on your screen. The customer scans and pays.
Card entry
Type the card in when the customer would rather hand it over.
Deposits and partial payments
A deposit when the quote is approved, and the balance at pickup.
Cards on file and autopay
For fleets and accounts on a recurring billing schedule.
Deposit matching
erp.io Pey, live today, matches payments to the bank deposits they arrive in.
In the shop
Giant Revolt · WO-2288
Quality check · ready today
To do
Approve quote Q-0731$58
Pay invoice INV-1187$238.20
Review
Service history
Tune-up
Hanger
Tubeless
Paying from the customer portal
A planned customer portal view where a rider pays an open invoice. The portal itself is a live erp.io module; Service invoices do not appear in it yet, and paying online is on the roadmap. Illustrative only.
Illustration · sample data
Deposits, tips, refunds and fleets
Deposits matter for special orders and big jobs. When a customer approves a quote for a new drivetrain, the plan lets you take a deposit at approval and apply it to the final invoice automatically. Nobody has to remember that the customer already paid half.
Tips are in the plan, with preset percentages or a custom amount. Some shops will never use them; mobile repair customers often ask. Refunds, full or partial, and disputes are handled through Stripe with a record in Service.
For accounts such as a rental fleet or a corporate bike program, the plan includes a saved card or bank account on file and automatic payments on a billing schedule. ACH bank payments are in the Stripe design for those larger, regular invoices.
Money into the books
Every payment, refund and payout is a ledger event. The plan posts each one from Service to erp.io Accounting through a write connection planned under decision D2, and erp.io Pey matches Stripe payouts against the deposits in your bank feed. Pey is live today for matching; it does not collect or move money.
Card processing is done by Stripe on your own Stripe account, so processing terms are between you and Stripe. We are not publishing processing rates here, because they are Stripe's to set.
Instant payouts, lending and business bank accounts are explicitly out of scope for Service. Stripe handles holds, reserves and tax forms such as 1099-K as the processor.
FAQ
Questions shop owners ask
Can I take card payments in BIKE.co today?+
No. Today an admin records payments by hand against a sent invoice, including part payments. Taking card payments, pay links and QR codes are on the Service roadmap and will run through your own Stripe account.
Does BIKE.co support Tap to Pay or a card reader?+
No, and none is planned. The field app is a web app only, and Tap to Pay and card readers need a native app. Card-present payment will be a Stripe payment link, a QR code or typed card entry.
Who processes the card payments?+
Stripe, through a Stripe Connect account for your shop. Money goes to your Stripe account and then to your bank, and Stripe handles processing, payouts, holds and tax forms as the processor.
Can a customer pay before they come to pick up?+
Not through BIKE.co yet. Invoices are not delivered by email or text today, and there is no pay link. The design sends the invoice with a Stripe payment link so the customer can pay from home and just collect the bike.
Will deposits apply to the final invoice automatically?+
Yes. In the plan, a deposit taken when a quote is approved is applied to the invoice raised from that job, so the balance due is right at pickup.
Keep reading
Take in your next repair on BIKE.co.
30 days free, no card, every erp.io module switched on. Start with a request, end with an invoice.