Enter only the fields the provider requires
Profile ID, write-only server key, optional client key, allow-listed regional API endpoint and Live/Test mode.
- Selected business profile
- Explicit live or test mode
- Write-only secret editing
Payment integration
Use PayTabs hosted one-time invoice checkout in Invoice Crowd with raw callback HMAC and authenticated payment-query verification.
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.
Profile ID, write-only server key, optional client key, allow-listed regional API endpoint and Live/Test mode.
PayTabs controls eligible merchant regions, endpoint availability, currencies and fees.
Availability is evaluated before a customer enters checkout.
The hosted flow writes an immutable attempt, restricts regional endpoints, verifies the raw callback HMAC and queries PayTabs before accepting authorized status.
Automatic PayTabs subscription setup and callback mutation are retired.
The final local state follows provider evidence, not the browser.
Callback HMAC, authenticated payment query, exact profile/account, allocation, amount, currency and authorized state.
Only the verified hosted one-time flow is active. A posted status or automatic subscription callback cannot settle an invoice.
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
The hosted flow writes an immutable attempt, restricts regional endpoints, verifies the raw callback HMAC and queries PayTabs before accepting authorized status.
Automatic PayTabs subscription setup and callback mutation are retired.
Profile ID, write-only server key, optional client key, allow-listed regional API endpoint and Live/Test mode.
Callback HMAC, authenticated payment query, exact profile/account, allocation, amount, currency and authorized state.
PayTabs controls eligible merchant regions, endpoint availability, currencies and fees.
Only the verified hosted one-time flow is active. A posted status or automatic subscription callback cannot settle an invoice.
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 hosted checkout. The hosted flow writes an immutable attempt, restricts regional endpoints, verifies the raw callback HMAC and queries PayTabs before accepting authorized status.
Profile ID, write-only server key, optional client key, allow-listed regional API endpoint and Live/Test mode. PayTabs controls eligible merchant regions, endpoint availability, currencies and fees.
The hosted flow writes an immutable attempt, restricts regional endpoints, verifies the raw callback HMAC and queries PayTabs before accepting authorized status.
Automatic PayTabs subscription setup and callback mutation are retired.
Callback HMAC, authenticated payment query, exact profile/account, allocation, amount, currency and authorized state. 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.