Core banking and payment hubs
Your backend checks the decision server to server before a payment reaches the core banking system or the rail, so a hold means the money never left.
On this page
Before the payment posts
A hold only works if nothing has been sent. Your app calls DeepID before the payment is initiated, and when the decision is a hold, the app shows the customer’s message and your backend sends nothing on to the core banking system or the rail.
For login, DeepID issues a single-use token that your server redeems server to server before anyone is signed in, so the app never decides alone.
Which systems
DeepID does not post to your core banking system; your backend does, as it does today. How the decision is checked in your payment flow is agreed with your team, and no core banking product is named here until an integration is signed.
What it sends
payment.initiate: called before the payment is sent, returns the decisionToken redemption: your server redeems the login token before anyone is signed in
Set-up
- Call before the action takes effect
Before the payment is sent, the payee saved or the session opened.
- Act on the decision in your backend
A hold or a block means nothing goes to the core or the rail.
- Keep the decision id with the payment
So a complaint or an audit can follow one id end to end.