Processor: Walletdoc
Walletdoc is a V2 payment processor configured at the organization level via the unified onboarding flow. It supports card-reader transactions, manual card entry, hosted-payment-page iframe, tokenization (global), and card-on-file storage through WalletdocStoredAccount.
Before you begin
Permission: Organization administrator access is required to configure Walletdoc.
Walletdoc merchant-side prerequisites
- Active Walletdoc merchant account activated for your region and settlement currency.
- Card-reader provisioning (optional) β for centers using terminals, Walletdoc pairs each reader to the MID (Merchant Identifier).
- HPP (Hosted Payment Page) iframe allow-list β Walletdoc must know the Zenoti domain that will host the payment iframe.
Credentials
Walletdoc uses the V2 onboarding flow; fields are collected step-by-step in the Zenoti onboarding wizard.
| Field | Source / owner | What to enter |
|---|---|---|
| Walletdoc API credentials (merchant key / secret) | Walletdoc account representative | Entered through the V2 onboarding wizard. Zenoti does not provide defaults. [SOURCE GAP β PM VERIFY: exact field names in the V2 onboarding wizard.] |
Network requirements
| Direction | Port | Protocol | Why |
|---|---|---|---|
| Outbound from Zenoti to Walletdoc API | 443 | HTTPS | Charge, refund, tokenize, status |
| Outbound from guest browser to Walletdoc HPP iframe | 443 | HTTPS | Hosted iframe card entry |
| Outbound from Walletdoc card reader to Walletdoc | 443 | HTTPS | Terminal-integrated payments |
Walletdoc capabilities in Zenoti
| Capability | Supported |
|---|---|
| Sale | Yes |
| Refund | Yes |
| Void | [SOURCE GAP β PM VERIFY: no VoidTransaction override in code; same-day cancellations may route through refund.] |
| Card reader (terminal) | Yes |
| Manual card entry | Yes |
| Hosted payment page (iframe) | Yes |
| Stored accounts | Yes |
| Global tokenization (cross-processor) | Yes (rare β one of the few V1/V2 processors with this) |
| Recurring payments | Yes |
Configure Walletdoc
Walletdoc uses the V2 onboarding flow at the organization level. Do not attempt to configure it at the center level.
- Navigate to Configuration > Payments > Process payments > Payment processor onboarding.
- Select Walletdoc.
- Work through the onboarding wizard to enter your Walletdoc merchant credentials.
- Configure card-reader assignments for each center where physical terminals are used.
- Assign the processor to the centers.
- Select Save.
- Select Test to verify.
Toggle interactions
| Terminal | HPP iframe | Card-on-file | Behaviour |
|---|---|---|---|
| Off | Off | Off | Walletdoc unavailable. |
| On | Off | Off | Walk-in terminal only. |
| Off | On | Off | Online HPP iframe only. |
| On | On | Off | Walk-in + online, no stored cards. |
| * | * | On | Cards stored for return guests and recurring billing. Recommended for membership businesses. |
Process a payment
Terminal: standard card-reader flow. HPP iframe: embedded card entry on the Zenoti page; no redirect. Card-on-file: staff selects a stored card and charges it.
Process a refund
Refund β dual-system perspective
| System | What happens |
|---|---|
| Zenoti | Negative payment line; Collections report shows the refund row. |
| Walletdoc | Separate refund record in the Walletdoc merchant portal linked to the original transaction. Match key: Walletdoc transaction reference or Zenoti invoice number. |
Edit or reverse a posted payment
| Invoice state | What you can do |
|---|---|
| Open | Remove the payment line and refund if the charge has gone through. Because void is not confirmed, same-day cancellations use refund. |
| Closed | Reopen if permissions allow, or post a compensating refund. |
Failure modes
| Failure mode | User-visible symptom | Resolution |
|---|---|---|
| Walletdoc unreachable | HPP / terminal / card-on-file flow fails. | Check HTTPS and Walletdoc status. |
| Authentication | All transactions fail with auth error. | Re-run the V2 onboarding wizard to refresh credentials. |
| Card declined | Issuer decline. | Guest retries. |
| Amount out of range | Rejected. | Per-MID limits; contact Walletdoc. |
| Currency mismatch | Rejected. | Confirm center currency matches Walletdoc's activated currency. |
| Settlement failure | Approved but missing from settlement. | Raise with Walletdoc using the transaction reference. |
| Terminal pairing mismatch | Terminal fails. | Re-pair the reader with Walletdoc support. |
Settlement and reconciliation
Settlement cadence is region-specific. [SOURCE GAP β PM VERIFY: exact T+N per market.]
| Source | Report / view | Match key |
|---|---|---|
| Zenoti | Collections report (filter: Payment Method = Walletdoc) | Walletdoc transaction reference + Zenoti invoice number |
| Walletdoc | Walletdoc merchant portal settlement report | Same fields |
Recommended cadence: daily.
Tips
- The hosted payment page option allows guests to complete payments via a Walletdoc-hosted iframe, suitable for remote or online payment scenarios.
- Verify the card reader device is linked to the correct Walletdoc terminal configuration before accepting live payments.
- Walletdoc is one of the few processors in Zenoti with global tokenization β stored cards can be shared across Walletdoc instances in the same organization.