Error Handling in Europe

​

Types of error handling

​

Commando Mode

• Manual Commando Mode – Manually activated by the API or the Marqeta Dashboard.
  • Approves all transactions on your behalf for the specified time duration.
  • Used for a period of known downtime.
  • Follows standin_approved_by = COMMANDO_MANUAL.
• Automated Commando Mode – Automatically enabled or disabled on a per-transaction basis.
  • Follows real_time_standin_criteria.enabled = true.
    • include_connection_errors – Unable to establish connection to your endpoint.
    • include_response_timeouts – Gateway response slower than 3000ms.
    • include_application_errors – An application error (any non-connection, non-timeout error).
    • standin_approved_by = COMMANDO_AUTO.

{
  "transactions": [
    {
      "type": "authorization",
      "state": "DECLINED",
      "response": {
        "code": "0000",
        "memo": "Approved or completed successfully"
      },
      "network": "VISA",
      "subnetwork": "VISANET",
      "standin_approved_by": "COMMANDO_AUTO",
      "standin_by": "COMMANDO_AUTO"
    }
  ]
}

​

Webhook replay

• A messaging failure is defined as any HTTP response code other than 200.
• In the case of a messaging failure, the Marqeta platform:
  • Attempts to resend a notification message 10 times.
  • Exponentially increases the interval between retries by powers of 4, following a retry interval of: 4 seconds, 16 seconds, 64 seconds, and so on, up to an interval just over 12 days.
• In the event of a failure, you can replay events by sending a POST request to the /v3/webhooks/{token}/{event_type}/{event_token} endpoint.
  • {token} – The token of your webhook configuration endpoint.
  • {event_type} – The event type.
  • {event_token} – The token of the event itself. This can be a transaction token or card transition token.

​

Idempotency

• Each transaction is identified by a unique transaction token.
• Each webhook is identified by a unique event token.

​

Error handling responsibilities