> For the complete documentation index, see [llms.txt](https://docs.omni.integratedcommerce.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omni.integratedcommerce.io/hosted-payment-form/transaction-results.md).

# Transaction result parameters

Fields appended to returnUrl after a hosted payment attempt.

Server-generated redirects append these fields to your `returnUrl`. Fields depend on the outcome; do not require every field on every redirect.

| Parameter         | Description                                                                                                                                                                     |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `success`         | `true` when the form accepts the result, otherwise `false`. ACH acceptance is not settlement.                                                                                   |
| `paymentMethodId` | The resulting token when available; otherwise the initiating payment method. Present on the success path.                                                                       |
| `resultCode`      | The transaction result code, such as `0`, `4001`, `6800`, or `6900`. Some error paths fall back to `9999`.                                                                      |
| `cardType`        | Card brand on a card result, when available.                                                                                                                                    |
| `accountType`     | Funding classification when available: `Credit`, `Debit`, `Checking`, or `Savings`. The immediate hosted ACH path uses lowercase `checking` or `savings`.                       |
| `transactionId`   | Transaction ID on a server-generated result redirect.                                                                                                                           |
| `referenceId`     | The reference sent when creating the session.                                                                                                                                   |
| `amount`          | The requested session amount on a successful card sale or authorization. ACH success redirects use `0`; this field does not prove the settled amount. Tokenization can omit it. |
| `invoiceNumber`   | Invoice number, when supplied.                                                                                                                                                  |
| `orderNumber`     | Order number, when supplied.                                                                                                                                                    |
| `actionType`      | The form action on a server-generated failure redirect.                                                                                                                         |
| `errorMessage`    | Failure explanation, when applicable.                                                                                                                                           |
| `errorCode`       | Specific failure code, when applicable.                                                                                                                                         |
| `hash`            | Lowercase HMAC-SHA256 of `referenceId + resultCode`, keyed with the initiating session's payment method ID. Only server-generated redirects carry this hash.                    |

Client-side SDK failures can redirect with an error code and no hash or transaction ID. Treat those as interface errors and reconcile the request through your backend.

{% hint style="danger" %}
Browser parameters are untrusted. Verify the [redirect hash](/hosted-payment-form/redirect-verification.md) when present, then confirm the transaction, merchant, reference, amount, and outcome through a verified [webhook](/webhooks/webhooks.md) or authenticated [transaction retrieval](/payments/transaction-retrieval.md) before fulfillment. The hash covers only `referenceId` and `resultCode`.
{% endhint %}