Substack — India Payout Setup (All Scenarios)

✓

Account

2

Identity

3

Waiting

4

Review

Set up payouts

Select your country to see the payout setup requirements.

Country *

Personal identity

First name *

Last name *

Date of birth *

Required for identity verification

Tax ID *

Mobile number *

Residential address

Address line 1 *

City *

State *

Postal code *

Business details

Business type *

Publication URL *

Confirms your publishing activity

Payout details

Declaration

I declare that the information provided is true and complete. I confirm I am a resident of the stated country for tax purposes, the identity document belongs to me, and the payout account is held in my name. I authorise Substack to share my information with the relevant payment processor for account verification and payout processing.

I have read and agree to the declaration above

Annotations

8 countriesForm targets India, Indonesia, and 6 LatAm markets (BR, MX, CO, AR, CL, PE). Fields are driven by a JS country config — tax ID type, phone prefix, routing identifier (IFSC / BI bank code / PIX / CLABE / CBU / CCI), payout rail (Stripe direct vs local PA), and optional local tax registration all vary by country.

Local PAFor all non-India countries, Stripe is not available as a direct payout rail. A notice explains the licensed local PA (Xendit/Midtrans for ID, BACEN PI for BR, CNBV SPEI for MX, SFC for CO, BCRA for AR, CMF for CL, SBS for PE). Creator experience is identical — routing is invisible.

IN onlyRBI purpose codes (P1101–P0801) and IFSC validation only appear for India. Other countries use their own regulatory frameworks and do not require RBI P-codes.

#101PAN/IFSC client-side validation active for India. Other countries show format hints only — full validation requires server-side integration with each country's identity verification service.

✓

Account

2

Identity

3

Waiting

4

Review

Verify your identity

Please correct the highlighted fields.

Personal identity

First name *

Last name *

⚠ PAN 5th char 'X' doesn't match surname initial 'R'. Enter name exactly as on PAN card.

Date of birth *

⚠ Date of birth indicates age under 18. Stripe requires the account holder to be at least 18 years old.

PAN number *

⚠ PAN entity type 'C' (5th character) is not accepted — only individual (P) PANs are valid. Company and HUF PANs cannot be used.

Mobile number *

+91

Residential address

Address line 1 *

City *

State *

PIN code *

⚠ PIN code must be 6 digits. "12345" is only 5 digits.

Business details

Business type *

⚠ Business type is required by Stripe.

Publication URL *

⚠ Please enter your specific publication URL, not substack.com. Example: yourname.substack.com

Remittance purpose

Business intent *

⚠ Please select a business intent to continue.

Bank account

Account number *

⚠ Account number must be 9–18 digits. "1234" is only 4 digits.

IFSC code *

⚠ Invalid format. Expected: AAAA0AAAAAA (4 letters · zero · 6 alphanumeric). Example: HDFC0001234

Account type *

₹1 test deposit — We'll send a ₹1 test deposit once all errors are fixed.

Declaration

I declare the information is true and complete. I confirm I am a resident individual in India for tax purposes, the PAN belongs to me, the bank account is in my name, and the inward remittances comply with FEMA and RBI guidelines. I authorise Substack to share my information with Stripe Payments India Pvt Ltd.

I have read and agree to the declaration above

Annotations

#101All errors accumulate — no fail-fast. Error banner counts total so the user sees scope upfront. Each error message names the exact field, value received, and what was expected.

#101PAN entity type check (5th char must be 'P') and surname-initial check are client-side mirrors of server validation. Both give specific character-position feedback, not just "invalid PAN".

Stripebusiness_type and business_profile.url are Stripe-required fields — blank values cause missing_required_field errors on account creation. URL must be a specific publication URL, not the platform root.

StripeDOB age check (must be ≥18) is validated client-side and server-side. Stripe rejects accounts where the individual is under 18.

✓

Account

✓

Identity

3

Waiting

4

Review

✅ Identity submitted · KYC-2026-05-24-NPQ

Here's where you stand

Every creator sees this screen after submitting. Your current platform metrics are compared against the endorsement thresholds. All green means you qualify for a Substack-endorsed fast-track application.

Platform Endorsement ⚠ 3 criteria not yet met

Once all criteria turn green, Substack will attach a signed endorsement to your Stripe India application — targeting a 48-hour invite SLA instead of the standard 2–6 month wait. Keep publishing to close the gaps below.

