Fix 500 WALLET_PASS_CREATE_FAILED and related server errors

What 500 responses such as WALLET_PASS_CREATE_FAILED and NOTIFICATION_SEND_FAILED mean, which are safe to retry and what to send support.

Last updated 2026-11-05

HTTP 500

{ "error": true, "error_code": "WALLET_PASS_CREATE_FAILED", "message": "Failed to create wallet pass.", "timestamp": "..." }

These are failures on Shakewell's side or with Apple or Google: WALLET_PASS_CREATE_FAILED, WALLET_PASS_UPDATE_FAILED, WALLET_PASS_DELETE_FAILED, WALLET_PASS_RETRIEVE_FAILED, WALLET_PASS_LIST_FAILED, NOTIFICATION_SEND_FAILED, BULK_NOTIFICATION_SEND_FAILED and INTERNAL_ERROR. Production responses carry a generic message by design.

Fix

Reads (GET) are safe to retry. Retry with backoff.
Before retrying a create, list passes by the customer's details to be sure the first call did not succeed.
If it persists, email support@shakewellwallet.com with the error_code, the timestamp and the time you sent the request.