Skip to content

Payment integration

Connect Stripe without treating checkout as proof

Connect a Stripe account to Invoice Crowd for verified hosted invoice checkout and durable subscription payment flows, subject to account and currency support.

  • Status: Active
  • Verified against application docs
  • Provider terms still apply

Last updated:

Invoice Crowd Stripe integration dashboard showing hosted checkout, amount and currency verification, and payment settlement evidence.

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.

Invoice Crowd Stripe connect stripe illustration with fabricated sample data.

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

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.

Invoice Crowd Stripe customer checkout illustration with fabricated sample data.

Use the supported one-time flow

Hosted Checkout is active. Invoice Crowd creates a durable attempt before Stripe, then verifies the returned Checkout Session or PaymentIntent before settlement.

  • 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
  • Retired creators stay unavailable

Verify before recording money

The final local state follows provider evidence, not the browser.

Invoice Crowd Stripe verify and record illustration with fabricated sample data.

Match the commercial record exactly

Paid or complete provider state, merchant account and mode, invoice allocation, amount, currency and stable Stripe identity.

  • Merchant account and mode
  • Allocation, amount and currency
  • Successful provider state

Keep the current limitation visible

The older public Stripe ACH setup and payment routes are retired. Use the supported GoCardless direct-debit path where appropriate.

  • 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. Invoice Crowd creates a durable attempt before Stripe, then verifies the returned Checkout Session or PaymentIntent before settlement.

  • 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

    Paid or complete provider state, merchant account and mode, invoice allocation, amount, currency and stable Stripe identity.

  • Regional fit

    Availability, settlement countries, currencies, fees and account review are controlled by Stripe.

  • Current boundary

    The older public Stripe ACH setup and payment routes are retired. Use the supported GoCardless direct-debit path where appropriate.

  • 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. Hosted Checkout is active. Invoice Crowd creates a durable attempt before Stripe, then verifies the returned Checkout Session or PaymentIntent before settlement.

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?

Hosted Checkout is active. Invoice Crowd creates a durable attempt before Stripe, then verifies the returned Checkout Session or PaymentIntent before settlement.

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?

Paid or complete provider state, merchant account and mode, invoice allocation, amount, currency and stable Stripe identity. A browser return or posted status alone cannot settle the invoice.

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