Card Guardian API

Card Guardian API

With Card Guardian API securely hide credit card numbers with ease. Protect user privacy and ensure secure transactions. Simplify compliance and improve data security.

API description

About the API:  

The API is a state-of-the-art solution designed to enhance credit card data security and protect sensitive information from unauthorized access. Thanks to its advanced features and robust functionality, this API offers developers a reliable and efficient way to hide credit card characters.

One of the main functions of the API is to mask credit card numbers by hiding certain characters. This process is crucial to prevent unauthorized people from seeing or obtaining sensitive information. By integrating this API into their applications, developers can ensure that credit card numbers are only displayed to authorized users in a secure manner. The API replaces certain digits of the credit card number with x, maintaining the overall structure of the card and making it unreadable to unauthorized eyes.

Card Guardian API is a powerful tool that enables companies and organizations to enhance their security measures. With a comprehensive set of features, this API enables seamless integration of safety number cards into various applications and systems.

Data security is a key concern for any application that handles credit card information. The Card Guardian API addresses this concern by implementing robust security measures. It employs encryption algorithms and follows best practices to ensure data confidentiality and integrity.

In addition, the Card Guardian API is designed for high performance and scalability. It can efficiently handle API calls to process credit card data in real time, making it suitable for applications that process numerous transactions simultaneously. Whether used in e-commerce platforms, payment gateways or financial applications, the API integrates seamlessly into existing infrastructure, ensuring smooth and efficient operation.


What this API receives and what your API provides (input/output)?

It will receive parameters and provide you with a JSON.


What are the most common uses cases of this API?

  1. Payment processing: Payment processors can use an API that hides credit card numbers to securely manage credit card transactions. The API can modify the credit card information, replacing the actual card numbers with X, ensuring that sensitive information is protected during the payment process.


  2. E-commerce platforms: E-commerce platforms can leverage the API to protect credit card information provided by customers. By hiding the actual card numbers, the API helps protect sensitive data, reducing the risk of data leakage and unauthorized access to customer payment details.


  3. Subscription services: Subscription-based businesses can use the API to securely store and manage credit card information for recurring payments. By hiding credit card numbers, the API adds an additional layer of security, preventing unauthorized access to sensitive customer data.


  4. Mobile wallets: Mobile wallet applications can integrate the API to safeguard credit card information stored on users' devices. By hiding the actual card numbers, the API ensures that sensitive data remains protected, even if the device is lost or stolen.


  5. Hotel and travel booking platforms: Travel and accommodation platforms can use the API to protect credit card data provided by customers for bookings. By hiding credit card numbers, the API helps maintain customer trust and protects against fraudulent activity.


Are there any limitations to your plans?

  • Free Plan: 1 API Calls.

  • Basic Plan: 4,300 API Calls. 10 request per minute.

  • Pro Plan: 10,000 API Calls. 20 request per minute.

  • Pro Plus Plan: 200,000 API Calls.

  • Premium Plan: 600,000 API Calls.

API Documentation


To use this endpoint simply enter a card number with text. Example: My credit card 4237324723472, you must also indicate by default sensitive in the models parameter.


Security Card - Endpoint Features
Object Description
text [Required]
models [Required]
Test Endpoint


                                                                                                                                                                                                                            {"_call_id":"ENV8RiKJ4N","call_response":{"models_applied":["Sensitive"],"input":{"text":"My credit card is 38383837"},"result":{"clean":"My credit card is 38383837","additional":{}},"input_hash":"6bda0a77bce1342c7c90d5530190d3af51136db5"},"_api_name":"cleanText","_api_version":"0.0.1","_call_time":"2023-05-31T18:29:47.958Z"}

Security Card - CODE SNIPPETS

curl --location --request GET ' card num 5555555555554444&models=Sensitive' --header 'Authorization: Bearer YOUR_API_KEY' 


API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Card Guardian API REST API, simply include your bearer token in the Authorization header.


Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.

🚀 Enterprise
Starts at $10,000/Year

  • Custom Volume
  • Dedicated account manager
  • Service-level agreement (SLA)

Customer favorite features

  • ✔︎ Only Pay for Successful Requests
  • ✔︎ Free 7-Day Trial
  • ✔︎ Multi-Language Support
  • ✔︎ One API Key, All APIs.
  • ✔︎ Intuitive Dashboard
  • ✔︎ Comprehensive Error Handling
  • ✔︎ Developer-Friendly Docs
  • ✔︎ Postman Integration
  • ✔︎ Secure HTTPS Connections
  • ✔︎ Reliable Uptime

Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.

Prices are listed in USD. We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble with paying by card, just contact us at [email protected]

Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further

Prices are based on a recurring monthly subscription depending on the plan selected — plus overage fees applied when a developer exceeds a plan’s quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.

Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.

You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]

 Service Level
 Response Time



Related APIs