Payments

Add a payment route

1. Choose the unit under Settings for, at the top of the page. A unit with no routes of its own shows the ones it uses from the unit above.
2. Press Add a route.
3. Type a Name people will know it by, such as “General donations” or “Event booking fees”.
4. Choose how it is paid under Paid by: a bank transfer or QR code, an outside payment page, or card payment with Stripe.
5. For a bank transfer, fill in Name on the account and the Account number, or paste the Payment QR code, or both.
6. For a payment page, choose it under Payment page and paste its Link. For Zeffy, use a Pay-What-You-Can item and a required question “Your ORG-APP booking reference” — bookers are shown the amount and reference to type.
7. Press Add the route, and confirm it's you when asked.

Then: The route joins the unit's list, and every owner and admin is told at once, in the app and by email — you included — so a change nobody expected is seen. It is recorded in the audit log. A unit's first route becomes its default for bookings, and its first bank or payment page route its default for gifts: from then on, the unit's own routes come before the unit above's.

Rather not? Press Edit beside a route to change its details, or Archive to stop offering it: it asks first, in place, and where something is still owed on it, press Archive, and move what's still owed or Archive; they keep seeing it. Whoever still owes on an archived route keeps seeing it until you press Correct its details or Move what is owed under Archived routes. A card route connects its own Stripe account on its row, with Connect Stripe.

Who: Every owner and admin is told about every change to a route, whoever made it. If nobody expected one, check this page straight away: changed bank details are how money gets diverted.

Daniel's national office takes every payment. Daniel adds one bank transfer route, “National account”, on the top unit, and every region and center now shows that account on its bookings and its Give page. Every owner and admin gets the alert by email, Daniel included.

Choose which route bookings and gifts use

1. Choose the unit under Settings for, at the top of the page.
2. Find Defaults, under its routes: what bookings and gifts use now.
3. Press Change the defaults: they open at the side.
4. Choose a route in Bookings.
5. Choose one in Gifts: a bank transfer or a payment page.
6. Press Save the defaults, and confirm it's you.

Then: A program or fund at that unit, or at a unit below it with no routes of its own, that picks no route of its own is paid through these. Defaults says what bookings and gifts use now, and What a booker sees shows the bookings route as a booker reads it, with an example amount. Every owner and admin is told. Under the defaults, for whoever sets the routes up (a proposer sees only how many programs pick each route), Programs on the bookings default lists the programs still taking bookings that picked no route, and Programs with their own route those that did, with the route each uses: press a program's name to open How bookings are paid in its Settings › Tickets, or on its Money tab if you keep its money but do not run it.

Rather not? Give a unit no routes of its own and it uses the nearest unit above it, so the whole organization can share one account set up once on the top unit.

A center takes donations into its own account and event fees through Zeffy. Grace adds both routes there, then presses Change the defaults, chooses the Zeffy route in Bookings and the account in Gifts, and presses Save the defaults. The center's Give page now shows the account, and its bookings the Zeffy button.

Let a program or a fund use its own route

1. Under How bookings are paid — in a program's Settings › Tickets, beneath the tickets, and on its Money tab — choose a route in Paid through: one of the program's unit or a unit above it.
2. Press Save, and confirm it's you.
3. If bookings made earlier have paid part, a note opens saying how many and how much: read it, then press Move them too or Keep them on the route they were told.
4. For a fund, open Thank-yous and find How gifts to each fund are paid.
5. Choose the route beside the fund's name, and press Save.

Then: Bookings made from now are told the route picked, and so are the program's bookings made earlier that have paid nothing; bookings paid in full are not touched, because nothing is owed. Nobody who booked is sent a message: their booking page, reminders and card button show the new route from then. Gifts to the fund are shown its route from now. A program or fund left on the unit's default follows whatever the default becomes.

Rather not? Choose the first line, the unit's default, to go back to the route the unit uses. Where bookings made earlier are still told another route, How bookings are paid says how many: press Move them to the program's route to move them by the same rules.

Who: A program's is picked by whoever keeps its money — its unit's Finance officers too, as well as whoever runs it — and a fund's by whoever keeps its book. Only routes an owner or admin has set up are offered.

Sokha keeps a youth camp's money. On its Money tab, under How bookings are paid, Sokha chooses the region's Zeffy page instead of the unit's bank account and presses Save. The next booking is shown the Zeffy button, with the amount and its booking reference to type.

Propose a change, or approve one

1. As a unit's coordinator or finance officer, press Propose a new route, or Propose a change beside a route.
2. Type the details as they should be. The account number, QR code and link are hidden from you: type them again, or a blank one is proposed as removed.
3. Press Propose it, and confirm it's you.
4. As an owner or admin, read it under Waiting for approval: each line that changes, as it is now and as proposed.
5. Press Approve and apply. Or press Decline…, write why in Why it is declined, and press Decline.

Then: Proposing changes nothing: every owner and admin is told at once, and nobody paying sees a difference until one of them approves it. Approving applies it, records it, and tells every owner and admin who proposed it and who approved it. Whoever proposed it is told either way, with the reason when it is declined.

Rather not? Press Withdraw under Your proposals while it waits, then Withdraw it, to take it back. Archiving a route and the unit's defaults are proposed the same way, with Propose archiving, and with Propose new defaults then Propose these defaults.

Who: A unit's Unit coordinator or Finance officer proposes; the organization's Owners and Admins decide. Nobody approves their own proposal: another owner or admin does.

Mary Ann, a center's finance officer, hears the bank has given the center a new account. Mary Ann presses Propose a change on “Center account”, types the new number and presses Propose it. Daniel, an admin, reads the old and new number side by side and presses Approve and apply, and Mary Ann is told it was approved.

If people booking cannot see your payment details

1. Your organization is not verified yet. Until it is, the public sees no bank details, payment QR code or payment page on a booking, and no paid places, so nobody can take money in your name.
2. Press Ask to be verified in the notice at the top of this page.
3. Set up your routes meanwhile: they appear the moment your organization is verified.

Who: ORG-APP checks who runs your organization before anybody can pay it. There is no timer: it waits until that check is done.