Skip to content

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.

Core banking and paymentsServer-to-server decision check

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 decision
  • Token redemption: your server redeems the login token before anyone is signed in

Set-up

  1. Call before the action takes effect

    Before the payment is sent, the payee saved or the session opened.

  2. Act on the decision in your backend

    A hold or a block means nothing goes to the core or the rail.

  3. Keep the decision id with the payment

    So a complaint or an audit can follow one id end to end.

The decision object

More integrations.

How each decision reaches the systems your teams already use.

  • Webhooks

    Every decision as an event to an endpoint you run: the same id, the same reason codes and the same queue the app received, for your FRM, case manager or SIEM.

    Webhooks and eventsEvents to your endpoint

  • Your FRM system

    DeepID’s decisions reach your fraud risk management system as events, with the session signals it never sees today. Your FRM keeps its rules, queues and cases.

    FRM systemsDecision events into your FRM

See DeepID on a real phone.

We show your fraud, security and engineering leads how DeepID would run your sign-up, login or payment journey, then plan a pilot on your own traffic.