Skip to content

Payment integration

Connect PayFast without treating checkout as proof

Connect PayFast to Invoice Crowd for signed ZAR invoice checkout and verified settlement, with recurring support when provider requirements are met.

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

Last updated:

Invoice Crowd PayFast integration dashboard showing signed checkout, ZAR amount and verified ITN settlement.

Configuration to settlement

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

Enter only the fields the provider requires

Merchant ID, merchant key, optional passphrase and Live/Sandbox mode.

  • Selected business profile
  • Explicit live or test mode
  • Write-only secret editing

Confirm provider eligibility before rollout

Focused on eligible South African merchants and ZAR; PayFast controls onboarding, fees and account features.

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

Use the supported one-time flow

Invoice Crowd generates the signed checkout form from server-owned amount data, then verifies the ITN signature, PayFast postback, merchant and exact ZAR amount.

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

Read the recurring-payment boundary separately

Recurring setup and lifecycle operations are active when the merchant passphrase and provider API requirements are satisfied.

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

Match the commercial record exactly

Exact form and ITN signature, PayFast VALID postback, unique payment ID, allocation and exact ZAR amount.

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

Keep the current limitation visible

PayFast is hidden for non-ZAR invoices. The browser return does not settle the invoice.

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

Integration facts

What to verify before using PayFast

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

  • Availability

    Active for ZAR

  • One-time payment

    Invoice Crowd generates the signed checkout form from server-owned amount data, then verifies the ITN signature, PayFast postback, merchant and exact ZAR amount.

  • Recurring payments

    Recurring setup and lifecycle operations are active when the merchant passphrase and provider API requirements are satisfied.

  • Merchant setup

    Merchant ID, merchant key, optional passphrase and Live/Sandbox mode.

  • Settlement evidence

    Exact form and ITN signature, PayFast VALID postback, unique payment ID, allocation and exact ZAR amount.

  • Regional fit

    Focused on eligible South African merchants and ZAR; PayFast controls onboarding, fees and account features.

  • Current boundary

    PayFast is hidden for non-ZAR invoices. The browser return does not settle the 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

PayFast and Invoice Crowd, answered

Is the PayFast integration currently available in Invoice Crowd?

Current status: Active for ZAR. Invoice Crowd generates the signed checkout form from server-owned amount data, then verifies the ITN signature, PayFast postback, merchant and exact ZAR amount.

What do I need to connect PayFast?

Merchant ID, merchant key, optional passphrase and Live/Sandbox mode. Focused on eligible South African merchants and ZAR; PayFast controls onboarding, fees and account features.

How does PayFast one-time checkout work?

Invoice Crowd generates the signed checkout form from server-owned amount data, then verifies the ITN signature, PayFast postback, merchant and exact ZAR amount.

Does PayFast support recurring payments in Invoice Crowd?

Recurring setup and lifecycle operations are active when the merchant passphrase and provider API requirements are satisfied.

How does Invoice Crowd decide that a payment succeeded?

Exact form and ITN signature, PayFast VALID postback, unique payment ID, allocation and exact ZAR amount. 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 PayFast 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