- Coming
Text to pay
Get paid in the same conversation.
The job is booked or done, and the customer is already talking to you. Zenith will send a payment link from your own payment processor right there, for an amount taken from your records, and mark it paid on the customer's record when it clears. Ferrata never holds the money or sees a card number.
What happens with Zenith
From the amount on record to paid on the record.
- 01
The amount, from your records
An invoice, an accepted quote, a balance or the booking's deposit rule. Never a number the model chose.
- 02
Verified first
Invoice details and balances shared only after the customer is verified. Before that, no amount at all.
- 03
A link from your processor
Created on your own payment processor account and sent in the thread, by text or email.
- 04
Paid, on the record
When your processor confirms the payment, it will land on the customer's record and, under your approval rules, in your ERP.
- 05
Every link audited
Who asked for it, the amount and where it came from, and when it was sent, opened and paid.
You’re booked Thursday, 8 to 10am. A $79 deposit holds the visit and comes off the final bill.
Pay with your processor$79.00Deposit · diagnostic visitYour assistant · 7:47pmDone, thanks!
7:51pmWhat it covers
Four moments a business gets paid by text.
Deposits when booking
A deposit that holds the visit, the table or the install, by your rule for that booking type.
An invoice or a balance
The amount on the invoice, after the customer is verified.
A quote, accepted
Accept the quote and pay the deposit in one step.
An approved payment plan
Each installment of a plan your team already approved.
Processors
Your processor, your account, your money.
The link will be created on the business's own account. Ferrata will store no card data and touch no funds.
| What | Today |
|---|---|
| StripeConnected to your own account, which you can disconnect at any time. First. | Coming |
| SquareNext after Stripe. | Coming |
| Your ERP's payment portalIts own pay link, where neither processor fits. | Coming |
On its own, and what waits
It sends the link. People decide refunds and discounts.
On its own
- Sending a deposit link when a booking needs one
- Sending the invoice link when it is due, to a verified customer
- One reminder, inside your hours, if a link goes unpaid
- Marking the record paid when your processor confirms it
Waits for a person
- Every refund
- Discounts and any change to an amount
- A payment plan that is not already approved
- A customer who disputes what they owe
What it reads and writes
Your records in, the outcome back where it belongs.
Reads
- Invoices and balancesFrom your ERP or accounting system.Coming
- Quotes and bookingsThe deposit rule for each booking type.
- VerificationWhether this customer is verified before any amount is shared.
Writes
- A payment linkOn your own processor account, Stripe first.Coming
- Paid statusOn the customer's record in Zenith.
- Your ERPThe payment, under your approval rules.Coming
FAQ
Questions buyers ask about text to pay.
Will Ferrata hold our money or see card numbers?
No. The link will open your processor's own hosted payment page, the money will go straight to your account, and card details will never touch Zenith or Ferrata.
Which payment processors will it work with?
Stripe first, connected to your own account, which you can disconnect at any time. Square next, and an ERP's own payment portal link where neither fits. Text to pay is coming; nothing takes payments today.
Can the AI change the amount?
No. The amount will come from an invoice, a quote, a balance or your deposit rule. The model will write the message around the link and never set the number. Discounts and refunds will wait for a person.
What stops a balance going to the wrong person?
Verification. Until the customer is verified, no invoice number, amount, date or status is shared on any channel. A text or email will carry a secure link so the customer can verify first.
Do customers need an app?
No. The link will open a payment page in their phone's browser, with the card and wallet options your processor supports.
Will the payment reach our accounting system?
It will land on the customer's record in Zenith first. Writing it to your ERP or accounting system follows the approval rules you set, once that connection is live for you.
Start with deposits on new bookings.
The simplest place to begin: a deposit link sent when a booking is made, paid before the day.
Pricing is set with each business in the private beta.