Merchant Down Escalation

Merchant Down Escalation

Title: Merchant Down Escalation

Purpose:
Use this SOP when a merchant is unable to process payments and the issue is business-critical.

When to use:
Use this process when the merchant cannot accept card payments, the terminal is fully offline, transactions are failing, or service interruption is impacting operations.

Steps:

  1. Create or update the ticket immediately and set priority to High/Urgent.

  2. Confirm merchant details: business name, MID, location, contact person, callback number, and processor.

  3. Identify the exact impact: terminal offline, payment gateway issue, settlement issue, declined transactions, or connectivity problem.

  4. Check whether the issue is isolated or affecting multiple merchants.

  5. Perform initial troubleshooting if applicable.

  6. Escalate to the appropriate processor/support team immediately.

  7. Add all timestamps and actions taken in the ticket.

  8. Keep the merchant updated at agreed intervals until service is restored.

  9. Once resolved, confirm the merchant can successfully process a live transaction.

  10. Document root cause and resolution before closing.

Escalation rule suggestion:

  • Urgent ticket created

  • Notify assigned rep immediately

  • Notify manager if unresolved after X hours

  • Trigger follow-up update reminders until resolved

    • Related Articles

    • Terminal Swap Procedure

      Purpose: Use this SOP when a merchant reports that their terminal is faulty and needs to be replaced. When to use: Use this process for hardware issues such as terminal not powering on, frozen screen, connectivity failure, damaged unit, or repeated ...