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.
Endpoint | Event | Description |
---|---|---|
Create corporate account | Account application created Corporate account created | Platform generates events when a client creates a corporate account. |
Update corporate account | Account status changed | Platform generates event when a client changes an account status. |
Close corporate account | Account status changed | Platform generates event when a client closes an account. |
Post a payment | Authorization created Account balance changed Account balance changed Transaction created Evaluation requested Accounting entry created | Platform generates two or more events during the validation process. |
Post a multi-leg payment | Authorization created Account balance changed Account balance changed Transaction created Evaluation requested Accounting entry created | Each leg generates all events except one. If flex controls are configured, the additional evaluation_requested-1 is generated. |
Schedule a payment | Current scheduled payment status displayed Authorization created Account balance changed Transaction created | 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 | Current scheduled payment status displayed | Platform generates event when a client cancels a scheduled payment. |
Create earmark | Authorization created Account balance changed Account balance changed Transaction created Earmark created, updated, or canceled | 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. |
Update earmark | Authorization created Account balance changed Account balance changed Transaction created Earmark created, updated, or canceled | 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 created Account balance changed Account balance changed Transaction created Earmark created, updated, or canceled | 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 | Corporate hierarchy created | Platform generates event when a client creates a hierarchy. |
Create division | Corporate division created (deprecated) | Platform generates event when a client creates a division. |
Patch division | Corporate division updated (deprecated) | Platform generates event when a client modifies a division. |
Create account balance history configuration | Account balance history configuration created | Platform generates event when a client creates a balance history configuration. |
Update account balance history configuration | Account balance history configuration changed | Platform generates event when client changes account balance history configuration. |
Create dormancy configuration | Dormancy configuration created | Platform generates event when dormancy is configured. |
Update dormancy configuration | Dormancy configuration updated | Platform generates event when client changes dormancy configuration. |
Updated 17 days ago