Your endorsement criteria

Account age	180 days	185 days to go
Threshold: 365 days — 185 days remaining
Free subscribers	320 / 500	180 away
Threshold: 500 subscribers
Avg. open rate	38.5%	✓ Met
Publications	8 / 12	4 posts away
Threshold: 12 published posts
Chargebacks	0	✓ Met

What you can do now

→Keep publishing — 185 more days of account history gets you to the age threshold.

→Grow to 500 free subscribers (180 away). Share your pledge link so readers know payouts are coming.

→Publish 4 more posts to clear the minimum publication count (8 → 12).

→Start your pledge wall — reader pledges accumulate now and are captured the moment your account is approved.

Pledge wall fast-track: If 12 or more readers express interest before you formally qualify, we'll flag your application for expedited manual review — even without a full endorsement.

Without endorsement: You can still submit to Stripe India's invite queue, but the typical wait is 2–6 months (or indefinitely — there is no public SLA). The endorsement is what Substack is working to change.

Reader pledge wall

👛

0

readers interested

Pledges accumulate now, regardless of where you stand on endorsement criteria. They're captured the moment your account is approved.

Annotations

UXThis screen is the universal post-submit landing — not a failure state. Creators who fully qualify see all criteria green. Creators with gaps see the specific shortfalls and what to do. Framing is neutral/informational throughout.

#302Milestone trigger (reader count threshold) acts as an alternate fast-track signal regardless of endorsement status. Pledge accumulation is never paused.

#101Eligibility panel shows exact shortfall counts (180 subscribers, 185 days, 4 posts) and progress bars — not a generic "not qualified" message. Each gap has an actionable suggestion.

✓

Account

✓

Identity

3

Waiting

4

Review

✅ Identity submitted · KYC-2026-05-24-PRK

Platform Endorsement ✓ Qualified

Account age	412 days	✓
Free subscribers	1,240	✓
Avg. open rate	38.5%	✓
Publications	47	✓
Chargebacks	0	✓

Substack will submit a signed endorsement once your bank account is verified. Stripe fast-track target: 48 hours.

₹1 test deposit in progress

Sending ₹1 IMPS credit to your HDFC account ending in …8901 (IFSC: HDFC0001234). Typically arrives within 2–6 hours. Check your SMS alerts.

Note: The platform endorsement is sent to Stripe only after your bank account is confirmed via penny-drop — not immediately on form submission.

Live pledge wall

👛

0

readers interested

Milestone progress 0 of 12 readers

Annotations

#301Reader interest ledger — intent signals, not payments. The ledger persists through all waiting states and survives bank verify delays.

#302Milestone trigger: when reader interest count reaches 12 the UI transitions to 2c and a cron job elevates the Stripe application to expedited queue.

#103Endorsement fires only after penny-drop confirmed (step 3b), not on KYC form submission. This panel reflects the pending state.

✓

Account

✓

Identity

3

Waiting

4

Review

✅ Identity submitted · KYC-2026-05-24-PRK

Platform Endorsement ✓ Expedited — milestone triggered

Your pledge total has triggered expedited review. Our team will manually fast-track your Stripe application regardless of normal endorsement timing.

₹1 test deposit still in progress

Sending ₹1 to your HDFC account ending in …8901. Bank confirmation pending — your milestone status is noted regardless.

Pledge wall — milestone reached!

👛

18

readers interested

Milestone progress 18 of 12 readers — ACHIEVED 🎉

A

Arjun Mehtainterestednow

S

Sneha Krishnaninterested1m ago

R

Rahul Vermainterested3m ago

P

Pallavi Nairinterested5m ago

Annotations

#302Cron-triggered milestone elevation: when reader interest count reaches 12, a background job elevates the Stripe application priority and updates the endorsement status chip to "Expedited".

#301Reader interest count is used as a demand signal in Stripe application triage — not a revenue figure. No amounts are shown anywhere on the pledge wall. No reader has been charged at this stage.

✓

Account

✓

Identity

3

Waiting

4

Review

We sent ₹1 to your HDFC account ending in …8901 (HDFC0001234) 48 hours ago. If you haven't seen it, something may have gone wrong with the transfer.

Choose what to do next

✓ I did receive it — confirm now

If the ₹1 appeared in your account, click here to confirm and proceed to Stripe review.

✎ Re-enter bank details

