Simulate Bank Transactions
Transactions are imported statement transactions from the bank. Transactions are used in reconciliation for payment confirmation. From Modern Treasury's perspective, there are two types of transactions on your bank statements, originated and unoriginated. Below you will find ways to create both types of transactions and some related workflows you may want to test in your sandbox.
Your sandbox is preloaded with special banks, namely Gringotts Wizarding Bank (GWB) and Iron Bank of Bravos (IBB). Payment that use GWB as the originating bank will successfully run through end-to-end, whereas payments using IBB will fail to reach the bank. These allow you to test different states, and you can read more in Simulate a Payment Order Failure.
Originated Payment Transactions
Originated payments are when you as a Modern Treasury customer are originating a debit or credit against a counterparty's account. In Modern Treasury, you accomplish these payments using Payment Orders.
These transactions types can be generated by creating a Payment Order using any Gringotts Wizarding Bank account as the internal account. A few moments after creation of the payment order, Modern Treasury will automatically create a transaction and reconcile the payment order to it.
Unoriginated Payment Transactions
Unoriginated payments are when your bank accounts receive a debit or credit originated by a counterparty (e.g. someone sends you money). These also appear as transactions on your bank statement.
To create these types of transactions, you can Simulating an Incoming Payment Detail. A few moments after the creation of the IPD, Modern Treasury will automatically create a transaction.
Unoriginated transactions are not reconciled to a payment order. They can, however, be reconciled to Expected Payments, which you can also simulate in your sandbox.
Updated 3 months ago