Error - General system failure

[ahteshamsid]

encountering authorization failures in Sandbox with the same processor configuration error, even after the earlier confirmation that settings were updated for our merchant profile.

Current error:
- `status`: `SERVER_ERROR`
- `reason`: `SYSTEM_ERROR`
- Transaction details show Reason Code `150` with message:
  `The following property is either invalid or missing: usd_outlet_id, usd_terminal_id`

Recent request IDs:
- `7812832862116200504807`
- `781283285826200204807`

What we have validated on our side:
- JWT capture context and transient token generation are successful.
- Token verification passes (`verifyIsValid = true`).
- Payment payload is well-formed and includes required billTo fields (including email), amount details, and tokenized card data.

Please help!!!

[nathn34]

Hi,

This one is actually pretty clear from the error you shared.

The request is failing **before payment processing**, because two required fields are missing in the merchant configuration:

> `usd_outlet_id`

> `usd_terminal_id`

Even if your JWT, tokenization, and payload are correct, the sandbox will reject the transaction if these merchant identifiers are not attached.

What to check:

* Make sure your merchant profile in sandbox has an **active outlet + terminal assigned**

* Confirm those IDs are being passed in the **correct section of the request (not inside payment token or billTo)**

* Double-check environment mismatch (sandbox merchant IDs vs production IDs — this is a very common issue)

Reason Code `150` usually means:

“merchant setup incomplete or invalid configuration”, not a card or payload problem

So your flow is actually working — the block is purely on merchant setup.

If those IDs are already set in your dashboard, try:

* Re-saving the merchant configuration

* Regenerating credentials / API key context

* Retesting with a fresh sandbox merchant session

If it still fails after that, it’s likely a backend provisioning issue and support will need to re-sync your merchant profile.

[alextaylorone]

The fact that transient token generation and token validation are succeeding is useful here, because it narrows the failure down to the payment authorization path rather than the tokenization step. I would avoid changing the JWT or card payload until the merchant-side configuration is confirmed.

Since the error explicitly names usd_outlet_id and usd_terminal_id, I'd have Cybersource support verify that those values are provisioned and associated with the exact sandbox merchant profile being used by these requests. Providing the two request IDs should also make it easier for them to check the backend logs and determine whether this is a configuration or provisioning issue.