Integrations and evidence boundaries

UPayments v2

On 17 July 2026, a credentialed UPayments Sandbox payment for KWD 1.500 reached CAPTURED and was reverified server-to-server. The credential was redacted and must not be reused. This is not production proof; the public return URL returned 404 at capture time, and this release adds a safe status-page fallback, but no public webhook or backend is deployed. Production requires a private merchant credential, approved pricing, and provider account activation.

Official UPayments v2 documentation — documentation reference only.

KNET through UPayments

The adapter maps payment_method:knet to paymentGateway.src=knet, but for real use the provider must enable White Label and KNET on the merchant account; Rabet cannot activate it.

MyFatoorah

A MyFatoorah v2 HTTP prototype with offline contract tests exists, but it is deferred from the foundation release and is not exposed through MCP. v3 and credentialed operation remain future work. The v2 prototype exists as code and contract tests but is deferred; v3 and credentialed operation are not implemented yet.

Official MyFatoorah API-key documentation — documentation reference only; keys do not belong in the browser.

Separate WeenAro7 status

Remediation of the WeenAro7 UPayments v2 integration is underway. Merchant secrets were not supplied to this Rabet verification, and the public Rabet site contains none. The case-study links are separate public interfaces, not a Rabet purchase or payment proof.

Other providers

Tap, Hesabe, Payzah, Casheer, Ecom, Tahseeel, K-lick Pay, and SADAD remain research/planning entries only, without ready adapters or sandbox evidence.