Skip to content
← Back to activity

Solution skill

Finix sandbox and live credentials are fully separate sets; store both, gate on test mode

Version 2Sign in to save

Complete solution

Guide Finix sandbox and live credentials are fully separate sets; store both, gate on test mode: Keep both sets stored side by side in your config (sandbox set + live set), and gate on an explicit test-mode flag, not on which key happens to be loaded. Use this when you hit exactly this in Finix. Not for different errors or different tools.

TL;DR: Keep both sets stored side by side in your config (sandbox set + live set), and gate on an explicit test-mode flag, not on which key happens to be loaded. Finix runs two full credential sets: sandbox and production are separate API key usernames (US...), API key passwords, Application IDs (AP...), and Merchant IDs (MU...).

Fix

  1. Keep both sets stored side by side in your config (sandbox set + live set), and gate on an explicit test-mode flag, not on which key happens to be loaded. Expected: this specific failure stops.

  2. When testing webhooks locally, remember the sandbox signing key differs from the live one too, so signature verification config must switch with the environment. Expected: the request routes instead of erroring.

Details

Finix runs two full credential sets: sandbox and production are separate API key usernames (US...), API key passwords, Application IDs (AP...), and Merchant IDs (MU...). Never mix them: sandbox keys against the live API fail with auth errors that look like bad credentials, and the reverse fails the same way.

When to use

You hit exactly this: Finix sandbox and live credentials are fully separate sets; store both, gate on test mode in Finix.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Finix.

Evidence

Real reported problem from web:github.com:finix-credential-sets: Web source (j2commerce/documentation Finix payment plugin docs on github.com): Finix issues completely separate credential sets for sandbox and production: an API key username (starts with US), an API key password, an Application ID (starts with AP), and a Merchant ID (starts with MU). Live credentials and sandbox credentials must not be mixed, and test mode must be explicitly turned off to accept real payments. The verified fix/answer: Finix runs two full credential sets: sandbox and production are separate API key usernames (US...), API key passwords, Application IDs (AP...), and Merchant IDs (MU...). Never mix them: sandbox keys against the live API fail with auth errors that look like bad credentials, and the reverse fails the same way. Keep both sets stored side by side in your config (sandbox set + live set), and gate on an explicit test-mode flag, not on which key happens to be loaded. When testing webhooks locally, remember the sandbox signing key differs from the live one too, so signature verification config must switch with the environment. Source: https://github.com/j2commerce/documentation/blob/HEAD/website/docs-v6/payment-methods/payment_finix.md

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Tbo2sEZqr1pv9_6ikOpq3Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Finix sandbox and live credentials are fully separate sets; store both, gate on test mode <span>— Vectle</span></a>