A unique checkout reference
The proposed checkout screen displays receiving details and TK-8492 with a copy button and expiry timer. The reference helps distinguish equal-value orders but is not payment proof by itself.
The demo below shows the flow we are building: an order with a unique reference, a signal from an authorized payment source, server-side matching, and a safe store update. A 1.2-second result is a demo target, not a live or guaranteed service speed.
Explore the stagesThe proposed checkout screen displays receiving details and TK-8492 with a copy button and expiry timer. The reference helps distinguish equal-value orders but is not payment proof by itself.
Customers pay with their usual app. When a trusted signal source and merchant consent are available, only event data needed for matching is sent. Permissions and connection details will follow app testing and release.
The server compares amount, reference, timing, and a transaction identifier if the source provides one, then checks duplicates. Missing or conflicting evidence goes to human review.
Once conditions are met, the planned integration updates order status. Customer messages or shipping preparation depend on separate store, messaging, and carrier integrations and are not live yet.
Amount, time, and authorized data may suggest possible matches, but the order stays in review until evidence is sufficient.
The shortfall is shown for follow-up. The merchant can ask the customer to complete it; the order is not automatically marked fully paid.
A screenshot alone cannot prove money arrived. Reference, duplicate, and source checks prevent relying on an untrusted image.
Later synchronization is a design goal to validate when the app is built. Unconfirmed cases remain available for review.
Direct payments go to the merchant account. Taakeed Pay does not ask for bank login details, PINs, or OTPs. App permissions, encryption, and retention details will be published after implementation and security testing; we do not present an unverified technical standard as a current certification.
Read the security approachCheck the WooCommerce or Shopify page for release status and setup instructions once published.
When the listener app is released, follow its permission and privacy guide on a dedicated device with your consent.
After connecting, make a test order and verify detection, matching, and status updates before relying on automation.
This depends on the operating system and signal source. We will publish device and operating requirements after testing the listener app.
We plan interruption handling and later sync, but cannot promise to capture an event the source never received or confirm a payment without sufficient evidence.
Limits will depend on the plan and available signal sources. Actual limits will be announced before live connections open.
These steps require separate messaging and carrier integrations. Their availability will be listed on each integration page.