Errors

3D Secure could not be initialized

Authorize.net premium checkout — Cardinal/Songbird 3DS JWT or script init failed.

3D Secure could not be initialized

Authorize.net premium checkout tried to start Cardinal/Songbird 3-D Secure (premium.threeDsSetupFailed) and failed — JWT fetch error, missing Songbird URL, or script init exception.

Why this happens

3DS is enabled in checkout config but /api/checkout/authorize-net/cardinal-jwt failed, Songbird could not load, or browser blocked the script. Distinct from later “3D Secure is unavailable” / challenge failures (next phases).

Diagnose and fix

1. Admin: Authorize.net — confirm API credentials, 3DS/Cardinal settings, and Songbird URL.

2. Member: hard refresh; allow third-party scripts; try another browser/card.

3. Temporarily disable 3DS only if policy allows and non-3DS checkout is acceptable.

4. See Authorize.net and Common payment failures.

Related