A product by AlMorshed Net AlMorshed Net
العربية Start now

Inspect, prepare, and verify your integration

Rabet shows what your project needs, proposes the change, and verifies the result while secrets stay in your environment.

Start the interactive experienceUnderstand the product

Local developer tooling, not a hosted payment gateway. This site collects neither money nor card data.

A product ready to try and download

Try the lab, download the package, or follow the Laravel guide. Commercial installation starts after scope and price are approved.

Choose your path

The evidence and next action adapt to your role while payment and security boundaries stay explicit for everyone.

  • Owner

    Understand preparation, operating responsibilities, and the commercial next step.

    A clear installation request and understood responsibility boundary.

    Start with this evidence: offers · boundaries · status

    Start with this roleRequest an installation purchase link

  • Developer

    Inspect the project, review the file plan, then verify the path locally.

    A reviewable integration backed by commands and tests.

    Start with this evidence: commands · components · tests

    Start with this roleOpen the developer guide

  • Investor & partner

    Assess the product through evidence, limitations, and a grounded roadmap before an investment or partnership decision.

    An honest view of the current surface and partnership path.

    Start with this evidence: milestones · limitations · roadmap

    Start with this roleRequest a partnership discussion

  • Customer

    Understand the redirect to the provider-hosted checkout and the final result.

    A clear payment experience without unnecessary implementation detail.

    Start with this evidence: redirect · privacy · result

    Start with this roleView the educational simulation

What works today?

These capabilities are covered by code and tests, with clear notes on what still needs setup.

  • Local inspection: rabet doctor checks the environment without uploading the project.
  • Plan before write: the generator shows the proposed paths and waits for explicit confirmation.
  • Order control: the component sends offer_id only; the server selects amount and order, with duplicate protection and a database lock.
  • Server verification: a webhook notification and status path re-check CAPTURED.
  • Provider contracts: UPayments is in foundation; the MyFatoorah v2 prototype is deferred with offline contract tests.

Install the published foundation build

The public package is a foundation prerelease, not a production-readiness claim. Review the project and tests before use.

npm install --global "@ween.aro7/rabet-kit@0.1.0-foundation.6"

You can also select and copy the command manually.

Open the public package on npm, then follow the usage and installation guide.

The journey in seven steps

From context selection to result, human approval remains ahead of any apply or payment-link simulation.

  1. 1

    Choose context

    Choose your role and demo environment.

  2. 2

    Inspect the project

    The inspection shows what exists and what is missing.

  3. 3

    Review the plan

    Review eight generated paths before any write.

  4. 4

    Confirm and apply

    No write or link simulation proceeds without explicit confirmation.

  5. 5

    Sandbox redirect

    See an educational redirect to a provider-hosted checkout.

  6. 6

    Webhook and verification

    The merchant server receives an event, then checks status with the provider.

  7. 7

    Result and next action

    Separate the demonstration from available code and merchant setup.

Run the journey in the interactive lab

Merged path from v1 to v12.7

The current site does not discard the earlier work; it merges the strongest parts into one story: product, experience, installation, current status, and payment boundaries.

  1. v1-v3

    Foundation

    Idea documentation, safety boundaries, and the adapter contract before a public interface.

  2. v4-v6

    Installability

    CLI, MCP, and the Laravel generator with preview before write.

  3. v7-v9

    Public experience

    Bilingual pages, offline behavior, and accessibility/content guards.

  4. v10-v11

    First complete public shape

    Official Rabet mark and AlMorshed Net endorsement, with old visual-board image strips removed from the bottom of the site.

  5. v12-v12.3

    Product journey

    Interactive lab, complete legal and operational pages, UPayments Sandbox proof, and a deferred MyFatoorah v2 prototype with contract tests.

  6. v12.4-v12.7

    Product access and verified delivery

    Clear try/download paths, a truthful start wizard, PowerShell-safe install commands, corrected English copy, a rotated cache, and a verified rollback-ready Hostinger package.

Sources ready for the meeting and NotebookLM

These files explain what was done, what works now, and what still needs a merchant decision or secret. They contain no private keys.

  • docs/reports/RABET_PRODUCT_JOURNEY_V12_3_PAYMENT_PROOF_2026-07-17.md

    Payment proof, UPayments Sandbox status, and production boundaries.

  • docs/reports/RABET_PRODUCT_JOURNEY_V12_2_LIVE_2026-07-17.md

    Live build, browser measurements, and public status.

  • docs/reports/RABET_PRODUCT_JOURNEY_V12_2026-07-12.md

    Product journey and the interactive lab.

  • docs/research/KUWAIT_PAYMENT_GATEWAYS_2026-07-11.md

    Kuwait payment-gateway map, KNET, MyFatoorah, and planned providers.

  • docs/superpowers/plans/2026-07-12-rabet-product-journey-v12.md

    Plan for merging product, experience, and content.

Know the difference before you start

The current truth is separated into available code, an educational demo, and work that still needs a decision or setup.

Available

Reviewable, installable code

CLI, MCP, Laravel generator, Web Component, webhook listener, HTTP adapters, and contract tests.

Review evidence and milestones
Interactive demo

A journey simulation with no charge

The lab explains both payment-provider paths without sending a financial request or asking for card data.

View the simulation
Needs setup

Production payment and automated sale

Production payment activation in the live application is blocked until the merchant adds the required merchant secrets and completes provider-account enablement. Purchase and subscription remain manual requests with no invented price.

Request installation or support

Read every gateway boundary