Skip to main content
Support is reached through the support link in the dashboard at app.prosperavest.com, signed in to the account the question is about.

​
What to include

  • The requestId of the failing request. It is in the error body and in the X-ENSC-Request-Id header of every response, and it identifies the exact request on ENSC’s side.
  • The conversion reference when the question is about a conversion, in particular one in requires_manual_review: a short payment, a payout that could not be completed, or a destination mismatch is resolved by a person at ENSC.
  • The environment (Sandbox or Live) and the chain (celo-sepolia or celo).
  • The error code (ENSC_…) and the SDK version (@ensc/sdk 0.4.1 is current).
Never include a secret: not your API key, encryption key, signing private key or wallet private key. Key ids (enc_…, sig_…) and your merchant id (mrc_…) are not secret and are fine to share.

​
Before you write

  • Errors lists every code with its meaning; many are resolved by a retry or a corrected request.
  • Webhooks: GET /v1/events/{id} and the dashboard show every delivery attempt with the HTTP status your endpoint answered.
  • IP allowlist covers ENSC_IP_NOT_ALLOWED and ENSC_IP_ALLOWLIST_REQUIRED.
  • A leaked credential: revoke it in the dashboard immediately, generate a replacement and deploy. See Going live.

​
Persistent 5xx and voucher failures

ENSC_SIGNER_UNAVAILABLE and ENSC_SIGNER_REFUSED (the voucher could not be issued) and any 5xx that persists after the SDK’s automatic retries are worth a support case with the requestId.