What a completed review should leave you with
A routing readiness record naming the organization destination, non-secret key metadata, verification state, and rules that use it.
Evidence to collect
- Organization, destination display name, account identifier, and key mode metadata.
- Verification, webhook, charge, and onboarding status.
- Billing rules or defaults that point to the destination.
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 intended organization before adding or editing its routing record.
A new or rotated provider credential is being prepared.
Use the approved key mode and keep the full credential out of notes, screenshots, and worksheets.
The saved destination is not in a ready state.
Resolve verification or webhook setup issues before assigning the destination to a billing rule.
The provider status and organization setup are confirmed.
Recheck the fallback or standard route after the destination is ready.
A common mistake to avoid
Copying a full Stripe key into an operational record while trying to prove that routing is configured.
How are invoice payment destinations prepared?
Review the organization's configured Stripe destinations and the fallback or standard route used by billing. Add or update an allowed account, confirm its status, and return to billing readiness or the rule before processing invoices.
Manage the work in Granite
Granite's payment destinations workspace connects permitted Stripe accounts to billing rules and readiness.
Open dashboard ↗