Online payments
Payments through Bayable's Stripe to your payout account, cards and bank accounts on file, autopay, pay-by-phone at the counter, and what fees you pay.
Online payments are part of Professional and Enterprise. There are two ways to take them.
Through Bayable (accounts opened on bayable.com)
When you sign up you add a payout account – your bank, a voided check, and Stripe's terms. That's all: cards, bank payments and autopay then run through Bayable's Stripe account and each payment is paid out to your bank automatically, less Bayable's processing fee – shown under Corporate settings → Payouts & Billing (the card rate for cards, the bank rate for bank debits). There are no keys and no webhook to set up. Wherever a card or bank account is entered – the website, the portal, the office – it's typed into Bayable's own form on the page; nobody is sent to a payment processor's page. The card number goes from the browser straight to the processor (Stripe) and never touches Bayable's servers.
Payments switch on as soon as Stripe has verified the business – if it needs more (the representative's date of birth, for example), Corporate settings → Payouts & Billing shows a Finish with Stripe button that opens Stripe's own page. The same tab shows the payout bank and lets you change it.
Accounts with their own Stripe keys
Accounts set up before payments moved to Bayable may still take payments through a Stripe account of their own; those keys keep working and take precedence. Keys can no longer be added from the admin – to switch over to Bayable's payouts, or with any question about an older setup, write to Bayable support.
What tenants can do
- Pay online from the website's reservation and move-in and from the portal: a card typed into the page's own form, or – in the portal – one of their saved cards or a verified bank account (ACH) where you allow it. Bank payments show as processing until they clear, usually in a few business days.
- Payment methods in the portal (Account → Payment methods): add a card or bank account in the portal's own form (a bank account is ready at once when the tenant logs in to their bank in Stripe's window; added by its numbers instead, it's confirmed by two small deposits sent to it – the tenant types the code or the two amounts from their statement under Payment methods, and the account is ready to use), make one primary, remove old ones, and choose for each space whether autopay is on and which card or account it charges. The "autopay failed" email links straight there, so an expired card can be replaced without calling the office.
- Autopay per rental: on the due date the amount due is charged to the chosen method (or the primary). A decline notifies the tenant once and is tried again three days later by the facility's calendar (declined on the 1st, tried again on the 4th, whatever time the nightly run happens); while it waits, none of the tenant's spaces here is charged again – the space they moved to after a transfer included. A bank payment still clearing counts as paying what it covers: autopay charges only the rest (after a transfer, just the difference), and no late fee is debited on top of rent that's clearing. If Stripe's answer to a charge gets lost (an outage), the next run looks the charge up in Stripe instead of charging again. Paying in full by any method clears the delinquency stage and restores gate access.
What staff can do
- Card by phone (<!-- ── B (tenant page) ── -->tenant page → Take Payment → *New card*<!-- ── end B (tenant page) ── -->; on Whole account it charges the whole balance, oldest invoices first): the card details are typed into Bayable's card form (name, number, expiry, security code and billing ZIP) – the number goes from the browser straight to the processor and never touches our servers – and the payment is recorded at once. A declined card says why and the form stays for another card. Tick save for autopay to keep the card. It works as soon as online payments are on – there's nothing to set up; Stripe treats it as a phone order where it can, so the tenant doesn't have to approve it on their own device.
- Add a payment method without charging (tenant page → Payment methods → Add a payment method): the same form saves a card or a bank account for autopay. Staff type a bank account's numbers (only the tenant can log in to their bank), so it waits for its two small deposits – the tenant reads the code or the amounts off their statement and either of you types them in (the tenant under Payment methods in the portal, you on the tenant's Payment methods tab) – and is chargeable after that.
- Card readers (Stripe smart readers) – see below. <!-- ── B (tenant page) ── -->A card taken on any other terminal is recorded with Take Payment → Card terminal (shown when no reader is set up). Card on file: Take Payment → Card on file charges one of the tenant's saved cards at once – pick the card; a declined card says why and nothing is recorded.<!-- ── end B (tenant page) ── -->
Card readers
Stripe's smart readers – the Stripe Reader S700/S710 and the BBPOS WisePOS E – take tap, chip and swipe payments at the counter. They connect to the internet over Wi-Fi or ethernet, so they work with any computer in the office; there's nothing to install.
Adding a reader (owners and managers): Settings → Card Readers. On the reader, open Settings (admin PIN 07139 unless you've changed it) and choose Generate pairing code; type the three-word code here with a name staff will recognise, like "Front desk". The first reader registers the facility with Stripe at its address (Settings → Facility needs the street, city, state and ZIP). Readers can be renamed or removed, and the list shows whether each is online. With test-mode payments you can add a simulated reader to try everything without hardware.
Charging on a reader:
- Tenant ledger → Take a payment → Card reader: the amount (the balance by default), whether to email a receipt, and the reader. <!-- ── B (tenant page) ── -->It's the choice already picked when the facility has readers and the tenant no saved card.<!-- ── end B (tenant page) ── -->
- Move-in → Payment → Card reader: the total due; the move-in completes as soon as the card is approved (refunded automatically if it can't be saved). Change the move-in while the reader waits (add a protection plan or a lock) and the reader asks for the new total – if Stripe won't change the amount, the waiting payment is cancelled (nothing is charged) and you send the new amount. If the card went through just before the change, the move-in completes and the message says how much is still owed (the gate code switches on once it's paid); if the move-in came to less than the card paid, the difference goes straight back to the card.
- Merchandise → Sell → Paid by: Card reader: the sale is rung up once the card is approved, at the prices charged. Refunding the sale, or returning some of its items, refunds that amount to the card – less anything already refunded to it in Stripe for that sale, so the card is never refunded twice (a tenant's bill just comes down). If the card refund fails, a walk-in's return is recorded with the money owed to the customer (it shows on the sale, and on Close of Day the day the refund in Stripe goes through); a tenant's waits on their account as money.
On the tenant's ledger a card payment says where it was taken: Card (card reader), Card (by phone), Card (in the office), Card (autopay) or Card (online) when the tenant paid in the portal.
The screen waits while the customer taps, inserts or swipes. A declined card shows the reason – try another card with Send to Reader Again, or Cancel Payment (the reader stops waiting and nothing is charged). Approved payments are booked exactly once, even if the screen is closed – Stripe's notice books them – and a page reloaded mid-payment picks the payment up again. If a reader is left waiting on a payment nobody is watching, Clear Reader under Settings → Card Readers cancels it. They're paid out with your other card payments, less the same processing fee. Settings → Card Readers lists recent reader payments.
Disputes and refunds
Online payments run through Bayable's Stripe account, so there is no Stripe dashboard of your own – refunds and disputes go through Bayable support.
- Refunds – write to support with the tenant, the date and the amount; we refund the payment in Stripe and the amount comes back out of your payouts. The refund appears on the tenant's ledger by itself, dated the day it was given, and what the payment had paid is owed again. Bayable's processing fee on a refunded payment isn't returned (Stripe keeps its own fee too); a charge the system refunds by itself because it couldn't be booked returns the fee.
- Disputes (chargebacks) – when the cardholder's bank takes the money back, the payment comes off the ledger that day (a Chargeback row) and the balance is owed again, late from that day (not from the bill's old due date). Autopay is switched off on all the tenant's rentals – a disputed card mustn't be charged again without the cardholder's say-so – with a note on each rental, and the office gets an email: talk to the tenant, then switch autopay back on from their Payment methods tab if they want it. If the dispute is won and the money comes back, the late fees the chargeback brought are waived – late fees put on the reopened bills from the chargeback day on, and the late fee on a later bill that the money taken off the account would have paid (money paid ahead pays the next bill as it's billed; the chargeback took it, so that bill went late) – and the money is booked as a payment that day; the office is told, and autopay stays off until you switch it back on. A refund made in Stripe after a won dispute shows on the ledger like any other, taken from the money that came back. Bayable answers disputes with Stripe and asks you for what shows the charge was right (the signed agreement, the ledger, receipts). A lost dispute and Stripe's dispute fee can be taken from your later payouts.
- Bank payments take a few business days to clear. One paid online shows as pending until it clears (autopay won't charge the same bill meanwhile) and is then booked as a bank payment; a bank debit that comes back unpaid is taken off the ledger the day it's returned (Bank debit returned). A returned bank debit – one booked and then taken back, or one that came back while it was still clearing (online or autopay) – is charged the facility's Returned payment fee on its own bill dated that day, when one is set; a declined card never is.
Accounts that still use their own Stripe keys refund and answer disputes in their own Stripe dashboard.
Fees
Bayable's processing fee is taken from each online payment before it's paid out to you – by default 2.9% + 30¢ per card payment and 0.8% per bank payment (at most $5), Stripe's standard US rates. The fee that applies to you is shown under Corporate settings → Payouts & Billing. Your Bayable subscription is separate and flat per facility, whatever the volume. Accounts on their own Stripe keys pay Stripe's fees to Stripe instead.
Moving saved cards from another system
Cards saved with your previous software live with its processor. See Credit cards on file: moving them for the PAN-migration route that brings them into Bayable's Stripe account without asking tenants to re-enter them.





