This page documents the KatFacil API surface for Digital MasterCards. Third-party providers stay hidden behind the platform, so integrators work only with KatFacil authentication, KatFacil endpoints, and KatFacil webhook delivery.
[]Clients authenticate only against KatFacil. The platform handles the provider communication internally and exposes a simpler Digital MasterCard API surface to apps and partners.
Every endpoint below is a KatFacil API route intended for authenticated client applications.
https://katfacil.com/api/user
https://katfacil.com/api/user/login
Use the bearer token returned by the KatFacil login endpoint. Provider secrets stay private on the server side.
{
"Authorization": "Bearer YOUR_ACCESS_TOKEN",
"Accept": "application/json"
}Use your own server webhook URL here. KatFacil sends business card events to the callback endpoint you configure from your business webhook settings.
https://your-domain.com/webhooks/katfacil
These are the KatFacil API routes available for issuing, listing, details, transactions, funding, wallet OTP, card controls, and 3DS approval for Digital MasterCard.
Returns the authenticated user digital Mastercard collection from KatFacil.
/api/user/digital-mastercards
[]Returns issue and funding charge rules used by KatFacil for Digital MasterCard.
/api/user/digital-mastercards/charges
[]Creates a Digital MasterCard through KatFacil after wallet balance and KYC checks.
/api/user/digital-mastercards/create
{
"firstname": "Jean",
"lastname": "Die",
"dob": "2002-03-13",
"address1": "59 Rue Sicot Prol",
"postalcode": "6110",
"city": "Port-au-Prince",
"country": "HT",
"state": "Ouest",
"countrycode": "+509",
"phone": "37000000"
}Returns one authenticated user card by KatFacil local card id.
/api/user/digital-mastercards/details/{id}
[]Returns remote Digital MasterCard transactions for one local card id.
/api/user/digital-mastercards/transactions/{id}
[]Funds a digital Mastercard using one authenticated user wallet.
/api/user/digital-mastercards/fund
{
"id": 12,
"amount": "50",
"fund_amount": "50",
"from_currency": "USD"
}Freezes one authenticated user Digital MasterCard.
/api/user/digital-mastercards/freeze/{id}
[]Unfreezes one authenticated user Digital MasterCard.
/api/user/digital-mastercards/unfreeze/{id}
[]Returns wallet activation OTP from KatFacil for Google Pay or Apple Pay.
/api/user/digital-mastercards/wallet-otp/{id}
[]Checks whether the authenticated user card has a pending 3DS verification.
/api/user/digital-mastercards/check-3ds/{id}
[]Approves a pending 3DS request with the eventId returned by KatFacil.
/api/user/digital-mastercards/approve-3ds/{id}
{
"eventId": "evn-34234-erte45-joor3663",
"event_id": "evn-34234-erte45-joor3663"
}KatFacil already stores and reacts to these provider events internally for Digital MasterCard lifecycle, OTP, 3DS, transaction and funding updates.
digitalcard.newcard
New card issued and deposit addresses returned.
digitalcard.cardauthorization
3DS authorization requested for merchant approval.
digitalcard.transaction
Transaction completed or declined.
digitalcard.blockchain
Blockchain settlement, deposit, refund, transfer or withdrawal activity.
digitalcard.xpayactivation
Google Pay or Apple Pay activation code sent for the card.
digitalcard.fundrequest
Funding request accepted and processing.
digitalcard.funded
Funding approved and card ready to use.
This implementation is currently focused on Digital MasterCard only. KatFacil creates the card, stores the local card record, receives provider webhook events in the background, exposes OTP and 3DS approval endpoints, and listens for funding request and funding approval updates.