> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cryptoprocessing.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure callbacks

export function Available({to, except}) {
  const roles = <Tooltip tip="Roles determine what each user can see and do in the portal." cta="See role descriptions" href="/merchant-administration/add-a-user#determine-which-role-to-use">roles</Tooltip>;
  if (to) {
    return <><strong>Available to {roles}:</strong> {to.map(role => <>{" "}<Badge color="blue">{role}</Badge></>)}</>;
  } else {
    return <><strong>Available to all {roles} except</strong> {except.map(role => <>{" "}<Badge color="blue">{role}</Badge></>)}</>;
  }
}

<Available to={["Owner"]} />

Choose which additional callbacks CryptoProcessing sends for deposits and withdrawals, and which fields they include.

## Additional callbacks

CryptoProcessing can send callbacks for these additional events, each of which you can enable or disable independently:

* **Deposits less than minimum amount** — sent when a deposit doesn't meet the minimum amount, enabled by default. See [callback examples](/api-reference/callbacks/deposit-callbacks).
* **Cross-currency deposits** — sent when a deposit's currency differs from the address's currency, enabled by default. See [callback examples](/api-reference/callbacks/deposit-callbacks).
* **Business wallet transactions** — sent for deposits to portal-created addresses and portal-initiated withdrawals, including individual withdrawals from a mass payout, disabled by default.

<Steps>
  <Step>
    In your portal, go to **Settings** and open the **Callbacks** tab.
  </Step>

  <Step>
    Under **Additional callbacks**, click **Manage**.
  </Step>

  <Step>
    Enable or disable the callbacks you want to change, then click **Save changes**.
  </Step>
</Steps>

## Callback parameters

By default, deposit callbacks don't include the sender's blockchain address, but you can enable it for your account at any time.

<Steps>
  <Step>
    In your portal, go to **Settings** and open the **Callbacks** tab.
  </Step>

  <Step>
    Under **Callback parameters**, click **Manage**.
  </Step>

  <Step>
    Enable **Sender address**, then click **Save changes**.
  </Step>
</Steps>

When enabled, the sender's address is included as `transactions[].sender.address` in [deposit callbacks](/api-reference/callbacks/deposit-callbacks) and shown for individual transactions in the [portal](/portal#viewing-transactions-history) — unless the deposit has multiple sender addresses, in which case it's omitted from both.