Verification recommendations

​

Recommended polling interval

​

Timeouts — when to stop polling

1. Mark the transaction as expired in your database (application-level status, not LigdiCash).
2. Inform the user that the processing is in progress and that they will be notified.
3. Keep listening for the callback — if it arrives, re-verify with confirm and update.

​

Hybrid strategy — primary callback + fallback polling

1. Create the transaction → store the token and status = "pending"
2. Configure a callback_url reachable from the internet
3. On callback receipt:
     → Call confirm with the creation token
     → Update your database
4. If the callback does not arrive after 2 minutes:
     → Trigger a fallback polling (async job)
     → 10 attempts, every 5 seconds
5. If polling timeout:
     → Mark "expired" in the database
     → Keep processing the callback if it arrives late

​

Handling pending transactions

• Approval mode (Moov Africa) — the customer must confirm on their mobile app, which can take several minutes.
• Expired OTP — the customer did not enter the OTP in time. The transaction will stay pending then move to notcompleted after expiration.
• Operator network congestion — rare but possible during traffic spikes.
• Payout awaiting funds — if the merchant account balance is insufficient at the moment of initiation.

async function reCheckExpiredTransaction(token) {
  const res = await fetch(
    `https://app.ligdicash.com/pay/v01/redirect/checkout-invoice/confirm/?invoiceToken=${token}`,
    {
      headers: {
        Apikey: process.env.LIGDICASH_API_KEY,
        Authorization: `Bearer ${process.env.LIGDICASH_API_TOKEN}`,
        Accept: "application/json",
      },
    }
  );
  const data = await res.json();

  if (data.status === "completed") {
    await updateOrder(token, "paid");
  } else if (data.status === "notcompleted") {
    await updateOrder(token, "failed");
  }
  // If still "pending", leave the scheduled job for the next check
}

​

Related pages

• Polling vs callback — choosing the right strategy
• Callback — security — re-verification with confirm
• Callback — idempotency — deduplicating the two requests
• Validation modes — USSD OTP, SMS OTP, approval
• Response codes and statuses — full reference