Choose by customer path
Hosted checkout, mobile money, direct debit and request links solve different collection jobs.
- Hosted checkout and wallets
- Provider-specific constraints
- Fallback gateway planning
Integration directory
Payment integrations, with current availability and limits visible
Invoice Crowd connects active provider paths to the same invoice record, but merchant region, currency, customer experience and settlement proof differ. Use the directory to choose the right collection model before entering credentials.
- 15 provider and payment guides
- Status checked August 7, 2026
- Unavailable methods clearly identified
Last updated:
Choose deliberately
Start with the collection model, then the logo
A familiar provider matters, but the real decision is whether the merchant, customer, currency and evidence contract fit the invoice.
Choose by customer path
Cards, wallets, bank debit and provider payment requests.
Map the payer experience
Consider what the customer recognizes and where the provider hosts or embeds the step.
- Document the decision
- Test representative data
- Review before launch
Choose by merchant region
Gateway coverage follows the provider account, country and currency.
Choose by merchant region
Regional options such as M-Pesa, PayFast, Razorpay, PayTabs and Telr sit beside broader multi-market providers.
- Country, currency and account
- Provider-specific constraints
- Fallback gateway planning
Confirm merchant eligibility
Check the provider country list, account mode, settlement currency and required production approval.
- Document the decision
- Test representative data
- Review before launch
Choose by settlement evidence
A successful-looking return page is never enough.
Choose by settlement evidence
Invoice Crowd verifies signatures and/or provider state, then matches the account, allocation, amount, currency and stable payment identity.
- Exact provider evidence
- Provider-specific constraints
- Fallback gateway planning
Keep pending and failed distinct
Only an authenticated successful result changes the invoice; uncertainty remains visible and retry-safe.
- Document the decision
- Test representative data
- Review before launch
Provider directory
Every documented payment path in one place
An Active label describes the current Invoice Crowd path, not universal provider availability. Open a guide for setup, verification, recurring support and limitations.
-
Stripe
Status: Active. Availability, settlement countries, currencies, fees and account review are controlled by Stripe.
-
PayPal
Status: Active with currency checks. PayPal controls merchant availability, supported currencies, fees and account eligibility.
-
Razorpay
Status: Active. Razorpay controls merchant onboarding, supported countries/currencies, fees and International Payments eligibility.
-
M-Pesa
Status: Active one-time checkout. Designed for eligible M-Pesa merchants and KES transactions; Safaricom controls account access, fees and production approval.
-
PayFast
Status: Active for ZAR. Focused on eligible South African merchants and ZAR; PayFast controls onboarding, fees and account features.
-
GoCardless
Status: Active direct debit. Scheme, country, currency, collection timing and merchant availability are controlled by GoCardless.
-
ACH & Direct Debit
Status: Stripe-hosted ACH for eligible one-time USD invoices plus active GoCardless direct debit. Provider eligibility, fees, timing and regional availability still apply.
-
Square
Status: Active one-time checkout. Square controls merchant countries, location availability, currencies, fees and account review.
-
Authorize.Net
Status: Active tokenized capture. Authorize.Net controls merchant eligibility, supported currencies, fees and settlement services.
-
Braintree
Status: Active. Braintree controls merchant countries, currencies, account features, plans and fees.
-
Payoneer
Status: Active payment requests. Payoneer controls program, payee, account, currency, fee and geographic availability.
-
PhonePe
Status: Not currently available. PhonePe and merchant availability are provider-controlled; Invoice Crowd must still complete the current v2 integration contract.
-
PayTabs
Status: Active hosted checkout. PayTabs controls eligible merchant regions, endpoint availability, currencies and fees.
-
Telr
Status: Active one-time checkout. Telr controls merchant markets, currencies, account services and fees.
-
Airwallex
Status: Active hosted checkout. Airwallex controls merchant onboarding, supported markets/currencies, account features and fees.
Questions
Payment integrations, answered
Which payment gateways does Invoice Crowd support?
Current documented paths include Stripe, PayPal, Razorpay, M-Pesa, PayFast, GoCardless, Square, Authorize.Net, Braintree, Payoneer, PayTabs, Telr and Airwallex, plus a direct-debit guide. PhonePe has a noindex status page because it is not currently available.
Does every gateway support recurring payments?
No. One-time and recurring capability differs by provider. Some providers support existing renewal bindings without creating new subscriptions, while other gateways support one-time payments only.
Can a customer pay in any currency?
No. The invoice currency, merchant account, provider product and region must all support the transaction. Invoice Crowd applies provider-specific checks where implemented and the provider remains the final eligibility source.
Does returning from a gateway mark an invoice paid?
No. Active paths require a signature and/or authenticated provider read plus exact account, allocation, amount, currency and successful-state checks before local settlement.
Are gateway fees included in an Invoice Crowd plan?
No. Payment-processing, exchange, settlement and account fees come from the gateway and merchant agreement and are separate from the Invoice Crowd subscription.
Why is PhonePe listed if it is not active?
The page prevents a stale credential screen or old route from being mistaken for a supported integration. PhonePe checkout is not currently available, so the status page is noindexed and points to active alternatives.
Test the provider against a real invoice scenario
Use test or sandbox mode where available, include the currency and collection method you actually need, and confirm the provider result before broader rollout.
- Current availability disclosed
- Provider terms apply
- No inferred payment success