Payment

Configure the payment gateway credentials, and the bank account residents transfer to when paying manually.

view
get
create
update
delete

What it’s for

This is where the developer’s payment setup lives: gateway credentials for online payments, and the bank account details residents see when they’re expected to pay by manual transfer instead.

Where to find it

Sidebar → Settings → Payment, at /admin/settings/payment.

Who can use it

See the menu item and open the page — needs view.
See the configuration list — needs get.
Create, edit, delete — each needs its own permission.

On this screen

A table of payment configurations, with create, edit, and delete.

How to…

Add a payment configuration

Click create.
Enter a title and pick the payment type (currently Midtrans).
Enter the gateway credentials: merchant key, server key, merchant ID, and the callback finish URL.
Optionally set a transaction fee.
Mark whether it’s running in production.
Fill in the manual-transfer bank details — bank name, account number, and account holder — if this developer has any cluster set to offline resident payment.
Set it Active or Not Active.
Save.

Field reference

Field	Required	Notes
Title	Yes
Payment type	Yes	Midtrans
Merchant key, server key, merchant ID, callback URL	No	Gateway credentials
Transaction fee	No
Production	Yes	Live vs. sandbox
Bank name, account number, account holder	No	All three must be filled for the resident app to show transfer instructions at all
Status	Yes	Active / Not Active

Rules & statuses

The bank details here are exactly what shows up as manual-transfer instructions for a cluster whose resident payment method is set to offline, on Housing Cluster. Leave any of the three blank and the resident app has nothing to show.

Housing Cluster — where a cluster is set to online or offline resident payment.
IPL Bill — where manually-transferred payments get reviewed and confirmed.
See the full payment flow → — how these credentials and bank details actually get used on the resident side.