Fintech Core Modulr logo

Modulr Integration for Fintech Core

Bring Modulr accounts and payments into your product through Fintech Core by DashDevs. The Modulr banking adapter already exists, so your project starts from configuration, with cards shaped to your scope.

Book a Modulr integration demo

Why Fintech Core + Modulr

Modulr provides the accounts and payments. Fintech Core connects them to your product.

Fintech Core by DashDevs is a composable fintech infrastructure and orchestration platform. Its Banking module already includes a dedicated Modulr adapter, so your product talks to one Banking API while Fintech Core handles the Modulr connection behind it.

  • Start from an existing connection

    Fintech Core has a dedicated Modulr banking adapter and gRPC package. A new project starts from integration and configuration work, so your budget goes into your programme instead of a connector built from scratch.

  • Funding and payments inside your product

    Customers see account details, incoming funds and outgoing payments where they already use your product. Your back office gets the same activity in its own views, so support and finance work from one set of records.

  • Shaped around your Modulr programme

    Account structures, payment rails and card products follow the Modulr setup you contract for. We confirm the integration scope with you during discovery and configure Fintech Core to match, with card issuing treated as its own scope.

  • Keep your own Modulr contract

    Your agreement, credentials and enabled products stay with you and Modulr. Fintech Core connects to the setup you already hold, and you decide when to move from the Modulr sandbox to production.

What's ready out of the box

Four connection parts you don't have to build.

  • Dedicated Modulr adapter

    A Fintech Core adapter built specifically for Modulr, covering account, payment and banking operations within the Banking module of Fintech Core.

  • gRPC service package

    A packaged service interface that the Banking module uses to communicate with the Modulr adapter, so your team does not write this layer.

  • One Banking API

    Your product calls the same Banking module API it would use with any other banking provider connected to Fintech Core.

  • Room for more providers

    Moving between banking providers, or adding a second one next to Modulr, does not require rewriting the banking calls in your product.

How a payment runs

From the first request in your product to the updated record your team sees.

  1. 1 Start

    Your product starts the customer and account workflow configured for your programme, after your own onboarding and eligibility checks.

  2. 2 Request

    Fintech Core sends the supported request to Modulr through the Banking module and its dedicated Modulr adapter.

  3. 3 Provider response

    Modulr responds, and the customer receives account information and funding instructions once Modulr makes them available.

  4. 4 Activity

    Incoming funds and outgoing payments create activity at Modulr, reported through notifications that may arrive after the request.

  5. 5 Update

    Fintech Core records the statuses and references confirmed for your scope against the customer and the account.

  6. 6 Review

    Your back office reviews transaction history and reconciliation information. Card flows are added only within the validated scope.

What lands on the account record

Payment statuses from Modulr, plus the account and payment data your scope confirms.

Payment status

Status Meaning
SUBMITTED
Modulr has accepted the request and will run internal validation.
VALIDATED
The request passed validation and is queued for the external payment system.
PENDING_FOR_DATE
The request is waiting for its scheduled processing date to arrive.
PENDING_FOR_FUNDS
The request is waiting for enough funds in the paying account.
PROCESSED
The payment was processed and sent to the destination payment system.
CANCELLED
The payment request was cancelled and will not be sent onwards.
ER_INVALID
The request failed validation, for example no funds or an inactive account.

Some Modulr error codes, such as an expired request, send no webhook. Fintech Core records later status changes as Modulr reports them.

Data

  • Accounts

    Identifiers that link your customer to the account opened at Modulr, with the details customers need to receive money.

    • Customer and account references
    • Account details and funding instructions
    • Currency and balance

  • Payments

    Payment references, amounts and the current payment state, with timestamps showing when each Modulr notification arrived, so later changes stay visible.

  • Cards

    Where cards are in scope, the record holds card identifiers and status only. Fintech Core does not store full card numbers, CVV or PIN.

What stays under your control

Fintech Core handles the integration. Your programme decisions and your Modulr setup stay with you.

  • Modulr agreement

    Your contract, credentials and the products Modulr enables for you, including when you test in the sandbox and go live.

  • Customers and onboarding

    Which customers and businesses your programme serves, and the onboarding checks that run before an account is requested.

  • Accounts and rails

    The currencies and payment rails enabled on your Modulr setup, and how accounts are organised for customers and operations.

  • Payment approvals

    Which payments need approval and who gives it, plus which events your customers and your team are told about.

  • Card programme

    Card products, schemes and controls, where card issuing is part of your agreed integration scope with Modulr.

Ready to connect Modulr to your product?

Tell us about your licence setup, target markets, customer types and required workflows. We'll walk through the Modulr integration and the configuration your product needs.

Book a Modulr integration demo

No commitment. Already working with Modulr? We'll show you how to reuse your current setup.