Docs
Payments & Refunds

Payments & Refunds

The dashboard-wide payments page — every charge across every release, with filtering and refund tools.

The Payments page is your full ledger of charges. Unlike the per-release Payments tab (which scopes to one release), the global Payments page shows every charge in your organization, filterable by status, release, contact, and method.

The Payments page

dashboard.oncloudwine.com

Payments

Total 2,184 payments · $478,290 captured this year

ContactReleaseAmountMethodStatus
Alex ChenSpring 2026 Reds$192.00Stripe •• 4242COMPLETED
Casey LeeSpring 2026 Reds$168.00Square •• 1234FAILED
Jordan PatelLibrary Reserve Q1$420.00Stripe •• 0005COMPLETED
Sam RiveraHoliday Mixed Pack$240.00Stripe •• 9876PROCESSING

Statuses recap

StatusMeaning
PENDINGGenerated, not yet attempted.
PROCESSINGIn flight with the processor.
COMPLETEDSuccessfully captured.
FAILEDDeclined or errored. Failure reason on the record.

Payment methods

MethodSource
STRIPECard on file via Stripe. Most common for online wineries.
SQUARECard on file via Square. Common for wineries with both POS and online presence.

A contact can have one card on file per processor. The portal is where they manage these — see Member Self-Service.

Filters in detail

Release

Single-select. Useful for reconciling a specific release post-shipment.

Status

Multi-select. The default view excludes PENDING (which are operational noise on a global page) and shows everything else.

Method

Multi-select. Filter to STRIPE or SQUARE only.

Date range

Captures the charge attempt date, not the release date. Useful for matching to your processor's deposit reports.

Refunding a payment

Refunds happen at the payment level — same flow whether you got here from the global Payments page or a release's Payments tab.

  1. Open the payment

    Click any COMPLETED payment row.

  2. Click Refund

    Choose full or partial.

  3. Enter the partial amount (if applicable)

    Cannot exceed the original charge minus any prior refunds.

  4. Add an internal note

    Customer-facing reason (the email they receive) and the internal note (visible only to your team) can be set separately.

  5. Confirm

    The refund is sent to the processor. The payment record stays COMPLETED with a new "Refunded" badge and a timeline entry.

Reconciliation tips

Failed payments triage

Use the global Payments page filtered to Status: FAILED to see every failed charge across every release. This is where to spend 10 minutes a week to keep your aging clean:

  1. Sort by oldest first

    Failures over a week old are unlikely to self-resolve.

  2. Email the member or call

    Most failures need a new card. The portal makes it easy for them.

  3. Retry once they update

    Click into the payment and Retry.

  4. Cancel if unresponsive

    For fully unresponsive members after multiple attempts, mark the fulfillment cancelled and consider moving the contact to ON_HOLD.

What's next?