Skip to content

Strawberry AI brings conversational planning to every visitor journey.

Settle · Module

Payments & Settlements

Collections, refunds, tax records and reconciliation, traceable end to end.

Overview

What it is for.

A payment is only useful operationally if it stays attached to what it paid for. Most reconciliation pain comes from that link breaking somewhere between the gateway and the ledger.

Zipr keeps collections, refunds and adjustments tied to the booking and the channel that produced them, through to the settlement run.

A card being presented to a payment terminal
Capabilities

What the module does.

Configurable payment gateway connections

Refund and cancellation workflows

Tax and GST field capture per transaction

Reconciliation and settlement tracking

How it works

Three moves, repeatedly.

  1. 1

    Collect

    Payments captured across web, kiosk, counter and partner channels.

  2. 2

    Record

    Tax fields, channel and booking references stored with each transaction.

  3. 3

    Reconcile

    Gateway settlements matched; exceptions raised for review.

Deployment

Provided and configured.

CapabilityZipr providesYou configure
GatewaysConfigurable connectionsProviders scoped per deployment
Tax recordsStructured fields per transactionRates and treatment rules
ReconciliationMatching and exception queuesThresholds and owners

Scope is agreed per deployment. Nothing listed here is enabled until it has been configured and tested with your team.

Questions

Before you ask.

  • Gateway connections are configured during onboarding; availability depends on the scope agreed for your deployment.

See payments & settlements against your operation.

We will model it with your rules, your channels and your busiest day.