Payme integration for utility payments
Unitify processes residents' card payments in Uzbekistan through Payme's Merchant API, right inside the resident app.
What it does
Unitify implements Payme's Merchant API directly: transactions move through the four states Payme defines (pending, paid, canceled, paid-canceled), with the documented cancel reasons handled automatically and a dedicated webhook endpoint. Each organization has its own cashbox configured with Payme.
How it works
- 1
Resident opens an invoice
The resident app shows the amount due for the building.
- 2
Payme processes the payment
Unitify talks to Payme's Merchant API directly, not a generic webhook, so a payment's state is always known.
- 3
Status updates automatically
Payme reports status to Unitify's own Payme route, and the invoice updates without a manual step.
Where this runs
Payme acquiring is built for one market.
What it doesn't do
Payme is the payment method Unitify actually processes. Click is a channel Uzbekistan residents already use for housing payments on their own — it is not connected to Unitify, and payments made there don't reconcile automatically the way Payme payments do.
Frequently asked questions
Is this a live merchant account or a sandbox?
The Payme integration is built and registered in production code; confirm your organization's live merchant status with your Unitify contact before relying on it for collections.
Does Click work the same way?
No — Click is a rail residents already use, not a Unitify integration. Only Payme payments reconcile automatically in Unitify's billing.
What happens if a resident cancels a payment?
Payme's own documented cancel reasons are handled automatically, and the invoice status updates to match.
Do we need a separate Payme merchant account?
Yes — each organization configures its own cashbox with Payme; there is no shared Unitify account.
Start free — no card, no expiry
The $0 plan is real: core features, unlimited users and properties.