# Banking - Transaction banking

This table lists the transaction banking endpoints and the events they generate. For information on setting up event notifications, see the [Data and reporting overview](https://developers.pismo.io/pismo-docs/docs/data-reporting-overview).

<Table align={["left","left","left"]}>
  <thead>
    <tr>
      <th style={{ textAlign: "left" }}>
        Endpoint
      </th>

      <th style={{ textAlign: "left" }}>
        Event
      </th>

      <th style={{ textAlign: "left" }}>
        Description
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td style={{ textAlign: "left" }}>
        [Create transaction banking account](https://developers.pismo.io/pismo-docs/reference/post-account)
      </td>

      <td style={{ textAlign: "left" }}>
        [Account application created](https://developers.pismo.io/events/docs/onboarding-succeeded-1)\
        [Corporate account created](https://developers.pismo.io/events/docs/account-corporate-creation-1)
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates events when a client creates a corporate account.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        [Update transaction banking account](https://developers.pismo.io/pismo-docs/reference/patch-account)
      </td>

      <td style={{ textAlign: "left" }}>
        [Account status changed](https://developers.pismo.io/events/docs/account-status-change-2)
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates event when a client changes an account status.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        [Close transaction banking account](https://developers.pismo.io/pismo-docs/reference/post-accounts-accountid-close)
      </td>

      <td style={{ textAlign: "left" }}>
        [Account status changed](https://developers.pismo.io/events/docs/account-status-change-2)
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates event when a client closes an account.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        [Post payment](https://developers.pismo.io/pismo-docs/reference/corporate-v2-post-payments)
      </td>

      <td style={{ textAlign: "left" }}>
        [Authorization created](https://developers.pismo.io/events/docs/authorization-authorization-event-1)\
        [Account balance changed](https://developers.pismo.io/events/docs/availables-change-available-1)\
        [Account balance changed](https://developers.pismo.io/events/docs/account-balances-balance-change-1)\
        [Transaction created](https://developers.pismo.io/events/docs/transaction-creation-1)\
        [Evaluation requested](https://developers.pismo.io/events/docs/rules-evaluation-requested-1)\
        [Accounting entry created](https://developers.pismo.io/events/docs/accounting-entry-creation-1)
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates two or more events during the validation process.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        [Post multi-leg payment](https://developers.pismo.io/pismo-docs/reference/corporate-v2-post-multileg-payments)
      </td>

      <td style={{ textAlign: "left" }}>
        [Authorization created](https://developers.pismo.io/events/docs/authorization-authorization-event-1)\
        [Account balance changed](https://developers.pismo.io/events/docs/availables-change-available-1)\
        [Account balance changed](https://developers.pismo.io/events/docs/account-balances-balance-change-1)\
        [Transaction created](https://developers.pismo.io/events/docs/transaction-creation-1)\
        [Evaluation requested](https://developers.pismo.io/events/docs/rules-evaluation-requested-1)\
        [Accounting entry created](https://developers.pismo.io/events/docs/accounting-entry-creation-1)
      </td>

      <td style={{ textAlign: "left" }}>
        Each leg generates all events except one. If flex controls are configured, the additional evaluation\_requested-1 is generated.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        [Schedule a payment](https://developers.pismo.io/pismo-docs/reference/corporate-v2-post-scheduled-payments)
      </td>

      <td style={{ textAlign: "left" }}>
        [Current scheduled payment status displayed](https://developers.pismo.io/events/docs/corporate-schedule-payment-1)\
        [Authorization created](https://developers.pismo.io/events/docs/authorization-authorization-event-1)\
        [Account balance changed](https://developers.pismo.io/events/docs/availables-change-available-1)\
        [Transaction created](https://developers.pismo.io/events/docs/transaction-creation-1)
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates schedule\_payment-1 event shortly after a client schedules a payment. Subsequent events are generated when the transaction is executed.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        [Cancel scheduled payment](https://developers.pismo.io/pismo-docs/reference/corporate-v2-delete-scheduled-payment)
      </td>

      <td style={{ textAlign: "left" }}>
        [Current scheduled payment status displayed](https://developers.pismo.io/events/docs/corporate-schedule-payment-1)
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates event when a client cancels a scheduled payment.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        [Create earmark](https://developers.pismo.io/pismo-docs/reference/post-corporate-v2-earmarks)
      </td>

      <td style={{ textAlign: "left" }}>
        [Authorization created](https://developers.pismo.io/events/docs/authorization-authorization-event-1)\
        [Account balance changed](https://developers.pismo.io/events/docs/availables-change-available-1)\
        [Account balance changed](https://developers.pismo.io/events/docs/account-balances-balance-change-1)\
        [Transaction created](https://developers.pismo.io/events/docs/transaction-creation-1)\
        [Earmark created, updated, or canceled](https://developers.pismo.io/events/docs/corporate-earmark-1)
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates events when a client creates an  earmark. The earmarking process generates all these events because it triggers an internal transfer in the platform.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        [Update earmark](https://developers.pismo.io/pismo-docs/reference/patch-corporate-v2-earmarks-earmarkid)
      </td>

      <td style={{ textAlign: "left" }}>
        [Authorization created](https://developers.pismo.io/events/docs/authorization-authorization-event-1)\
        [Account balance changed](https://developers.pismo.io/events/docs/availables-change-available-1)\
        [Account balance changed](https://developers.pismo.io/events/docs/account-balances-balance-change-1)\
        [Transaction created](https://developers.pismo.io/events/docs/transaction-creation-1)\
        [Earmark created, updated, or canceled](https://developers.pismo.io/events/docs/corporate-earmark-1)
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates events when a client updates an  earmark. The earmarking process generates all these events because it triggers an internal transfer in the platform.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        [Cancel earmark](https://developers.pismo.io/pismo-docs/reference/post-corporate-v2-earmarks-earmarkid-cancel)
      </td>

      <td style={{ textAlign: "left" }}>
        [Authorization created](https://developers.pismo.io/events/docs/authorization-authorization-event-1)\
        [Account balance changed](https://developers.pismo.io/events/docs/availables-change-available-1)\
        [Account balance changed](https://developers.pismo.io/events/docs/account-balances-balance-change-1)\
        [Transaction created](https://developers.pismo.io/events/docs/transaction-creation-1)\
        [Earmark created, updated, or canceled](https://developers.pismo.io/events/docs/corporate-earmark-1)
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates events when a client cancels an earmark. The earmarking process generates all these events because it triggers an internal transfer in the platform.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        [Create hierarchy](https://developers.pismo.io/pismo-docs/reference/post-hierarchies)
      </td>

      <td style={{ textAlign: "left" }}>
        [Corporate hierarchy created](https://developers.pismo.io/events/docs/corporate-hierarchy-creation-1)
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates event when a client creates a hierarchy.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        [Create division](https://developers.pismo.io/pismo-docs/reference/post-division-v2)
      </td>

      <td style={{ textAlign: "left" }}>
        [Corporate division created (deprecated)](https://developers.pismo.io/events/docs/corporate-division-creation-1)
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates event when a client creates a division.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        [Update division](https://developers.pismo.io/pismo-docs/reference/patch-division-v2)
      </td>

      <td style={{ textAlign: "left" }}>
        [Corporate division updated (deprecated)](https://developers.pismo.io/events/docs/corporate-division-change-1)
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates event when a client modifies a division.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        [Create account balance history configuration](https://developers.pismo.io/pismo-docs/reference/post-account-balance-history-configuration)
      </td>

      <td style={{ textAlign: "left" }}>
        [Account balance history configuration created](https://developers.pismo.io/events/docs/account-balances-balance-history-config-creation-1)
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates event when a client creates a balance history configuration.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        [Update account balance history configuration](https://developers.pismo.io/pismo-docs/reference/patch-account-balances-history-configuration)
      </td>

      <td style={{ textAlign: "left" }}>
        [Account balance history configuration changed](https://developers.pismo.io/events/docs/account-balances-balance-history-config-change-1)
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates event when client changes account balance history configuration.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        [Create dormancy configuration](https://developers.pismo.io/pismo-docs/reference/post-dormancy-config-v2)
      </td>

      <td style={{ textAlign: "left" }}>
        [Dormancy configuration created](https://developers.pismo.io/events/docs/corporate-dormancy-config-creation-1)
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates event when dormancy is configured.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        [Update dormancy configuration](https://developers.pismo.io/pismo-docs/reference/patch-dormancy-config-v2)
      </td>

      <td style={{ textAlign: "left" }}>
        [Dormancy configuration updated](https://developers.pismo.io/events/docs/corporate-dormancy-config-change-1)
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates event when client changes dormancy configuration.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        Create check posting
      </td>

      <td style={{ textAlign: "left" }}>
        Platform authorization created
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates event when client creates check posting.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        Create check posting
      </td>

      <td style={{ textAlign: "left" }}>
        Check posting status changed
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates event when client creates check posting.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        Release check
      </td>

      <td style={{ textAlign: "left" }}>
        Platform authorization created
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates event when client releases checks.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        Release check
      </td>

      <td style={{ textAlign: "left" }}>
        Check posting status changed
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates event when client releases checks.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        Cancel check
      </td>

      <td style={{ textAlign: "left" }}>
        Platform authorization created
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates event when client cancels checks.
      </td>
    </tr>

    <tr>
      <td style={{ textAlign: "left" }}>
        Cancel check
      </td>

      <td style={{ textAlign: "left" }}>
        Check posting status changed
      </td>

      <td style={{ textAlign: "left" }}>
        Platform generates event when client cancels checks.
      </td>
    </tr>
  </tbody>
</Table>