> ## Documentation Index
> Fetch the complete documentation index at: https://docs.recepta.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Payments

> Collecting deposits and balances over text.

Recepta.ai can collect money from customers over text — a deposit at booking, or the balance after the visit. Payments go directly to your own connected account.

<Note>
  This is separate from your Recepta.ai subscription. Customer payments settle to your account; your Recepta.ai invoice is billed to you. See [Billing](/account/billing).
</Note>

## Connecting your account

Under **Payment settings**, connect the account you want customer funds to land in. You'll complete the provider's own onboarding — business details, bank account, and identity verification.

<Warning>
  Payouts don't start until the provider has verified you. Complete this before promising customers they can pay by link, and allow for the verification to take a day or two.
</Warning>

## Text-to-pay

The pattern that works for service businesses:

<Steps>
  <Step title="Send a link">
    A payment link goes out by SMS — at booking for a deposit, or once the job is done for the balance.
  </Step>

  <Step title="They pay on their phone">
    No app, no account, no calling back with a card number over the phone.
  </Step>

  <Step title="It reconciles automatically">
    The payment is recorded against the appointment and the contact, so your records match without anyone keying it in.
  </Step>
</Steps>

<Tip>
  Send the balance link while your technician is still on site. Collection rates fall sharply once the customer has moved on with their day.
</Tip>

## Deposits

Deposits at booking are the most effective no-show deterrent available — more so than reminders. They're worth considering for:

* long or high-value jobs
* first-time customers with no history
* slots that are expensive to lose, like weekend or emergency call-outs

Set your deposit policy in your [appointment settings](/booking/appointments) and make sure it's stated in your [knowledge base](/receptionist/knowledge-base) so the agent explains it consistently on the call.

## Payments through your CRM

If you run a connected [field-service CRM](/integrations/field-service-crm) with its own invoicing, decide deliberately where payment lives — in Recepta.ai or in the CRM. Collecting in both places splits your books and creates reconciliation work every month.

## Card security

Card details are handled by the payment provider and never touch Recepta.ai or your phone line. The agent will not take a card number verbally — it sends a link instead. That's deliberate: reading card numbers onto a recorded call is a PCI problem you don't want.