Steps for payment destination setup
- 01
Open Billing, then Payment destinations under Setup, and review each Stripe account you’ve connected.
- 02
Check the default payment destination and the one each rule uses.
- 03
Add or update a Stripe account if your role allows it.
- 04
Confirm the account is ready, then return to the rule or billing checks.
What the finished work leaves you with
A record of the payment destination, the organization it belongs to, non-secret account details, verification status, and the billing rules that use it.
What to do when the review finds a problem
More than one organization or Stripe account is in view
Confirm the destination belongs to the right organization before adding or editing it.
You are adding or replacing a Stripe key
Use the approved key mode and keep the full key out of notes, screenshots, and worksheets.
The saved destination is not ready
Fix verification or webhook setup before assigning it to a billing rule.
The Stripe status and organization setup are confirmed
Check the default destination again once this one is ready.
A common mistake to avoid
Copying a full Stripe key into a record to prove that payments are set up.
Franchise payment destination setup checklist
Use this checklist when setting up where franchise card payments are deposited. It confirms the organization, the Stripe account status, which billing rules use the destination, who can change it, and the readiness check, so the destination has a clear owner and works before billing.
Before you start
- Open Payment destinations under Billing setup for the right organization.
- Find the default or backup destination the billing rule expects.
- Confirm which role can add or change the payment account.
When a billing payment destination is not ready
A payment destination can exist but not work, point to the wrong Stripe account, or still be waiting on Stripe verification. Check which account it is and whether it is ready before adding it to a billing rule, and never put login details in notes.
The payment destination doesn’t appear under Payment destinations.
Check first
- Confirm your role lets you see payment destinations.
- Check whether it was set up under another account or is still partway through setup.
- Compare the destination name and Stripe account shown with the setup request.
Next action
Fix your access, or ask whoever set it up to finish it. Do not add a second destination until you know what happened to the first.
Confirm the result
Your account shows one destination with a readable account name, status, and owner.
The rule sends payments to a different destination than expected.
Check first
- Compare the destination on the rule with your default destination.
- Check whether an older active rule still applies to that period.
- Confirm the destination shown is the one your team intended.
Next action
Agree with the billing owner which destination should apply, then update the rule or the default. Keep the old destination visible for periods it already covered.
Confirm the result
A sample rule and period show the intended destination with no conflict.
The payment destination is still waiting for verification.
Check first
- Read the current verification status and the reason it is pending.
- Check whether account details or permissions are still missing in Stripe.
- Confirm no active billing rule is using it while it is not ready.
Next action
Finish the missing setup with the Stripe account owner, then check the status again. Keep affected rules off until Stripe confirms the account, and never paste secrets into notes.
Confirm the result
The destination shows as ready or gives a clear reason it is blocked, and any rule using it shows the same.
A destination change seems to save, but billing still shows the old status.
Check first
- Compare when the destination was updated with when the rule was last checked.
- Refresh the destination and confirm the saved account details.
- Check whether the rule points to a different destination.
Next action
Work out with whoever set it up which destination the rule uses, then check the rule again. Do not keep re-entering account details while that is unclear.
Confirm the result
The destination, the rule, and the billing preview all show the same destination and status.
When you need to hand it on
- Include the destination name, account ID, current status, the billing rule, and when it changed.
- Never include passwords, secret keys, or login tokens in the note.
- Send Stripe verification or permission questions to the person who owns the Stripe account.
Link to the record instead of copying passwords or unrelated personal details into your note.
A situation to work through
Two franchises need different payment destinations, and the organization also has a default one. The admin checks who owns each account, the currency, which franchises use it, and the default before saving.
Confirm each destination’s account, currency, franchises, and status, and check the default destination before invoices go out.
This is a planning example, not a customer result.
How are invoice payment destinations set up?
Review the Stripe accounts your organization has connected and the default payment destination your billing rules use. Add or update an account if your role allows it, check that it is ready, then go back to the rule or billing checks before you run billing.
Put the workflow into practice
In Granite, each fee can be paid into a different Stripe account you own, and billing warns you when a rule has nowhere to send payments.
Set it up in Granite with your own franchises, reporting periods and billing rules.