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
The Stripe integration lets customers pay your Invoice Crowd invoices by card through Stripe Checkout, and by US bank account on eligible one-time USD invoices. Subscriptions are supported, and refunds go back through Stripe from inside Invoice Crowd.
From setup to paid
Connection, customer checkout and final settlement are separate stages. Read the status and limitations before showing the method on a live invoice.
Each business profile has its own account and live or test mode.
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.
The payment option only shows when it can be used for that invoice.
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.
Subscription creation and signed renewal settlement are active through attempt-bound metadata and provider rechecks.
An invoice is marked paid only when the provider confirms it.
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.
The supported Stripe ACH path uses the same hosted Checkout flow as card payments. Stripe handles bank selection, verification and mandate acceptance.
Integration facts
The fields below describe the current Invoice Crowd path; the provider remains the source for merchant eligibility, fees and regional availability.
Active
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.
Subscription creation and signed renewal settlement are active through attempt-bound metadata and provider rechecks.
Publishable key, write-only secret key and Live/Test mode for the selected business.
A signed payment_intent.succeeded event must match the merchant account and mode, invoice allocation, amount, currency and immutable attempt before settlement.
Availability, settlement countries, currencies, fees and account review are controlled by Stripe.
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.
Amount, currency and allocation are derived from the current server-side invoice state.
If a confirmed Stripe payment can't be applied to its invoice, for example because the balance changed after checkout started, Invoice Crowd holds it in Payments Needing Review. You then apply it to the invoice, keep it as customer credit, or refund it.
Choose Refund on the invoice in Invoice Crowd and the money goes back to the customer through Stripe. The refund is booked only after Stripe confirms it. This covers online payments made on the invoice page.
Gateway fees, exchange costs and settlement timing come from the merchant agreement, not the Invoice Crowd subscription.
Configure another active provider when this gateway does not support the merchant, customer, currency or collection model.
Questions
Yes. Stripe is active in Invoice Crowd. Hosted Checkout takes card payments and, for eligible one-time USD invoices with Allow US bank payment enabled, Stripe-hosted ACH bank payment.
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. Stripe needs a paid Invoice Crowd plan; the free plan includes PayPal.
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.
Subscription creation and signed renewal settlement are active through attempt-bound metadata and provider rechecks.
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. A confirmed payment that can't be applied to its invoice is held in Payments Needing Review until you decide what to do with it.
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.
Yes. Choose Refund on the invoice (from the invoice list, the editor or Manage Payments), then pick "Refund it to the customer via Stripe". Invoice Crowd sends the refund through Stripe and books it only after Stripe confirms it. This works for online payments made on the invoice page, not for recurring, subscription or payment-link invoices.
Start with sandbox or test mode where the provider offers it, verify the exact currency and payment result, then plan production activation.