Payments

Overview

Payments in the Mallard Bay mobile app help outfitters and guides collect, review, share, refund, and record guest payments while working from a booking or payment workflow in the field.

Mobile payment workflows use these screen contexts: CreateAdditionalPayment, AdditionalPayment, SharePaymentRequest, PaymentDetails, CreateRefund, and GroupMemberUpdate.

Request or Record a Booking Payment

From a booking, use the booking actions menu and choose Request Payment when that option is available. This opens CreateAdditionalPayment and the AdditionalPayment payment form.

In this flow, you can:

• Add payment line items and amounts.
• Include unpaid balances.
• Add eligible add-ons to the payment.
• Review the payment summary before confirming.
• Choose how the payment will be collected.

Mobile supports payment request methods such as email invoice, QR code, saved card, and Stripe Terminal when terminal payments are enabled for the outfitter. It also supports recording offline payments as cash, check, or other.

Share a Payment Request

When a QR code payment request is created, the app opens SharePaymentRequest.

This screen shows a shareable payment request link and QR code so the guest can open the payment request from their own device. Existing requested payments can also show a Share Payment Request action from the booking payment request list when the request is still active.

Take In-Person Payments

For eligible requested payments, mobile can send the payment to Stripe Terminal from the booking payment request actions. Pending payment details can also show a Terminal Payment action from PaymentDetails.

If a pending online card payment can be processed on device, PaymentDetails may also show Process Card Payment. Pending payment links can be copied from the same screen when a payment URL is available.

Review Payment Details

Use PaymentDetails to inspect a payment before taking action. The screen can show customer details, payment ID, status, due date, payment method, amount, booking fee, processing fee, outfitter fee, sales tax, outfitter net, and notes.

For pending payments with a payment URL, the app can show a QR code and a copy-link action. Pending or failed payments can also be canceled from the payment details menu when that action is available.

Manage Booking Payments

On a booking, the Payments section lists existing payments. Depending on permissions and payment status, the payment menu can include actions to:

• View payment details.
• View refunds.
• Update the due date for a pending future payment.
• Mark an unpaid payment as paid.
• Change the payment method for a pending non-offline payment.
• Delete an offline payment.

The booking can also show Payment Requests and Unpaid Balances as separate sections. Payment requests can be shared, accepted on device, or marked as paid offline when their status supports the action. Unpaid balances can be canceled or reactivated when they are pending or canceled.

Create Refunds

From a booking payment’s refunds view, use the add action to open CreateRefund.

The refund form requires an amount, approver name, Stripe refund reason, user-facing reason, and whether the outfitter is responsible for the refund. After the refund is created, the app refreshes booking payment data and returns to the previous screen.

Group Pay Payments

For group pay bookings, the booking payments area groups payments by group member. Guides can review each member’s payment list and open the member menu for non-host members.

GroupMemberUpdate lets the team update a group member’s name, email, and phone number. This supports payment follow-up when a group pay member’s contact information needs to be corrected in the field.