Quick Pay links

Overview

Quick Pay lets you create standalone payment requests and share a guest checkout link with a customer. Those payments are tracked like other guest payments in Mallard Bay, but they are not created through a listing or booking checkout. Quick Pay is for collecting money when you do not need (or do not yet have) a full booking—for example, deposits taken over the phone, balances for custom arrangements, merchandise, or reimbursements.

Quick Pay is guest payment collection for your business. It is not the same as your Mallard Bay subscription billing.

Prerequisites

• Quick Pay on your plan — The Quick Pay area is wrapped in the same plan feature gate as other add-ons in the dashboard. If you see messaging that the feature is unavailable, you need Quick Pay enabled on your Mallard Bay plan (contact Mallard Bay support or your account manager).
• An outfitter selected — If no outfitter context is selected (common for some internal admin views), the screen asks you to select an outfitter before Quick Pay loads.
• Payment processing — When you choose to enter payment details now in the create/update flow, the dashboard collects card details through the standard Stripe Payment Element flow. Exact payout and Stripe onboarding behavior depends on how your Mallard Bay account is configured; this dashboard repository does not spell out those backend rules.

It is unknown from this codebase alone whether Mallard Bay can automatically email the payment link to the guest, what the full guest-facing URL looks like (domain and path), and how sales tax is calculated when you turn on tax collection—the API accepts a “include taxes” flag on create, but the dashboard does not document tax logic here.

Using Quick Pay in the dashboard

Open Quick Pay

Open Quick Pay in the admin dashboard (route /quick-pay). The exact spot in the sidebar or menus may vary by navigation setup; if your account uses global search, Quick Pay may appear there as well.

Review the list

The main table shows one row per Quick Pay payment with:

• Due date (from the payment’s date field),
• Customer name,
• Amount,
• Net (amount attributed to the outfitter after fees),
• Status (same status model as other payments),
• Notes.

Use the status filter (same payment statuses as elsewhere—includes values such as pending, success, failed, etc.) and pagination to work through the list. Click a row to open its detail page.

Create a Quick Pay

1. Select Create Quick Pay (primary action on the Quick Pay page header).
2. Fill in the form:
   • Amount (required, must be greater than zero).
   • Name, Email, Phone — Phone is optional. If QuickBooks is connected for your outfitter, name and email are required so Quick Pay transactions can sync; the form shows a QuickBooks banner explaining that.
   • Note — Optional internal or customer-facing note; appears in the list “Notes” column.
   • Would you like to collect tax for this payment? — Shown only when creating (not when editing). Sends a should include taxes flag to the server on create; how tax is computed is not described in this dashboard code.
   • Would you like to enter payment details now? — If yes, after you save, the modal continues to a step where you enter card details via Stripe’s Payment Element and submit; on success the modal can close with a success confirmation.
   • Would you like the client to cover the processing fees? — Overrides your outfitter default for whether the guest pays card/ACH processing fees for this Quick Pay only.
3. Submit with Create (or Continue if you chose to collect payment now).

If you do not collect payment in the modal, the payment is created and you can share the link from the list or detail view (see below).

Share the checkout link or QR code

For payments that are still pending and have a payment_url from the server:

• Use Copy link from the row menu or the detail Actions panel to copy the guest checkout URL.
• Use View QR code to show a QR code for that same URL (modal on the list; inline QR section on the detail layout when a URL exists).

Sharing is manual from your side (copy/paste, QR, your own email/SMS). This repo does not show an automatic “email link to guest” button for Quick Pay.

Open and manage a single Quick Pay (/quick-pay/:id)

The detail page shows:

• A back control to return to the Quick Pay list.
• Customer contact details (and a mail shortcut when email is present).
• Actions: Edit, Copy link, View QR code, Cancel, or Manage refunds, depending on status (see rules below).
• Payment details and fee / breakdown sections consistent with other payment detail views.
• Notes tied to the payment.

Edit an existing Quick Pay

Edit is only offered while status is Pending. In edit mode:

• Amount cannot be changed (disabled in the form).
• You can update customer fields, note, and whether the client covers processing fees.
• Tax toggle is hidden on edit (tax choice applies at creation only).
• You can still turn on enter payment details now to run the in-modal Stripe step for an existing pending Quick Pay.

Cancel or refund

• Cancel — Available for Pending or Failed payments (opens the same cancel flow used elsewhere for payments).
• Manage refunds — Available when status is Success and the payment is not marked offline. Offline successful Quick Pay payments do not show refund management in this UI.

Common pitfalls

• QuickBooks — With QuickBooks enabled, missing name or email will fail validation even though those fields are optional without QuickBooks.
• Cannot change amount after creation — Plan the correct total before creating; edits only adjust customer info, notes, fee payer, and optional immediate card capture for pending items.
• No link tools unless pending + URL — Copy link and QR code require Pending status and a non-empty payment_url. If something went wrong server-side and no URL exists, those actions will not appear.
• Mixing up with booking payments — Booking checkout and booking-linked installments live under bookings and listing flows. Quick Pay rows do not open a booking drawer from the mixed Payments report; they open Quick Pay–specific detail UI instead.

Related workflows (from the codebase)

• Payments (reporting) — The outfitter Payments report lists all payments; rows flagged as Quick Pay open Quick Pay detail in a drawer rather than the booking drawer.
• Payouts — Payout transaction lines that reference a Quick Pay payment can show View Quick Pay and open a Quick Pay details drawer instead of “View booking.”
• Notification logs — For log rows whose entity is a Payment, the UI label View Quick Pay can route you to the Quick Pay detail route for that payment id.
• Automations / templates — There is a global automation-oriented template named along the lines of Quick Pay Receipt / Payment Received for guest messaging. How and when that template is triggered in production is not defined in this dashboard repository.

If you rely on tax-inclusive Quick Pay or automated guest emails, confirm behavior with Mallard Bay support or your onboarding contact—the dashboard sends flags and displays fields, but tax rules and notification automation are largely outside this app’s source tree.