less than a minute read • Updated 4 minutes ago
Stitch Express
Easily accept payments with Stitch Express on your Webflow site for South African payment processing, with card, Apple Pay, Google Pay, and Capitec Pay options.
- Countries
South Africa
Stitch Express is a payment gateway built for South African merchants. It processes payments in ZAR only, and is the current name for the integration formerly called WigWag. If you sell to South African customers and need a local payment method, this is the gateway to use.
Setting up Stitch Express
You will need a Stitch Express account before you start.
Planning to sell subscriptions? Contact Stitch Express support and ask them to enable Card Consent on your account before you rely on Foxy's subscription functionality. See $0 subscription support below — it has an important limitation.
Redirect URL
Stitch Express hands the customer off to a Stitch-hosted payment page, then redirects them back to your Foxy checkout. Stitch only shows that payment page when the return address Foxy sends matches a redirect URL registered in your Stitch Express account. If your checkout URL isn't registered, or doesn't match exactly, the customer sees a 404 | Page not found error instead of the payment form and can't complete the purchase.
To register it:
The URL to add follows this pattern: https://YOUR-STORE.foxycart.com/checkout, substituting your own store subdomain. If you use a custom store subdomain such as secure.yourstore.com, use https://secure.yourstore.com/checkout instead.
Enter it exactly as shown. It must start with https://, not http://. If you later change your store subdomain, update the redirect URL in Stitch Express to match.
Going live
The panel is split into a Live setup block and a Test setup block carrying the same two fields, Client Id and Client Secret. There is no third credential for this gateway.
Testing
Foxy provides shared test credentials for Stitch Express, so you can run test transactions without setting up your own sandbox account. Leave the Test setup fields as they are.
Those shared credentials are for testing the integration only. If you want to test against your own Stitch Express account configuration, get your own Test Credentials from the Stitch Express dashboard's Account page and enter them into the Test setup fields instead.
Obtaining a test account
Sign up at the same place as a live account, stitch.money/express — Stitch Express test and live credentials both live on the same account's dashboard.
Test card numbers
The wiki does not publish Stitch Express test card numbers, and none were found in this pass. Contact Stitch Express for current test card details.
Advanced features
$0 subscription support
Stitch Express's Card Consent API — the mechanism Foxy uses for subscription payments on this gateway — does not currently support $0 payment requests. In practice this means:
Future-dated subscriptions (where the first charge is scheduled for later, with no charge due today) are not supported.
Subscription modifications that would produce a $0 charge today are not supported either.
Regular subscriptions with a non-zero charge due at the time of purchase or modification work normally. If your subscription model depends on $0 starts or $0 modification transactions, check with Stitch Express before committing to this gateway.
Important notes and caveats
ZAR only. Stitch Express does not support other currencies. Confirm your template set locale before going live (see step 7 above).
Card Consent is opt-in. It is not enabled by default — you must contact Stitch Express support to turn it on before subscriptions will work.
$0 transactions are unsupported for subscriptions using Card Consent — see above.
The redirect URL must be registered, or the Stitch payment page returns a 404 error and customers can't pay. See Redirect URL above.
Troubleshooting
The wiki has no published response-code guidance for Stitch Express. Contact Stitch Express support — they own the response codes and can see transaction detail on their side that Foxy cannot.
If the Stitch payment page shows 404 | Page not found when a customer leaves your checkout to pay, your checkout URL isn't registered as a redirect URL in Stitch Express, or doesn't match exactly. A common cause is registering it with http:// instead of https://. See Redirect URL above.
If customers are not returned to your checkout after paying, check that your checkout domain is registered as a redirect URL in the Stitch Express dashboard (see Redirect URL above).