Issue Credit Cards with Configurable Limits

Credit limits are enforced at the authorization layer by Fyatu's platform. When a cardholder initiates a transaction, Fyatu checks the requested amount against the cardholder's available credit — the difference between their configured limit and current outstanding balance — and declines the transaction if it would result in an over-limit condition. Your platform can update credit limits dynamically via API at any time, and the change takes effect on the next authorization attempt.

Yes. Fyatu's credit card API supports configurable billing cycle parameters per card product — cycle length in days, statement cut-off date, payment due date offset, and grace period. For example, you can run a 28-day cycle product for consumer credit cards and a calendar-month cycle for corporate cards, both under the same API account. Billing cycle configuration is set at the card product level and applies uniformly to all cards issued under that product definition.

Yes. Every credit card issued via Fyatu includes native 3D Secure 2.0 support. The 3DS2 authentication flow — including risk-based step-up challenges and device fingerprinting — is handled at the Fyatu platform and card network level. Your engineering team does not need to integrate a separate Access Control Server (ACS) or 3DS SDK to achieve PSD2 SCA compliance for credit card online transactions.

Merchant Category Code controls let you define which merchant types a credit card can and cannot be used at. You configure MCC rules as either a whitelist (only permitted MCCs are approved) or a blacklist (all MCCs are approved except those explicitly blocked) at the card product or individual card level. For example, a corporate credit card can be configured to block MCCs covering gambling, peer-to-peer transfers, and cash advances — and any attempt to transact at those merchant types is declined at the card network before reaching your authorization webhook.

Yes. Fyatu generates structured statement data for each completed billing cycle, accessible via the Statement API as a JSON object containing itemized transactions, opening and closing balances, minimum payment due, payment due date, and interest charges. Your platform can render this data as an in-app statement view or pass it to a PDF generation service for branded PDF statements — Fyatu provides the data, you control the presentation.

Launching a credit card program requires completing Fyatu's standard KYB onboarding (3–5 business days), selecting a Visa or Mastercard BIN, defining your card product configuration (credit limit range, billing cycle, MCC rules, 3DS settings), and integrating the card issuance and webhook APIs. Because Fyatu operates under pre-approved BIN sponsorship, you do not need to negotiate directly with a card network or obtain a credit institution licence to issue cards — Fyatu's regulatory framework covers the card issuance layer.