If you entered the wrong account number or IFSC, go back and correct them. We'll send a new ₹1 test deposit.

✗ My bank rejected it

Some banks reject IMPS credits. Click to learn more and get alternatives.

Still stuck? Contact India support →

Pledge wall — still accumulating

👛

0

readers interested

The bank verification timeout does not affect your pledge ledger. Pledges continue accumulating.

Annotations

#101Penny-drop is the only reliable mechanism to confirm bank account ownership for FEMA compliance — it cannot be skipped or substituted with a voided cheque upload alone.

R6Risk: penny-drop delays are the most common failure point. Three distinct recovery paths are provided: confirm receipt, re-enter details, or escalate bank rejection — not just a single "contact support" dead-end.

#301Pledge wall continues accumulating through all failure states. The timeout does not pause or reset the pledge ledger.

✓

Account

✓

Identity

3

Waiting

4

Review

✅

Bank account verified

Your HDFC account ending in …8901 is confirmed. We're now packaging your platform endorsement and submitting it to Stripe.

✓

Identity verified

✓

Bank account confirmed (HDFC …8901)

⟳

Submitting endorsement bundle to Stripe…

This usually takes less than a minute. You'll get an email when Stripe confirms receipt.

Your pledges are safe

Readers who expressed interest will be the first to know when you go live. Pledges are a signal of intent — no one has been charged. Pledges continue accumulating.

18

readers pledged

18

readers interested

Annotations

#103Endorsement bundle submission triggers here — on penny-drop confirmation — not on KYC form submit. The bundle includes: PAN details, platform eligibility scores, pledge ledger snapshot, and Substack's signed endorsement.

✓

Account

✓

Identity

✓

Waiting

4

Invite

Waiting for Stripe India invite

Stripe India operates on an invite-only model due to RBI regulatory requirements. Your application is in the queue — here's exactly where it stands.

Why invite-only? The Reserve Bank of India requires Stripe India to verify and approve each merchant individually before they can receive international inward remittances. Stripe cannot open accounts to all applicants simultaneously — invitations are issued in batches as RBI compliance slots become available.

Your queue position ⏳ In invite queue

Application submitted	24 May 2026, 10:06 AM IST
Platform endorsement	✓ Attached
Queue stage	Compliance pre-screening
Estimated invite	Targeting 48 hrs (see note)

Note — this is a proposed improvement, not yet live. Without Substack's endorsement, the typical Stripe India invite wait is 2–6 months — or indefinitely, as there is no public SLA. The 48-hour target is what Substack's India team is actively negotiating with Stripe BD as a committed SLA for endorsed creators. This screen reflects what the proposal would look like once in place.

✓

Identity & bank verified

24 May 2026, 10:05 AM IST

✓

Platform endorsement submitted to Stripe India

24 May 2026, 10:06 AM IST · includes PAN, eligibility scores, pledge ledger snapshot

✓

Application received by Stripe India compliance

24 May 2026, 10:07 AM IST

Stripe India invite issuance

Target: within 48 hours (endorsed) · Without endorsement: 2–6 months, no guarantee

○

Account activation & first payout

After invite accepted and final KYC cleared

What you can do while waiting

→Share your pledge link — reader pledges accumulate now and are captured the moment your account goes live. Every pledge signals demand to Stripe.

→Keep publishing. A higher open rate and subscriber count strengthens your file if Stripe requests additional review.

→Watch your email — Stripe may request additional documents (passport, Aadhaar, address proof). Respond within 48 hours to avoid losing your queue position.

→You will not be charged anything during this process.

What Substack is doing: Substack's India team is in active discussions with Stripe BD to commit the 48-hour invite SLA for endorsed creators. This is not yet a live arrangement — it is the outcome this proposal is designed to secure. Updates will appear here as the commercial agreement progresses.

From: noreply@stripe.com · This is what the invite email will look like

Your Stripe India account is ready to activate

Dear Priya,

You've been invited to activate your Stripe India payout account. This invitation was issued on the basis of Substack's platform endorsement.

To complete activation, please:
• Confirm your PAN and legal name match your records
• Upload one government-issued ID (passport or Aadhaar)
• Confirm your bank account (HDFC …8901) for payouts

Your invitation expires in 7 days. Please complete the steps above to secure your account.

— Stripe Compliance Team, India

Pledge wall — accumulating while you wait

18

readers pledged

18

readers interested

Share your pledge link while you wait. Pledges are captured the moment your Stripe India invite is accepted and your account activates.

Annotations

R1Stripe India is invite-only due to RBI requirements — this is not a generic "in review" state. The distinction matters: there is no public queue SLA today. The 48-hour target is the outcome being negotiated, not a current guarantee.

#103Platform endorsement bundle submitted here includes: PAN, eligibility scores, pledge ledger snapshot, and Substack's signed letter. This is the lever Substack holds in the BD negotiation with Stripe.

R2Risk: the 48-hour SLA is not yet committed by Stripe. Without it, the endorsed path has the same indeterminate wait as unendorsed. Substack India team is the active party pursuing this commitment.

#301Pledge wall continues accumulating through all wait states. The invite queue delay does not pause or reset the pledge ledger.

✓

Account

✓

Identity

✓

Waiting

✗

Review

What this means

Stripe's compliance team couldn't match your submitted PAN to their third-party identity verification system. This is usually caused by a name spelling mismatch — for example, if your PAN card says "PRIYA RAGHUNATHAN" but you entered "Priya Raghunathan Sharma" — or a recently issued PAN that hasn't propagated to verification databases yet.

✓

Platform endorsement submitted

24 May 2026, 10:06 AM IST

✓

Received by Stripe India compliance

24 May 2026, 10:07 AM IST

✗

Identity verification failed

PAN-to-name match failed in Stripe's verification system

Your options

📋 Request a manual review

File a support ticket with additional documents: passport, Aadhaar (front + back), and a bank statement showing your PAN. Manual review takes 5–7 business days.

✎ Re-submit with corrected details

Go back to the form and correct your legal name to match exactly as printed on your PAN card — including spacing and spelling. Common fix for most rejections.

💬 Contact Substack support

Substack's India team can advocate with Stripe's BD team. Useful if you've re-submitted and are still rejected, or if your PAN was recently issued.

Your pledge wall is safe. Readers who expressed interest are still recorded and will be the first to know once your account is approved — whether through re-submission or manual review. Interest signals do not expire.

Pledge wall — still accumulating

18

readers pledged

18

readers interested

Rejection does not affect the pledge ledger. New pledges continue to be accepted.

Annotations

R3Risk: Stripe India may require raw PAN data submitted via their API rather than a PDF attestation. This screen represents the outcome when Stripe's third-party PAN lookup (NSDL/UTI) fails to match.

R2Risk: Name mismatch between PAN records and bank account records is the most common rejection cause for Indian creators. The error message identifies this specifically and offers a targeted fix (re-enter name exactly as on PAN card).

#301Pledge ledger persists through Stripe rejection. New reader pledges continue to be accepted and held. The ledger transitions to captured revenue only on approval.

✓

Account

✓

Identity

✓

Waiting

✓

Active

🏦

Your payout account is live

Your Stripe India account is approved and linked to HDFC (…8901). International subscriptions can now settle in India.

Account status

Active

Readers pledged

18

Purpose code

P1101

Collected so far

$0

Next steps to receive your first payout

✅Stripe India payout account approved

✅Bank account linked — HDFC (…8901)

1 Set your subscription price. No readers are being charged yet — payouts only happen after you publish paid pricing and readers actively subscribe.
Set pricing →

2 Reach out to your 18 pledge readers. They expressed interest but have not paid anything. They are your warmest leads — send an announcement the moment pricing is live.
Send announcement →

📄 After your first payout settles, your bank (HDFC) will issue a FIRC (Foreign Inward Remittance Certificate). This is issued by your bank, not Substack. Keep it for any GST LUT claims.

Pledge wall — reader interest recorded

These readers have not been charged. A pledge is an expression of intent, not a payment. Actual charges happen only after you set pricing and a reader subscribes.

18

readers pledged interest

$0

collected

$0

collected

Annotations

#301Reader interest ledger — intent signals only. No amounts shown anywhere on pledge wall. The count of interested readers is used as a demand signal; it is not a receivable and no reader has been charged.

Payout timingFirst payout date is unknown until the creator sets subscription pricing and at least one reader subscribes and pays. No estimated date is shown — showing one would be misleading at this stage.

FIRCGenerated by the creator's AD-I bank after inward remittance settles. Not generated by Substack or Stripe. Only relevant once subscription revenue flows.