Payments and collections

Pulse — payments and collections

Pulse runs payments and collections, then posts the result into Titan. It is not a second ledger.

For your technology team. Pulse runs payments and collections and sends them to the core for posting. It manages each payment along its rail (the network that carries it); it is not a second ledger. The final settled record stays with Titan, or with the posting system the institution names.

What it does

  • Starts a payment or a collection from a channel or from operations.
  • Tracks that payment until it is posted.
  • Routes bills payment and QR payments into the same posting path.
  • Coordinates settlement with the core.
  • Hands the money result to Titan. Pulse is not a second ledger.
  • Asks Sentinel to check risk when the institution has that check turned on.
  • Asks Aegis and Atlas before a sensitive money change.

Who uses it

Payments operations, and the channels that start a payment for a customer.

Detail for your technology team

  • Runs payments and collections and sends them to the core for posting
  • Handles each payment’s steps along its rail
  • Works with Aegis and Atlas on controlled money paths

How it connects

Pulse CONNECTS TO Titan Posting Channels Payment requests from Nova and Summit Aegis / Atlas Sign-in and permissions (in production, money paths have no separate local sign-in) Ceres Optional, for collections Sentinel Sends risk events, where set up
Connections named on this page, with the platform marks. The diagram does not show balances or a live screen.
  • TitanPosting
  • ChannelsPayment requests from Nova and Summit
  • Aegis / AtlasSign-in and permissions (in production, money paths have no separate local sign-in)
  • CeresOptional, for collections
  • SentinelSends risk events, where set up

What it is not

A second general ledger; the system of record for card issuing (Vulcan); the system of record for remittance payouts (Wayfarer).