Issue virtual and physical cards your customers order and control in web, iOS and Android apps. Your team manages programmes, limits and card status in the Back-Office Dashboard.
Configure issuing products, spending policies and customer controls before bringing them into your banking app.
Put your brand into daily spending, with virtual and physical card products and familiar in-app controls. Let customers see their card, understand their allowance and manage the controls you enable.
Choose the issuer, card type, supported currencies and eligible customer segment for each card product. Link the relevant price list and approved design configuration to define what customers can order.
Set the rules for the card experience delivered through web, iOS and Android apps. Combine spending allowances with available card controls, while keeping product defaults separate from actions on an individual issued card.
Create separate card products for private and business customers. Define eligibility, account links and fee rules for each programme, with physical-card delivery handled through the issuing integration.
Choose integrations that fit your programme, market and required capabilities.
Connect the switches in your app to real card settings. Update online payments, contactless payments and cash withdrawals through one documented request.
/api/clients/{clientId}/issued-cards/{id}/settings// Update card settings
const baseUrl = process.env.CRASSULA_BASE_URL;
const apiKey = process.env.CRASSULA_API_KEY;
const clientId = process.env.CRASSULA_CLIENT_ID;
const cardId = process.env.CRASSULA_CARD_ID;
const path = `/api/clients/${encodeURIComponent(clientId)}/issued-cards/${encodeURIComponent(cardId)}/settings`;
const response = await fetch(`${baseUrl}${path}`, {
method: 'PATCH',
headers: {
Authorization: apiKey,
'Content-Type': 'application/json',
},
body: JSON.stringify({
"onlinePayments": true,
"contactlessPayment": true,
"atmWithdrawal": false
}),
});
if (!response.ok) throw new Error(`HTTP ${response.status}`);
const data = await response.json();# Update card settings
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"]
card_id = os.environ["CRASSULA_CARD_ID"]
path = f'/api/clients/{quote(client_id, safe="")}/issued-cards/{quote(card_id, safe="")}/settings'
response = requests.patch(
f"{base_url}{path}",
headers={"Authorization": api_key},
json={
"onlinePayments": True,
"contactlessPayment": True,
"atmWithdrawal": False
},
timeout=30,
)
response.raise_for_status()
data = response.json()# Update card settings
curl --request PATCH \
"${CRASSULA_BASE_URL}/api/clients/${CRASSULA_CLIENT_ID}/issued-cards/${CRASSULA_CARD_ID}/settings" \
--header "Authorization: ${CRASSULA_API_KEY}" \
--header 'Content-Type: application/json' \
--data '{
"onlinePayments": true,
"contactlessPayment": true,
"atmWithdrawal": false
}'
Business accounts, virtual and physical debit cards, local payments and multi-currency services with web and mobile interfaces.
Read case study: Pay IO
Account details, SEPA payments, card issuing, KYC onboarding and multi-currency exchange in one financial product.
Read case study: LuxPayThe questions teams ask us before a first call.
Not covered here?Bring your question to a demo with our team.Create the relevant virtual and plastic products and configure their availability through the selected issuer. Product eligibility and issuer capabilities determine what customers can order.
Configure card artwork and issuer approvals as part of the issuing programme. Apply your application’s brand identity separately across web and mobile experiences.
Separate products can define company eligibility, account links, pricing and spending rules. Available controls depend on the issuing programme.
Explore card products, issuer integrations and the controls your app can offer.
Request demo