MIQAS
By Ensign

Server-side purchase reporting (for developers)

If a developer maintains your platform, they can report each sale server-to-server. This does the same job as the checkout snippet in a stronger way. Pick one way to report sales, never two at once; if the same order is ever sent twice by mistake, MIQAS keeps only one copy.

Send one POST per order to the capture endpoint, authenticated with your capture key (find both, prefilled, under Settings → Integrations → Server):

POST https://miqas.ensignksa.com/api/events/capture
Header: X-MIQAS-Capture-Key: <your capture key>
Body (JSON):
{
  "event_name": "purchase",
  "external_order_id": "ORDER_12345",
  "amount": 199.00,
  "currency": "SAR",
  "email": "customer@example.com",
  "landing_url": "https://store.example/?fbclid=..." 
}

Include landing_url (or the click ids and UTMs directly) when you have them; that is what lets MIQAS attribute the sale to the exact campaign. Email and phone are hashed before storage.

Verify it worked
Send one test order. The response returns the attributed platform, and the order appears in MIQAS within seconds.