Skip to content

Payment integration

Connect PayTabs without treating checkout as proof

Use PayTabs hosted one-time invoice checkout in Invoice Crowd with raw callback HMAC and authenticated payment-query verification.

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

Last updated:

Invoice Crowd PayTabs integration dashboard showing hosted checkout, callback HMAC and authenticated payment query.

Configuration to settlement

How PayTabs 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 PayTabs connect paytabs illustration with fabricated sample data.

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

Confirm provider eligibility before rollout

PayTabs controls eligible merchant regions, endpoint availability, currencies and fees.

  • 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 PayTabs customer checkout illustration with fabricated sample data.

Use the supported one-time flow

The hosted flow writes an immutable attempt, restricts regional endpoints, verifies the raw callback HMAC and queries PayTabs before accepting authorized status.

  • Server-owned amount
  • Bound invoice allocation
  • Provider-controlled payment step

Read the recurring-payment boundary separately

Automatic PayTabs subscription setup and callback mutation are retired.

  • 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 PayTabs verify and record illustration with fabricated sample data.

Match the commercial record exactly

Callback HMAC, authenticated payment query, exact profile/account, allocation, amount, currency and authorized state.

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

Keep the current limitation visible

Only the verified hosted one-time flow is active. A posted status or automatic subscription callback cannot settle an invoice.

  • No inferred settlement
  • Pending stays pending
  • Mismatch fails closed

Integration facts

What to verify before using PayTabs

The fields below describe the current Invoice Crowd path; the provider remains the source for merchant eligibility, fees and regional availability.

  • Availability

    Active hosted checkout

  • One-time payment

    The hosted flow writes an immutable attempt, restricts regional endpoints, verifies the raw callback HMAC and queries PayTabs before accepting authorized status.

  • Recurring payments

    Automatic PayTabs subscription setup and callback mutation are retired.

  • Merchant setup

    Profile ID, write-only server key, optional client key, allow-listed regional API endpoint and Live/Test mode.

  • Settlement evidence

    Callback HMAC, authenticated payment query, exact profile/account, allocation, amount, currency and authorized state.

  • Regional fit

    PayTabs controls eligible merchant regions, endpoint availability, currencies and fees.

  • Current boundary

    Only the verified hosted one-time flow is active. A posted status or automatic subscription callback cannot settle an invoice.

  • 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

PayTabs and Invoice Crowd, answered

Is the PayTabs integration currently available in Invoice Crowd?

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.

What do I need to connect PayTabs?

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.

How does PayTabs one-time checkout work?

The hosted flow writes an immutable attempt, restricts regional endpoints, verifies the raw callback HMAC and queries PayTabs before accepting authorized status.

Does PayTabs support recurring payments in Invoice Crowd?

Automatic PayTabs subscription setup and callback mutation are retired.

How does Invoice Crowd decide that a payment succeeded?

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.

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 PayTabs 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