What we are building next

The partner-facing half of this is built and switched off. The part that touches Stripe itself is not built, and is deliberately blocked until some production payment problems are fixed.

Built: a partner can see the status and send a reminder

A partner sees one of the five words on this chapter's status page, and can send the owner a reminder. The reminder emails the owner and tells the partner it was sent — it never hands the partner a link.

The distinction is deliberate and permanent: an onboarding link leads to a form containing someone's identity documents. Partners get a send button and a timestamp. Owners get the link.

A partner also never sees what Stripe is asking for. That is the owner's personal information.

Not built: a partner starting onboarding, and readiness as a hard gate

Both are designed and blocked until existing production payment problems are resolved. Do not describe either as coming soon.

Not built: automatic reminders

Nudges are manual. The partner dashboard surfaces a venue that is stuck; nothing sends on a timer.

Important notes

If a venue asks whether you can set up their payments for them, the answer is no — and for the sensitive parts it will always be no. Stripe collects business, identity and bank details directly, from the venue's own authorised representative. That does not change.