Onboard the payee directly
Affiliate payout-account state is tied to the connected account without exposing provider credentials to the portal.
Stripe Connect integration
Separate affiliate account onboarding, operator approval and tenant-funded transfer execution while retaining provider identity and retry evidence.
Built for operating reality
Affiliate payout-account state is tied to the connected account without exposing provider credentials to the portal.
The tenant provider connection owns the transfer context rather than hiding funding behind a shared platform balance.
Immutable rail-attempt identity and exact idempotency replay protect against duplicate sends after timeouts.
Account boundary
AffiliateRails retains the connected-account identity and onboarding state required for programme operations without collecting bank details in the affiliate portal.
Settlement boundary
An approved payout item receives one durable rail-attempt identity. Inconclusive responses remain unknown until a strong provider result resolves them.
Questions, answered
Stripe’s connected-account onboarding surface collects provider-required payout information; AffiliateRails retains the account and readiness state.
The integration is designed around the tenant’s Stripe connection and tenant-funded transfer context.
The attempt remains unresolved until an exact replay or provider lookup returns a strong result. A timeout alone never authorises a second transfer.
Build the reliable path