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
Payment integration
Connect PayFast to Invoice Crowd for signed ZAR invoice checkout and verified settlement, with recurring support when provider requirements are met.
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.
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.
Availability is evaluated before a customer enters checkout.
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 setup and lifecycle operations are active when the merchant passphrase and provider API requirements are satisfied.
The final local state follows provider evidence, not the browser.
Exact form and ITN signature, PayFast VALID postback, unique payment ID, allocation and exact ZAR amount.
PayFast is hidden for non-ZAR invoices. The browser return does not settle the 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 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.
Recurring setup and lifecycle operations are active when the merchant passphrase and provider API requirements are satisfied.
Merchant ID, merchant key, optional passphrase and Live/Sandbox mode.
Exact form and ITN signature, PayFast VALID postback, unique payment ID, allocation and exact ZAR amount.
Focused on eligible South African merchants and ZAR; PayFast controls onboarding, fees and account features.
PayFast is hidden for non-ZAR invoices. The browser return does not settle the 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 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.
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.
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 setup and lifecycle operations are active when the merchant passphrase and provider API requirements are satisfied.
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.
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.