Corporate banking data events
This table lists the corporate banking endpoints and the events they generate. For information on setting up event notifications, see the Data and reporting overview.
| Endpoint | Event | URL | Description |
|---|---|---|---|
| Create corporate account | succeeded-1 corporate_creation-1 | POST /corporate/v1/corporate-accounts | Platform generates events when a client creates a corporate account. |
| Update corporate account | status-change-2 | PATCH /corporate/v1/corporate-accounts/{accountId} | Platform generates event when a client changes an account status. |
| Close corporate account | status-change-2 | PATCH /corporate/v1/corporate-accounts/{accountId}/close | Platform generates event when a client closes an account. |
| Initiate a payment | authorization-event-1 change_available-1 balance_change-1 creation-1 evaluation_requested-1 corporate-1 entry_creation-1 | POST /corporate/payments | Platform generates two or more events during the validation process. |
| Initiate a forced payment | authorization-event-1 change_available-1 balance_change-1 creation-1 corporate-1 entry_creation-1 | POST /corporate/payments/force | Platform generates two or more events during the validation process. |
| Schedule a payment | schedule_payment-1 authorization-event-1 change_available-1 creation-1 corporate-1 | POST /corporate/payments/schedules | Platform generates schedule_payment-1 event shortly after a client schedules a payment. Subsequent events are generated when the transaction is executed. |
| Cancel a scheduled payment | schedule_payment-1 | DELETE /corporate/payments/schedules/{scheduleId} | Platform generates event when a client cancels a scheduled payment. |
| Balance change | balance_change-1change_available-1 | POST /corporate/v1/payments | Platform generates events on new transactions, any earmark operation, or credit limit changes. |
| Create earmark | authorization-event-1 change_available-1 balance_change-1 creation-1 corporate-1 earmark-1 | POST /corporate/v1/earmarks | 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. |
| Create force earmark | authorization-event-1 change_available-1 balance_change-1 creation-1 corporate-1 earmark-1 | POST /corporate/v1/earmarks/force | 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. |
| Execute earmark payment | authorization-event-1 change_available-1 balance_change-1 creation-1 corporate-1 earmark-1 | POST /corporate/v1/earmark-execution | Platform generates events when a client executes an earmark payment. The earmarking process generates all these events because it triggers an internal transfer in the platform. |
| Update earmark | authorization-event-1 change_available-1 balance_change-1 creation-1 corporate-1 earmark-1 | PATCH /corporate/v1/earmarks/{earmarkId} | 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. |
| Cancel earmark | authorization-event-1 change_available-1 balance_change-1 creation-1 corporate-1 earmark-1 | DELETE /corporate/v1/earmarks/{earmarkId} | 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. |
| Create hierarchy levels | hierarchy_creation-1 | POST /corporate/v1/hierarchies | Platform generates event when a client creates a hierarchy. |
| Create division | division_creation-1 | POST /corporate/v1/divisions | Platform generates event when a client creates a division. |
| Update division | division_change-1 | PATCH /corporate/v1/divisions | Platform generates event when a client modifies a division. |
Updated about 1 month ago