Stripe payouts for partners

Before connecting Stripe

Select the correct store first. Provider availability, currency, holding period, threshold, payout policy, preferred destination, and history are all store-specific.

Stripe must be operational and enabled by the merchant. If the card says Unavailable, use Notify merchant; connecting a personal Stripe account elsewhere does not enable it for this store.

ScreenshotEnd-to-end flow

Local image

View full-size image: Partner Stripe payout flow

Part 1: connect your Stripe payout destination

1. Open Payout Settings for the intended store.
2. Find Connected payout destinations.
3. On Stripe bank payout, choose Connect with Stripe.
4. Affilyn creates a connected account under the selected merchant's Stripe platform and opens Stripe-hosted onboarding.
5. Enter accurate legal, identity, business, website or product, and banking information on Stripe's hosted pages.
6. Complete identity, business, website/product description, and bank destination steps requested by Stripe.
7. Submit until Stripe returns you to Affilyn.
8. Affilyn refreshes and stores only safe destination information: encrypted recipient/account ID, masked destination, country, currency, account type when safe, verification state, and outstanding requirements.
9. Confirm the card shows a usable destination. If setup is incomplete, choose Complete setup and finish the remaining Stripe requirements.

Affilyn never asks you to type raw bank account or routing details into the Partner Portal. Those details belong only on Stripe-hosted pages.

Part 2: choose the preferred destination

If multiple providers are connected, exactly one is Preferred.

• Future automatic payouts use only the preferred verified provider.
• An on-request payout may show a provider selector when more than one provider is ready.
• Selecting a provider for one request snapshots that provider without silently changing the preferred destination.
• Affilyn never falls back from Stripe to another provider when Stripe is unavailable.
• Reserved, processing, and completed payouts retain their original provider and masked destination snapshot.

Destination controls explained

Part 3: understand your payout balance

When earnings move from pending to available, the portal balance updates and the partner receives an availability email.

Part 4A: request a payout

The Request payout button is enabled only when all conditions pass:

• Stripe is enabled and operational for the selected store.
• Your Stripe destination is verified.
• The payout currency is supported and matches the eligible commissions.
• Available finalized balance meets the effective minimum.
• The optional maximum is valid.
• No request or payout is already active.
• The store permits partner requests or early requests.

To request:

1. Review Available now, Minimum payout, and the selected provider.
2. If multiple providers are ready, choose Stripe payout destination under Send this payout through.
3. Choose Request payout.
4. Affilyn calculates the amount on the server and reserves the selected commission rows transactionally.
5. Review the new Current payout status and request-confirmation email.
6. If merchant approval is required, wait for the merchant. Do not submit another request.

Part 4B: automatic payout behavior

When the merchant selects weekly or monthly automatic payouts, you normally do not need to request payout.

At the scheduled UTC time, Affilyn checks your preferred Stripe destination, currency, available balance, threshold, holding period, cap, active payout state, and merchant provider readiness. If a check fails, the payout is skipped; Affilyn does not switch providers. Resolve the displayed issue before the next run or contact the merchant.

Part 5: follow the payout lifecycle

Part 6: review history and notifications

Open Payout History to see amount, provider, immutable masked destination, provider reference, timestamps, and final status. Sensitive account details are never shown.

Expected emails include:

1. Earnings became available.
2. Payout request submitted.
3. Merchant approved the request.
4. Stripe payout is processing.
5. Payout completed, failed, or reversed.

Approval is not proof of payment. A payout becomes complete only after Stripe webhook or authoritative reconciliation confirms settlement.

First live payout checklist

1. Confirm the selected store shows Stripe as available.
2. Choose Connect with Stripe and complete the live Stripe-hosted onboarding with accurate information.
3. Return to Affilyn and confirm Stripe is connected, verified, and preferred.
4. Wait until finalized commissions pass the holding period and appear under Available now.
5. Confirm the available balance meets the store's effective threshold.
6. Submit Request payout, when the store permits requests, and verify the confirmation email.
7. If merchant approval is required, wait for approval and its notification.
8. Confirm the payout changes to processing only after Stripe accepts the live transfer.
9. Do not submit another request while processing.
10. After webhook or authoritative reconciliation, confirm paid/completed, zero reserved balance, an immutable history record, and the completion email.
11. Allow for the partner bank's delivery timing after Stripe marks the transfer successful.

Troubleshooting

Merchant sees Stripe Ready but partner sees Unavailable

The merchant must also enable Stripe in Methods available to partners. Confirm both pages use the same store and live Stripe environment, then refresh provider status and reload the partner page.

Stripe onboarding returns but setup is still required

Choose Complete setup or Refresh status. Stripe may require a website, product description, identity information, or a valid external account before enabling payouts.

Request payout is disabled

Read the message beside the button. Common causes are insufficient available balance, holding period, unverified destination, requests disabled by policy, currency mismatch, or an existing active payout.

Payout remains processing

Processing means Stripe accepted the transfer, not that settlement is complete. The merchant should confirm webhook delivery or run authoritative reconciliation. Do not reconnect or submit another request.

Completion email did not arrive

Verify the email on your partner profile and check spam. The email is sent only when the request actually transitions to paid; replaying reconciliation for an already-paid record does not send a duplicate.