Transaction schemes are used to direct the flow of transactions in °neo Accounts. For instance, how an incoming payment is routed from the counter accounts to the eventual beneficiary account. Or from which account interest is paid to a customer and how it is routed. Transaction schemes are part of a product template and are applicable for all accounts that are created as part of that product.
Transaction schemes can be created and updated, even when a transaction scheme is part of a product that is published.
The name and description are parameters for the entire transaction scheme. Each transaction scheme is made up from one or more transaction bindings, which represent a certain operation and its flow through the system. Each binding is defined with:
Denotes the operation type for the binding.
The counter account denotes the debit/credit side of the transaction.
Is optional to make the binding specific for one payment source.
Is optional to make the binding specific for one payment type.
Is optional to make the binding specific for one payment subtype.
Is optional to make the binding specific for one message type.
For informative purposes only.
Transaction bindings can be created, updated and deleted on any scheme.
Updated 5 months ago