A Tutorial: Setting Up Payment Collection Through WhatsApp for Your Beauty Salon

What you'll accomplish

By the end of this tutorial, your beauty salon will be able to:

• Send payment requests via WhatsApp for deposits, service payment, and package purchases.
• Receive payment confirmations automatically and dispatch receipts.
• Handle common exceptions (payment failed, wrong amount, disputes) with defined workflows.

Estimated time: 4-8 hours of active work over 2-3 weeks (waiting for Meta approvals and payment processor setup consumes the elapsed time). Not something you can complete in a single sitting.

What you need to start: a functional WhatsApp Business Platform account, a payment processor account appropriate for your market (I'll walk through the market-specific options below), and a client list to test with. If you don't have these, address them first.

Step 1: Choose your primary payment rail

The first choice shapes everything downstream. Your primary payment rail should be the one your specific salon clientele already uses.

By market:

• Kenya: M-Pesa Till or Paybill via Safaricom.

• Egypt: Instapay from Central Bank of Egypt, or Vodafone Cash.

• Nigeria: Paystack for card processing, direct bank transfer for larger amounts.

• South Africa: SnapScan or Zapper QR-based payment, or bank transfer.

• Portugal: MB WAY, with SEPA for larger amounts.

• Brazil: PIX with QR code embedded in message.

• India: UPI with intent link or Bharat QR.

• Indonesia: QRIS accepting any local e-wallet.

• Turkey: iyzico or PayTR card processing, or bank IBAN transfer.

• Mexico: SPEI via CLABE for larger amounts, Mercado Pago QR for smaller.

• UK: Stripe, Payplug, or bank transfer.

Choose one primary; you can add secondary rails later. Setting up multiple rails simultaneously slows the tutorial and produces configuration complexity.

Step 2: Set up your payment processor account

Go to your chosen payment processor's website and create a business account. Provide business registration documents (varies by market and processor), banking information for settlement, and identity verification for the business owner.

Expect this step to take 3-7 business days depending on the processor and market. This is verification time, not active work time.

While waiting for account activation, prepare the following:

• Your salon's service catalogue with pricing (deposits, services, packages, tips-if-applicable).

• Your salon's refund and cancellation policy in writing.

• Your payment method disclosure for clients (which processor you use, how they receive receipts, how to raise disputes).

Step 3: Design your payment request templates for Meta

You'll need 3-5 Meta-approved templates for common payment scenarios:

Template A — Deposit request: Sent when a client books a service requiring a deposit. Includes salon name, service description, deposit amount, payment link or QR, and refund policy note.

Template B — Service payment reminder: Sent 24 hours before appointment for clients who prefer to pay in advance. Includes appointment details, total service amount, payment link, and alternative to pay at salon.

Template C — Package purchase: Sent when a client wants to purchase a service package (unlimited monthly, N-service package, gift package). Includes package details, price, terms, and payment link.

Template D — Post-service payment: For clients who choose to pay after service. Sent after service completion with total, payment link, tip suggestion if applicable.

Template E — Payment failed follow-up: Sent when a payment attempt failed. Includes what happened, options to retry, and alternative payment methods.

Submit these templates to Meta for approval. Category them correctly — utility for booking-related payment requests, marketing for package-purchase promotional broadcasts. Expect 3-7 business days per approval cycle. Iterate on rejected templates.

Step 4: Connect the payment processor to your BSP or CRM

Your BSP (Business Solution Provider) or CRM connecting to Meta's WhatsApp Business Platform needs to integrate with your payment processor. This step varies by BSP.

If your BSP has native integration with your payment processor:

1. Log into your BSP admin panel.

2. Find the payment processor integration.

3. Enter your API credentials (from your payment processor's dashboard).

4. Configure the specific integration options (payment link generation format, webhook URL for payment confirmations, etc.).

5. Test with a small transaction to yourself before configuring for clients.

If your BSP doesn't have native integration but supports webhook-based custom integration:

1. Set up a webhook receiver (may require a developer for this step).

2. Configure your payment processor to fire webhooks to your webhook receiver.

3. Configure the receiver to update your CRM and dispatch confirmation messages.

If your BSP has neither, you may need to consider a different BSP. Payment integration is not something that can be worked around.

Step 5: Configure automation triggers

Now that templates are approved and payment integration works, configure the automation triggers that dispatch the templates at the right moments.

Common triggers to set up:

Trigger A — Booking with deposit requirement: When a client books a service in the salon's booking system that has a deposit requirement, automation dispatches Template A (deposit request) automatically.

Trigger B — Day-before appointment for advance-payment clients: When it's 24 hours before an appointment for a client marked as preferring advance payment, automation dispatches Template B.

Trigger C — Package purchase request: When a client messages requesting a package purchase, automation dispatches Template C after human confirmation of the specific package.

Trigger D — Post-service payment: When a service is marked complete for a client who prefers post-service payment, automation dispatches Template D.

Trigger E — Payment failure: When your payment processor's webhook reports a failed payment attempt, automation dispatches Template E.

Test each trigger with your own phone as mock client before enabling for real clients.

Step 6: Handle exceptions and edge cases

The first two weeks of live operation will surface edge cases the tutorial can't fully anticipate. Common ones:

Client pays wrong amount: Client pays less or more than the requested amount. Set up a workflow: automation dispatches a message confirming what was received and what was expected, offering resolution (client sends additional payment for underpayment, receipt showing overpayment credit for future service).

Payment succeeds but confirmation doesn't arrive: Client confirms they've paid but the payment processor webhook didn't fire. Set up a manual reconciliation workflow the salon can trigger during business hours.

Client disputes charge: Client contests a payment weeks after service. Set up a defined dispute-handling workflow with clear timelines for salon response and resolution.

Refund requests: Client requests refund per your cancellation policy. Automation acknowledges the request; human processes refund via payment processor's dashboard; automation dispatches refund confirmation.

Document each exception workflow you encounter for future consistency. This is where the operational discipline of running WhatsApp payment collection emerges over months rather than being fully anticipated at setup.

Step 7: Ongoing monitoring

After launch, monitor monthly:

• Payment success rate. Should be above 95%. Below that, investigate specific failure patterns.

• Time from template dispatch to payment received. Should be under 15 minutes for the majority of dispatches. Longer indicates payment friction.

• Dispute rate. Should be low (under 2% typically). Higher indicates unclear communication about the service or the refund policy.

• Client feedback on payment experience. Review WhatsApp threads for client comments about the payment process; iterate templates as needed.

One year in, your payment collection workflow should be handling the majority of your salon's transactions with minimal manual intervention. Reaching that state requires the setup and 2-3 months of iteration described here.

Meta bills WhatsApp Business Platform utility conversations at rates varying by market. Payment-related conversations typically fall in the utility category; your Meta cost for payment collection alone is usually a small fraction of the salon's overall Meta cost. Software layer (BSP, payment processor fees) is the primary expenditure.