---
title: "Stitch Launches PayShap Request for SA Enterprise RTP"
description: "Stitch launched PayShap Request in South Africa, letting enterprises send pay requests to banking apps with multi-acquirer routing for higher reliability."
canonical_url: "https://liners.com/news/stitch-payshap-request-south-africa-enterprise"
markdown_url: "https://liners.com/news/stitch-payshap-request-south-africa-enterprise.md"
type: "article"
language: "en"
published_at: "2026-08-04T19:22:28.189Z"
updated_at: "2026-08-04T19:21:52.696Z"
---

# Stitch Launches PayShap Request for SA Enterprise RTP

Stitch launched PayShap Request in South Africa, letting enterprises send pay requests to banking apps with multi-acquirer routing for higher reliability.

## Breadcrumbs

- [News](/news)
- [Stitch Launches PayShap Request for SA Enterprise RTP](/news/stitch-payshap-request-south-africa-enterprise)

## Content

## In Short
- Stitch launched PayShap Request for enterprise businesses in South Africa.
- It lets merchants request real-time payments inside a customer’s banking app.
- The product uses multi-acquirer redundancy and smart routing to reduce payment downtime.

## What Happened: Stitch PayShap Request For Real-Time Payments
On August 4, 2026, [Stitch](/stitch) launched PayShap Request for South African enterprise businesses that want to collect real-time payments across major banks. PayShap Request is a “request to pay” flow, meaning a business sends a payment request to a customer’s banking app, and the customer approves it there. Settlement happens in near real time, which is closer to an instant bank transfer than a card payment.

Stitch says several enterprise clients have already moved collections to real-time payment rails (real-time payments infrastructure that clears and settles quickly). Unlike checkout flows that redirect users to internet banking or require manual account entry, PayShap Request is designed to reduce steps and lower errors.

## What Happened: Multi-Acquirer Architecture and Automated Routing
A key part of Stitch’s announcement is its “multi-acquirer architecture.” In plain terms, that means Stitch maintains live connections to more than one acquiring bank at the same time, instead of relying on a single bank to process requests.

If one acquiring bank has downtime or degraded performance, transactions can be automatically routed through another acquirer. Stitch also says it routes each transaction to the “optimal” acquirer based on real-time availability and success rates. For enterprises, this can reduce failed payments and customer support load during bank incidents.

## Why It Matters: Reliability and One Integration For SA Payments Teams
For large merchants, reliability is often the main constraint when adopting real-time payment methods. A payment option that is fast but frequently unavailable can be worse than a slower one.

Stitch is positioning PayShap Request as an enterprise-grade option that prioritises resilience. It also matters operationally because merchants integrate once via Stitch’s API, then gain access to multiple acquiring relationships without separate contracts and reconciliation flows.

## Sources and products

- [stitch.money](https://stitch.money/blog/stitch-offers-payshap-request-with-redundancies-smart-routing)
- [Stitch](/stitch)

## Related pages

- [Product Launches](/news)

## Access and citation

- [Canonical HTML page](https://liners.com/news/stitch-payshap-request-south-africa-enterprise)
- [Markdown route index](/sitemap.md)
- [Agent access guide](/llms.txt)