> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/transaction30api/sandbox/user-manual/cashout_full_accepted.md).

# cashout\_full\_accepted

**Goal:** Send a full ticket cashout-inform and receive an **accepted** reply.

Sandbox module name: `cashout_full_accepted`. Prefer `sendCashoutInform` (goldens use cashout-inform); `sendCashout` routes to the same scenarios.

## How to build the request (Java SDK)

{% stepper %}
{% step %}

### Build the inner `CashoutRequest`

Build an inner `CashoutRequest` with a unique `cashoutId`.
{% endstep %}

{% step %}

### Set ticket cashout details

Set details with `CashoutDetails.newTicketCashoutDetailsBuilder()` (JSON type `"ticket"`).
{% endstep %}

{% step %}

### Select the routing method

Route with either:

* **Magic `ticketId`:** `"mock_cashout_full"`, or
* **`meta.punter.id`:** `"customer_cashout_accepted"` with any normal `ticketId`.
  {% endstep %}

{% step %}

### Attach a cash payout

Attach a cash payout (`Payout.newCashPayoutBuilder()`) — amount is not used for routing.
{% endstep %}

{% step %}

### Wrap the request

Wrap in `CashoutInformRequest.newBuilder().setCashout(...)`.
{% endstep %}

{% step %}

### Send the request

Send with `mbsSdk.getTicketProtocol().sendCashoutInform(request)`.

No mobile / ticket context on cashout-inform content.
{% endstep %}
{% endstepper %}

## Java example

```java
import com.sportradar.mbs.sdk.entities.cashout.CashoutDetails;
import com.sportradar.mbs.sdk.entities.common.AcceptanceStatus;
import com.sportradar.mbs.sdk.entities.payout.Payout;
import com.sportradar.mbs.sdk.entities.request.CashoutInformRequest;
import com.sportradar.mbs.sdk.entities.request.CashoutRequest;
import com.sportradar.mbs.sdk.entities.response.CashoutInformResponse;
import java.math.BigDecimal;

CashoutInformRequest request = CashoutInformRequest.newBuilder()
    .setCashout(CashoutRequest.newBuilder()
        .setCashoutId("co-1")
        .setDetails(CashoutDetails.newTicketCashoutDetailsBuilder()
            .setTicketId("mock_cashout_full")
            .setTicketSignature("sandbox-signature")
            .setPayout(Payout.newCashPayoutBuilder()
                .setAmount(new BigDecimal("10"))
                .setCurrency("EUR")
                .build())
            .build())
        .build())
    .build();

CashoutInformResponse response = mbsSdk.getTicketProtocol().sendCashoutInform(request);
// expect: response.getStatus() == AcceptanceStatus.ACCEPTED, getCode() == 0
```

## Wire JSON (what the SDK sends)

```json
{
  "operatorId": 9985,
  "correlationId": "corr-1",
  "timestampUtc": 1710000000000,
  "operation": "cashout-inform",
  "version": "3.0",
  "content": {
    "type": "cashout-inform",
    "cashout": {
      "type": "cashout",
      "cashoutId": "co-1",
      "details": {
        "type": "ticket",
        "ticketId": "mock_cashout_full",
        "ticketSignature": "sandbox-signature",
        "payout": [
          {
            "type": "cash",
            "amount": "10",
            "currency": "EUR"
          }
        ]
      }
    }
  }
}
```

| Field name                                  | Value                 | Mandatory / Optional | Data type | Ignored by sandbox   |
| ------------------------------------------- | --------------------- | -------------------- | --------- | -------------------- |
| `operatorId`                                | `9985`                | Mandatory            | integer   | Yes                  |
| `correlationId`                             | `"corr-1"`            | Mandatory            | string    | No (echoed in reply) |
| `timestampUtc`                              | `1710000000000`       | Mandatory            | integer   | Yes                  |
| `operation`                                 | `"cashout-inform"`    | Mandatory            | string    | No                   |
| `version`                                   | `"3.0"`               | Mandatory            | string    | No (echoed in reply) |
| `content.type`                              | `"cashout-inform"`    | Mandatory            | string    | No                   |
| `content.cashout.type`                      | `"cashout"`           | Mandatory            | string    | No                   |
| `content.cashout.cashoutId`                 | `"co-1"`              | Mandatory            | string    | No (echoed in reply) |
| `content.cashout.details.type`              | `"ticket"`            | Mandatory            | string    | No (routing: full)   |
| `content.cashout.details.ticketId`          | `"mock_cashout_full"` | Mandatory (sandbox)  | string    | No (routing; echoed) |
| `content.cashout.details.ticketSignature`   | `"sandbox-signature"` | Mandatory            | string    | Yes                  |
| `content.cashout.details.payout[].type`     | `"cash"`              | Mandatory            | string    | Yes                  |
| `content.cashout.details.payout[].amount`   | `"10"`                | Mandatory            | string    | Yes                  |
| `content.cashout.details.payout[].currency` | `"EUR"`               | Mandatory            | string    | Yes                  |

Magic map: `mock_cashout_full` → `customer_cashout_accepted`.

## Expected response

| Java getter      | Expected value               |
| ---------------- | ---------------------------- |
| `getStatus()`    | `AcceptanceStatus.ACCEPTED`  |
| `getCode()`      | `0`                          |
| `getMessage()`   | `"accepted"` (sandbox)       |
| `getCashoutId()` | `"co-1"` (echo)              |
| `getTicketId()`  | `"mock_cashout_full"` (echo) |

Wire JSON (content type `"cashout-inform-reply"`):

```json
{
  "correlationId": "corr-1",
  "timestampUtc": 1710000001000,
  "operation": "cashout-inform",
  "version": "3.0",
  "content": {
    "type": "cashout-inform-reply",
    "cashoutId": "co-1",
    "ticketId": "mock_cashout_full",
    "status": "accepted",
    "code": 0,
    "message": "accepted",
    "signature": "sandbox-signature"
  }
}
```

## Common mistakes

| Mistake                       | Result                                                                                       |
| ----------------------------- | -------------------------------------------------------------------------------------------- |
| Using `mock_cashout_rejected` | Hits [`cashout_full_rejected`](broken://pages/41aa2eb9d1bbb2d407bf8e66a890ef8545d752c0)      |
| Partial details builder       | Routes to [`cashout_partial`](broken://pages/7768693dede2f674b5ad2ca3178bc9b41b1fd30b) steps |
| Wrong magic id / punter       | Fallback `-999`                                                                              |

See also: [Error responses](broken://pages/3cdf760ce49fd6992d47d7772f4a4b9f67f0519f#error-responses) in the parent manual.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sportradar.com/transaction30api/sandbox/user-manual/cashout_full_accepted.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.