---
title: "tell. integration | Crassula"
description: "tell.: Managed open banking and payee account verification."
url: "https://crassula.io/connectors/app/tell/"
lang: "en"
alternates:
  "en": "https://crassula.io/connectors/app/tell/"
  "de": "https://crassula.io/de/connectors/app/tell/"
  "es": "https://crassula.io/es/connectors/app/tell/"
  "fr": "https://crassula.io/fr/connectors/app/tell/"
  "x-default": "https://crassula.io/connectors/app/tell/"
index: "https://crassula.io/llms.txt"
---

# tell.

Managed open banking and payee account verification.

- ##### Modules

  ###### [Transfers](https://crassula.io/features/transfers/)

## About tell.

tell.money provides managed open banking interfaces and account-verification services. Its products include Confirmation of Payee and Verification of Payee capabilities for checking account details before a payment. The Crassula connector is relevant to account providers building open banking and payee-checking workflows. A name-match result supports a payment decision; it does not replace customer identity verification or guarantee that a payment is fraud-free.

## Designing the verification journey

A verification workflow needs to connect the customer’s request with the checks appropriate to the product. Depending on the provider service, the information may concern an individual, a business or a payment account. Crassula provides the surrounding customer and operational context for the verification functions enabled in the project.

- Define when a check is requested and what information it requires.
- Map results to a clear customer status and review action.
- Plan corrections, incomplete submissions and manual follow-up.

The practical aim is a journey that is understandable to both the applicant and the operating team. Customers need to know what is required and how to continue. Reviewers need sufficient context to interpret a result, resolve an exception and record the decision reached under the business’s own policies.

## Working with the connector

Crassula provides the software layer for organising customer journeys and operational processes around the connected service. A team can bring the functions included in its implementation into a branded product, while retaining a common place to review customer information, service requests and the resulting operational records. The provider continues to deliver its part of the service under the relevant agreement.

A useful starting point is to map the customer journey from the initial request to its final outcome. Define which information is submitted, what response is expected, which status is shown to the customer and how an operator handles an exception. This makes it easier to design a clear experience and to identify where automated processing or human review is appropriate.

## Planning your implementation

Agree the required functions with Crassula and the provider, then test the complete journey in the available test environment. Include successful requests, incomplete data, unsuccessful responses and recovery after an interruption. Establish responsibility for customer support, operational follow-up and changes to the provider service. The connector can then become part of a documented product workflow, with clear expectations for customers and the team operating it.

## Provider and connector overview

The gallery gives a provider-specific visual overview. Official imagery is included where available, alongside a simplified explanatory diagram of the connector’s role in a Crassula product.

![tell. screen 1](https://storage.googleapis.com/crassula/marketplace/app/screen/55-product-dark-v2.webp)

![tell. screen 2](https://storage.googleapis.com/crassula/marketplace/app/screen/55-provider-dark-v2.webp)

## Create a digital bank in a matter of days

[Request demo](https://crassula.io/request-demo/)

![Companies using Crassula](https://crassula.io/static/images/home/cta/logos.png)

**150+**
companies already with us