Frequently asked questions
Answers reflect the current implementation and separate available behavior from Planned work.
Is Rabet a payment gateway?
No. It is a developer integration tool, not a bank, acquirer, or payment service provider. Payment and settlement relationships are between the merchant and provider.
Which real gateway works now?
The UPayments v2 adapter is the current real integration. A second mock adapter tests the programming contract and is not a production gateway.
Is KNET integrated today?
Yes, as an optional selector inside the UPayments adapter, not as a separate gateway. Send payment_method:"knet" to emit paymentGateway.src=knet. UPayments must enable White Label and KNET on the merchant account; the code cannot grant approval or activate the account, and processing and settlement remain with the provider and KNET.
What is MyFatoorah's current status?
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. It is not exposed in foundation; v3 and credentialed operation are not implemented yet.
Does the site collect card or customer data?
The static site does not request it. The core does not persist or log optional customer fields, but merchant-provided values may travel directly from the merchant environment to the provider and fall under merchant/provider policies.
Does it work automatically with any website?
No. The current generator targets an existing Laravel project. A Laravel, WordPress, and Next.js scanner is Planned and unavailable today.
Does doctor validate credentials?
No. It checks token-variable presence, lightweight API-host reachability, and local tool detection. Gateway acceptance requires a safe provider-side test.
Can init overwrite my files?
The current scaffold previews first and skips existing files. Still use Git and backups and review the file plan and generated content.
Is the Web Component enough by itself?
No. The generator creates a secure endpoint, but it is disabled by default; the merchant must configure env and prices, run the migration, register routes, and operate a Laravel server runtime. The component sends only offer_id, while authentication, authorization, amount, and order state remain on the server.
What does sandbox prove?
On 17 July 2026, a credentialed 1.500 KWD UPayments Sandbox payment reached CAPTURED and was confirmed server to server. The credential was redacted and must not be reused. This proves test-environment behavior only, not production or settlement. The public /return route returned 404 at capture time, and this release adds a safe status-page fallback, but no public backend or webhook is deployed yet.
Which licence applies?
Apache-2.0 governs the code. It does not generally license trademarks, and the NOTICE and source conditions remain relevant.
How do I contact support or report security?
Email Info@almorshednet.com. Send a redacted error and public-safe context; never send tokens, PAN, CVV, or customer data.