A payment integration you can review before running

Rabet brings inspection, file planning, confirmation, and verification into one path inside the merchant project without moving secrets to the public site.

Problem and outcome

Payment setup is often split across environment, files, browser return, and webhooks. Rabet shows the change first, waits for a human decision, then explains independent server verification.

Available components

  • CLI and MCP
  • Eight-path Laravel generator: environment template, model, two controllers, UPayments client, configuration, migration, and routes
  • The Web Component sends offer_id only; the server owns amount and order with idempotency and a database lock
  • UPayments in foundation; a deferred MyFatoorah v2 prototype has offline contract tests

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.

Install the public foundation

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

This foundation build is for review and is not a production-payment readiness claim. npm.

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.

Current boundaries

Rabet is not a payment provider and does not automatically create a merchant account, price, or subscription. Every commercial request currently starts as a manual email; production requires merchant and provider setup.