Bringing fiat and digital assets together.
Fiat and crypto payments, multi-currency exchange and digital-asset accounts on Crassula infrastructure.
Read case studyCrassula's Decision-Making System offers a comprehensive solution designed to streamline client verification and account opening processes in financial services. This advanced system integrates client scoring, transaction monitoring, and profile screening, providing a robust and efficient approach to client verification. Enhance your customer onboarding with 3-party integration.
Define how identity verification, questionnaires and risk scoring inform your onboarding policy.
Create customer profiles and share the relevant applicant information with the verification provider. Combine identity checks and questionnaire information with risk-scoring inputs before the fintech makes its onboarding decision.
Make onboarding feel like the beginning of your banking relationship. Show customers where they are in the journey, while your fintech stays in control of verification, review and account opening.

Define custom client tags and the rules that apply to each segment. Use provider-side workflows to route additional checks and reviews where your onboarding policy requires them.
Use verification and scoring results in the back office to make the final onboarding decision. Set account provisioning to follow the approval policy defined for your business.
Bring the relevant verification and risk information into your onboarding process.
Use the account status returned by the Banking API to reflect where an account stands. Keep your customer journey aligned with the opening and approval process configured for your fintech.
/api/clients/{clientId}/accounts/{accountId}// Retrieve the account status
const baseUrl = process.env.CRASSULA_BASE_URL;
const apiKey = process.env.CRASSULA_API_KEY;
const clientId = process.env.CRASSULA_CLIENT_ID;
const accountId = process.env.CRASSULA_ACCOUNT_ID;
const path = `/api/clients/${encodeURIComponent(clientId)}/accounts/${encodeURIComponent(accountId)}`;
const response = await fetch(`${baseUrl}${path}`, {
method: 'GET',
headers: {
Authorization: apiKey,
},
});
if (!response.ok) throw new Error(`HTTP ${response.status}`);
const data = await response.json();
# Retrieve the account status
import os
from urllib.parse import quote
import requests
base_url = os.environ["CRASSULA_BASE_URL"]
api_key = os.environ["CRASSULA_API_KEY"]
client_id = os.environ["CRASSULA_CLIENT_ID"]
account_id = os.environ["CRASSULA_ACCOUNT_ID"]
path = f'/api/clients/{quote(client_id, safe="")}/accounts/{quote(account_id, safe="")}'
response = requests.get(
f"{base_url}{path}",
headers={"Authorization": api_key},
timeout=30,
)
response.raise_for_status()
data = response.json()
# Retrieve the account status
curl --request GET \
"${CRASSULA_BASE_URL}/api/clients/${CRASSULA_CLIENT_ID}/accounts/${CRASSULA_ACCOUNT_ID}" \
--header "Authorization: ${CRASSULA_API_KEY}"
Fiat and crypto payments, multi-currency exchange and digital-asset accounts on Crassula infrastructure.
Read case studyAccount details, SEPA payments, card issuing, KYC onboarding and multi-currency exchange in one financial product.
Read case studyThe fintech uses the verification and risk information to make its final decision in line with its own policy. A successful provider check is an input to that process.
Custom tags and configured provider workflows can support different checks for different customer segments. Define these requirements for the product and the customer segment.
No. Verification, risk review, the onboarding decision and account provisioning are separate stages. The customer experience should reflect the stage actually reached.
Explore identity integrations, risk inputs and the account-opening policy behind your customer journey.
Request demo