Expected Payment Sandbox Reconciliation
Expected Payment behavior based on Internal Account and Connection types in sandbox
Expected Payments can be used to automatically reconcile and account for incoming, unoriginated payments. Combined with their Expected Payment Webhooks, they enable you to automate workflows around incoming payments. In some cases, you may want to test Expected Payment reconciliation in your sandbox.
Sandbox Banks
Modern Treasury sandboxes are pre-populated with two banks whose default names are "Iron Bank of Braavos (IBB)" and "Gringotts Wizarding Bank (GWB)." Depending on the bank associated to the Expected Payment (via the Internal Account), the sandbox behavior will vary.
Expected Payment reconciliation workflows will typically leverage the Iron Bank of Braavos (IBB) bank.
While there are exceptions to this guidance, Expected Payment reconciliation will typically use an Iron Bank of Braavos (IBB) Internal Account, and Payment Order testing will use a Gringotts Wizarding Bank (GWB) Internal Account.
Iron Bank of Braavos (IBB) behavior for Expected Payments
Expected Payments created with an Internal Account associated to an Iron Bank of Braavos (IBB) Connection will only reconcile when you create a Transaction that reconciles based on the defined Reconciliation Rules.
Gringotts Wizard Bank (GWB) behavior for Expected Payments
A matching Transaction will automatically be created for any Expected Payment created with an Internal Account associated to a Gingotts Wizarding Bank (GWB) Connection. This Transaction will be automatically reconciled to the Expected Payment.
Updated 2 months ago