Community payments

In-app payments for residential communities.

Residents pay for bookings, deposits, fees and services in the Onzane app. Every operation is linked to a property, a concept and a transaction that management can review.

A payment with context

From concept to record in four steps.

The operation starts with a real community need and ends with an identifiable transaction for both residents and managers.

  1. 01Define the concept

    The community sets what is charged, the amount and the properties it applies to.

  2. 02Choose how to pay

    The resident uses their balance, tops up by card or requests a charge to the next fee if enabled.

  3. 03Confirm the operation

    The app shows the concept and amount before completing payment.

  4. 04Keep the transaction

    The payment remains in the property history and can be reviewed in the panel.

Control from the panel

The community decides how residents can pay.

Payment methods do not have to be the same for every property. Management configures their scope and reviews operations in the management panel.

Payment method settings in the Onzane panel
01Payment methods and top-up rules
  • Enable in-app payments globally.
  • Top up the wallet by bank card.
  • Top up by charging the next community fee.
  • Apply restrictions by property, for example when debt exists.
  • Connect the community’s own payment gateway.
Top-up report in the Onzane panel
02Top-ups that management can review and export

Onzane app

Residents know how much they pay and why.

Balance, top-ups and transactions remain within the process that created the payment.

Property wallet in the Onzane app
01

Property wallet

Check the available balance before booking or paying for a service.

Card wallet top-up in the Onzane app
02

Card top-up

Add the required amount with a debit or credit card.

Wallet top-up charged to the community fee
03

Charge to community fee

Request that the top-up be added to the next fee when enabled.

Financial transaction list in the Onzane app
04

Transaction history

Review top-ups, payments, refunds and adjustments for the property.

Property wallet history in the Onzane app

Shared balance, clear transactions

The wallet belongs to the property.

People linked to the same home share its available balance. The history explains how it was topped up and used without mixing it with other properties.

  • One balance per property.
  • Top-ups, spending and refunds shown separately.
  • Concept, date and amount for each transaction.
  • Balance returned when an operation is cancelled.
  • Access in the app and control in the panel.

Payments tied to community life

Collect payment at the right moment.

Payment is built into the process that needs it, rather than becoming an isolated transfer that must be identified later.

01Booking and use

Facilities and deposits

Charge for a court, room or other facility and return the relevant amount after cancellation according to its rules.

02Community

Fees and assessments

Collect community concepts while identifying the property and reason for payment.

03In-person service

Products and services by QR

Staff can generate a QR code so the resident confirms a product or service charge on their phone.

Real process

Top up the wallet by card.

The demo shows how a resident adds balance to the property wallet with a bank card.

Before enabling payments

Questions about in-app payments.

Answers about balances, cards, fees and transaction management.

01What can a resident pay for in the app?

The community can enable bookings, deposits, fees, assessments, products and other services. The concept and amount are shown before confirmation.

02Is the wallet mandatory?

Currently available payments use the property wallet. It can be topped up only by the amount needed before the operation.

03Can several people use the same balance?

Yes. The wallet belongs to the property, so people linked to the same home can use it according to their permissions.

04Does the community need a payment gateway?

A compatible gateway in the community’s name is required for card top-ups. Onzane currently integrates with Stripe.

05Where does money from card top-ups go?

It reaches the account configured by the community with its payment provider. The net amount depends on that provider’s fees.

06Can charge-to-fee be blocked for a debtor?

Yes. Top-up methods can be enabled or disabled by property, including restrictions when debt exists.

07What happens when a paid booking is cancelled?

Onzane can return the relevant amount to the wallet according to the cancellation rules configured for the facility.

08Can transactions be used for accounting?

Yes. The panel provides top-up and transaction information for incorporation into the community’s accounting process.

Connected payments

Enable the payments your community needs.

We configure payment methods, property rules and the right journey for residents and managers.