Enter only the fields the provider requires
Account type, merchant email, client ID, write-only client secret and Live/Sandbox mode.
- Selected business profile
- Explicit live or test mode
- Write-only secret editing
Payment integration
Accept supported-currency invoice payments through PayPal Orders in Invoice Crowd, with provider capture and amount/currency verification before settlement.
Last updated:
Configuration to settlement
Connection, customer checkout and final settlement are separate stages. Read the status and limitations before showing the method on a live invoice.
Credentials and mode stay tied to the selected business.
Account type, merchant email, client ID, write-only client secret and Live/Sandbox mode.
PayPal controls merchant availability, supported currencies, fees and account eligibility.
Availability is evaluated before a customer enters checkout.
PayPal Orders is available only when the invoice currency is in the server-owned supported list. The completed capture is fetched and verified.
Existing legacy Billing Agreement renewals and lifecycle handling remain active when the exact provider bindings exist.
The final local state follows provider evidence, not the browser.
Completed capture or sale, bound invoice, exact amount and currency, merchant account/mode and stable payment identity.
The email-only PayPal Standard browser return is not payment proof and stays manual-review only.
Integration facts
The fields below describe the current Invoice Crowd path; the provider remains the source for merchant eligibility, fees and regional availability.
Active with currency checks
PayPal Orders is available only when the invoice currency is in the server-owned supported list. The completed capture is fetched and verified.
Existing legacy Billing Agreement renewals and lifecycle handling remain active when the exact provider bindings exist.
Account type, merchant email, client ID, write-only client secret and Live/Sandbox mode.
Completed capture or sale, bound invoice, exact amount and currency, merchant account/mode and stable payment identity.
PayPal controls merchant availability, supported currencies, fees and account eligibility.
The email-only PayPal Standard browser return is not payment proof and stays manual-review only.
Amount, currency and allocation are derived from the current server-side invoice state.
A provider screen or browser return is a locator, not sufficient settlement proof.
Durable attempts and stable provider identities prevent an uncertain response from becoming an unbounded duplicate payment.
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
Current status: Active with currency checks. PayPal Orders is available only when the invoice currency is in the server-owned supported list. The completed capture is fetched and verified.
Account type, merchant email, client ID, write-only client secret and Live/Sandbox mode. PayPal controls merchant availability, supported currencies, fees and account eligibility.
PayPal Orders is available only when the invoice currency is in the server-owned supported list. The completed capture is fetched and verified.
Existing legacy Billing Agreement renewals and lifecycle handling remain active when the exact provider bindings exist.
Completed capture or sale, bound invoice, exact amount and currency, merchant account/mode and stable payment identity. A browser return or posted status alone cannot settle the invoice.
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.
Start with sandbox or test mode where the provider offers it, verify the exact currency and payment result, then plan production activation.