Use Payments with Appointments & Orders

Map verified payment status to appointment confirmation, order processing, notifications, deposits, and refunds.

Overview

Do not deliver, confirm, or activate a paid service solely from a browser redirect or customer screenshot. Use the verified provider event.

Who should use it

Workspace owners, operations teams, sales users and authorized technical users.

Where to find it in Wemblo

Wemblo -> Automations -> Appointment Booking / Marketing -> Orders / My Subscription -> Payment Gateway

Before you begin

  • Use the correct workspace and authorized role.
  • Prepare fictional Pakistan test data.
  • Confirm connected provider accounts where required.
  • Define who approves price, stock, booking, payment or final status.

Main concepts and fields

Concept / FieldMeaning or Use
ServiceBookable offering.
AvailabilityPermitted time slots.
DurationLength of booking.
ReminderScheduled customer notification.

Step-by-step instructions

  1. Open Wemblo -> Automations -> Appointment Booking / Marketing -> Orders / My Subscription -> Payment Gateway.
  2. Define one business purpose and owner.
  3. Create or select the required configuration.
  4. Enter the required fields and mappings.
  5. Connect the approved provider or resource where needed.
  6. Add validation, confirmation and human review.
  7. Save.
  8. Run a fictional end-to-end test.
  9. Review logs, status and customer notification.

Test and verification

  1. Complete one successful path with fictional data.
  2. Complete one invalid, failure or permission path.
  3. Confirm the result appears in the correct workspace and module.
  4. Confirm the correct person or team can review and continue the work.

Common issues and solutions

IssueWhat to Check
Configuration does not saveRequired fields, validation, permission and active workspace.
External action failsCredential, provider status, endpoint or field mapping.
Duplicate record or actionEvent ID, idempotency, retries and existing record.
Customer notification is missingTemplate, channel connection, status transition and contact details.

Security, privacy, consent, cost and provider notes

  • Use only data the business is authorized to process.
  • External provider charges, policies, approvals, limits and availability remain separate.
  • Do not expose passwords, API keys, tokens, webhook secrets, payment credentials or private customer data.
  • Use human review for sensitive, regulated, urgent, financial or final decisions.

Last reviewed: