Enter only the fields the provider requires
Publishable key, write-only secret key and Live/Test mode for the selected business.
- Selected business profile
- Explicit live or test mode
- Write-only secret editing
Payment integration
Accept invoice payments with Stripe
Accept eligible card payments, US bank payments on one-time USD invoices, and supported subscription payments through Stripe.
- Status: Card and eligible ACH active
- Verified against application docs
- Provider terms still apply
Last updated:
Configuration to settlement
How Stripe fits the Invoice Crowd payment boundary
Connection, customer checkout and final settlement are separate stages. Read the status and limitations before showing the method on a live invoice.
Connect the merchant account
Credentials and mode stay tied to the selected business.
Confirm provider eligibility before rollout
Availability, settlement countries, currencies, fees and account review are controlled by Stripe.
- Merchant country and account
- Invoice and settlement currency
- Provider fees and review
Understand the customer path
Availability is evaluated before a customer enters checkout.
Use the supported one-time flow
Hosted Checkout is active. A one-time USD invoice with Allow US bank payment enabled explicitly offers card plus us_bank_account; other invoices are card-only. Stripe hosts bank selection, mandate acceptance and verification.
- Server-owned amount
- Bound invoice allocation
- Provider-controlled payment step
Read the recurring-payment boundary separately
Subscription creation and signed renewal settlement are active through attempt-bound metadata and provider rechecks.
- One-time and recurring differ
- Existing bindings may be compatibility-only
- Unavailable creation paths stay unavailable
Verify before recording money
The final local state follows provider evidence, not the browser.
Match the commercial record exactly
Only a signed, account-scoped payment_intent.succeeded event with the exact merchant, invoice allocation, amount, currency and stable Stripe identity can settle a one-time payment.
- Merchant account and mode
- Allocation, amount and currency
- Successful provider state
Keep the current limitation visible
The supported Stripe ACH path uses the same hosted Checkout flow as card payments. Stripe handles bank selection, verification and mandate acceptance.
- No inferred settlement
- Pending stays pending
- Mismatch fails closed
Integration facts
What to verify before using Stripe
The fields below describe the current Invoice Crowd path; the provider remains the source for merchant eligibility, fees and regional availability.
-
Availability
Active
-
One-time payment
Hosted Checkout is active for cards. Eligible one-time USD invoices with Allow US bank payment enabled explicitly add us_bank_account in the same Checkout Session.
-
Recurring payments
Subscription creation and signed renewal settlement are active through attempt-bound metadata and provider rechecks.
-
Merchant setup
Publishable key, write-only secret key and Live/Test mode for the selected business.
-
Settlement evidence
A signed payment_intent.succeeded event must match the merchant account and mode, invoice allocation, amount, currency and immutable attempt before settlement.
-
Regional fit
Availability, settlement countries, currencies, fees and account review are controlled by Stripe.
-
Current boundary
Stripe ACH is active through hosted Checkout for eligible one-time USD invoices. Invoice Crowd settles only after the signed, account-scoped Stripe success webhook matches the exact attempt.
-
Invoice data
Amount, currency and allocation are derived from the current server-side invoice state.
-
Customer result
A provider screen or browser return is a locator, not sufficient settlement proof.
-
Retries
Durable attempts and stable provider identities prevent an uncertain response from becoming an unbounded duplicate payment.
-
Provider fees
Gateway fees, exchange costs and settlement timing come from the merchant agreement, not the Invoice Crowd subscription.
-
Alternative gateways
Configure another active provider when this gateway does not support the merchant, customer, currency or collection model.
Questions
Stripe and Invoice Crowd, answered
Is the Stripe integration currently available in Invoice Crowd?
Current status: Active. Stripe hosted Checkout supports card payments and, for eligible one-time USD invoices with Allow US bank payment enabled, Stripe-hosted ACH bank payment.
What do I need to connect Stripe?
Publishable key, write-only secret key and Live/Test mode for the selected business. Availability, settlement countries, currencies, fees and account review are controlled by Stripe.
How does Stripe one-time checkout work?
Invoice Crowd creates an immutable attempt before Stripe. Eligible one-time USD invoices can offer card and US bank payment in hosted Checkout; other invoices are card-only. A browser return stays processing until Stripe's signed success event confirms payment.
Does Stripe support recurring payments in Invoice Crowd?
Subscription creation and signed renewal settlement are active through attempt-bound metadata and provider rechecks.
How does Invoice Crowd decide that a payment succeeded?
A browser return or posted status cannot settle the invoice. One-time payment requires a signed, account-scoped payment_intent.succeeded event matching the exact merchant, invoice allocation, amount, currency and immutable attempt.
Are gateway fees included in Invoice Crowd pricing?
No. Provider transaction fees, foreign-exchange costs, settlement timing and account terms are controlled by the gateway and merchant agreement. Check the provider before activation.
Test Stripe with a representative invoice
Start with sandbox or test mode where the provider offers it, verify the exact currency and payment result, then plan production activation.
- No browser-only settlement
- Provider terms apply
- Current status is visible