JCC payment gateway integration
Unitify connects to JCC's payment gateway so buildings in Cyprus can accept card payments directly through the resident app.
What it does
Card payments run through JCC's gateway with a dedicated production and test host, per-organization API credentials, and nine order states with five callback operations mapped to Unitify's own payment statuses.
How it works
- 1
Resident opens an invoice
The resident app shows the amount due for the building.
- 2
JCC's gateway processes the card
JCC's own payment gateway collects the card details.
- 3
Callback confirms and reconciles
JCC's callback reports the final order state; Unitify marks the invoice paid.
Where this runs
JCC acquiring is built for one market.
- Cyprus
Frequently asked questions
Is there an active Cyprus deployment today?
The JCC adapter is built and registered in production code; Cyprus isn't yet one of Unitify's published markets — ask your Unitify contact about current availability.
Does Unitify support the JCC gateway API?
Yes — Unitify's JCC integration processes card payments through JCC's gateway API, with all nine of JCC's order states mapped through five callback operations, so a payment's status is never guessed at.
Is there a test environment?
Yes — JCC's gateway has a separate test host from production, for verifying the integration before going live.
How are credentials configured?
Each organization has its own JCC API username and password, set per organization rather than shared.
Start free — no card, no expiry
The $0 plan is real: core features, unlimited users and properties.