MerchantStandard AffiliateVIP PartnerReference
Stripe payout questions and answers
Production-focused answers about merchant-owned Stripe funding, partner onboarding, payout eligibility, approval, automatic schedules, statuses, security, and troubleshooting.
Last reviewed: Sep 14, 2026UI path: Merchant dashboard → Payouts; Partner Portal → Payout Settings
Summary
Production-focused answers about merchant-owned Stripe funding, partner onboarding, payout eligibility, approval, automatic schedules, statuses, security, and troubleshooting.
When to use this page
- You need a quick answer about live Stripe payout setup or behavior.
- A Stripe provider, destination, balance, request, or status does not look as expected.
Before you start
- Know whether your question concerns the merchant Stripe account or the partner payout destination.
Success looks like
- You understand which action belongs to the merchant and which belongs to the partner.
- You know whether to wait, update setup, retry safely, or contact Affilyn support.
Where to find it
Merchant dashboard → Payouts; Partner Portal → Payout Settings
Setup guides and flow diagrams
- Merchants: start with Stripe payouts for merchants for the ownership diagram and the provider setup, approval, and settlement instructions.
- Partners: start with Stripe payouts for partners for the destination, eligibility, request, and settlement diagram and onboarding instructions.
- Wrong store or missing destination: use the store-context guide, which includes desktop and Arabic mobile navigation screenshots, before following the Stripe setup steps.
The Stripe visuals are flow diagrams, not screenshots of Stripe-hosted onboarding. Follow the instructions shown by Stripe when entering bank or identity information.
Stripe payout FAQs
1. Does Affilyn hold or supply Stripe payout funds?
No. The payout is funded from the merchant's own connected Stripe balance and delivered by Stripe to the partner's connected destination. Affilyn coordinates authorization, eligibility, status, and records without holding the money.
2. What does the merchant need before connecting Stripe?
The merchant needs a live Stripe account with Connect access, completed Stripe business verification, a live write-only credential, and enough available balance to fund payouts and applicable provider fees.
3. Why is a valid Stripe key not enough?
A key can identify an account without granting the Connect capabilities needed to create and manage partner destinations or submit transfers. Affilyn verifies the required payout capability separately before showing Stripe as Ready.
4. What do Connected, Ready, and Enabled for partners mean?
Connected means Affilyn validated the merchant authorization. Ready means the required Stripe payout capability is operational. Enabled for partners means the merchant has made Stripe selectable for partners in this store. All three are required for normal partner onboarding.
5. Why does the merchant see Stripe Ready while the partner sees Unavailable?
The merchant must also enable Stripe in Methods available to partners. Both pages must use the same store and live Stripe environment. After enabling it, refresh provider status and reload the partner page.
6. Does Affilyn collect a partner's bank account details?
No. Stripe collects identity and bank information on Stripe-hosted onboarding pages. Affilyn stores only safe operational data such as an encrypted provider account ID, masked destination, country, supported currency, verification state, and outstanding requirements.
7. Can a partner connect Stripe to every merchant automatically?
No. The Stripe destination is created under the selected merchant's Stripe platform and is store-specific. The partner must use the payout settings for the correct store.
8. What does Preferred destination mean?
It is the verified provider Affilyn uses for future automatic payouts for that store. A partner may connect more than one supported provider, but Affilyn never switches providers automatically when the preferred one is unavailable.
9. Can a partner replace or disconnect Stripe at any time?
Not while commissions are reserved or a payout is approved, queued, or processing. This lock protects the immutable destination snapshot attached to the active payout.
10. What is the difference between Pending, Available, and Reserved balance?
Pending commissions have not completed finalization or the holding period. Available commissions are finalized, past the holding period, and unreserved. Reserved commissions are locked to an active payout request so the same earnings cannot be paid twice.
11. Why is Request payout disabled?
Common causes include an unavailable merchant provider, incomplete partner onboarding, unsupported currency, balance below the threshold, a holding period that has not finished, requests disabled by store policy, or another payout already in progress.
12. What happens after a partner requests payout?
Affilyn calculates the eligible amount on the server, reserves the exact commission rows, records the selected Stripe destination, and creates a request. If merchant approval is required, it waits in the merchant's Request Queue.
13. Does merchant approval mean the partner has been paid?
No. Approval authorizes Affilyn to begin secure Stripe processing. The payout is not paid until Stripe's final outcome is verified and the status changes to Paid.
14. How does Pay now differ from a partner request?
Pay now is initiated and confirmed by the merchant using the partner's preferred verified destination. A partner request starts from the Partner Portal and may wait for merchant approval. Both flows reserve eligible commissions and use the merchant-owned Stripe account.
15. How do weekly and monthly automatic payouts work?
Weekly payouts run each Monday at 00:00 UTC and monthly payouts run on the first day of the month at 00:00 UTC. Affilyn checks holding period, currency, threshold, optional cap, provider readiness, destination readiness, balance, and active-payout state before creating a payout.
16. Will Affilyn use another provider if Stripe is unavailable?
No. Affilyn skips the payout and alerts the merchant. It never changes provider or funding source automatically, because an unexpected fallback could send money to the wrong destination.
17. What does Processing mean?
Processing means Stripe accepted the transfer instruction. It is not proof that the payout is complete. Affilyn waits for a verified provider outcome before changing the payout to Paid, Failed, or Reversed.
18. What should we do if a payout stays Processing?
Do not create another payout. Review the provider reference and operational alert in Payouts. Affilyn checks unresolved payouts automatically; contact Affilyn support if the status remains unchanged unusually long.
19. What happens when the merchant's Stripe available balance is insufficient?
The payout does not complete. Funds must first appear in the merchant's Available Stripe balance, not merely Pending. Keep the original request reserved and use Retry safely only after Affilyn confirms Stripe did not already create a successful transfer.
20. Can the same payout be submitted twice?
Affilyn transactionally reserves commission rows and uses stable idempotency references to prevent duplicates. Unknown outcomes stay reserved. Users should never create another request to work around an approved or processing payout.
21. When are payout emails sent?
Notifications cover earnings becoming available, request submission, merchant approval, processing, and final paid, failed, or reversed outcomes. A replay of an already-finalized event does not send a duplicate completion email.
22. Where can merchants and partners see completed Stripe payouts?
Merchants use Payouts and Payout History. Partners use Payout History for the selected store. History includes the amount, provider, status, timestamps, masked destination snapshot, and provider reference without exposing sensitive account details.
Limitations
- This FAQ covers Stripe payouts only, not PayPal or off-platform manual payments.
- Internal endpoints, operational scripts, and secrets are intentionally excluded.