Payment-provider disclosure
Rabet is local developer integration tooling, not a payment service provider, bank, acquirer, or merchant of record. The public site performs no live purchase and asks for no card data.
Providers and evidenced status
- UPayments: the first foundation adapter, with separate Sandbox evidence that is neither production nor real funds.
- KNET: the adapter maps
payment_method:knettopaymentGateway.src=knet. For real use, the provider must enable White Label and KNET on the merchant account; Rabet cannot activate the account. - MyFatoorah: a preliminary v2 prototype is deferred from foundation; Sessions/Payments v3 and credentialed operation remain unimplemented, unevidenced future work.
Authoritative status
A browser return and webhook are operational signals, not final success proof by themselves. The merchant server must validate identity, authority, amount, currency, and order, then independently retrieve provider status before fulfilment or a financial-record transition.
Merchant and provider responsibility
The merchant owns the provider account, production configuration, prices, tax, orders, cancellation or refund policy, reconciliation, and settlement. The provider controls available methods, fees, settlement, and reversals under its merchant agreement. Rabet does not guarantee account approval, method enablement, or transaction outcome.
Secrets and data
Keys, tokens, and webhook secrets stay on the merchant server or in an approved secrets store; never place them in a browser, public repository, or support message. Rotate any secret that appeared in a conversation or log before real testing.
Read Integrations for operational detail and Support for a safe help request. If the versions conflict, the Arabic version governs.