La API permite a los desarrolladores validar y verificar la información de la tarjeta de crédito utilizando el Número de Identificación Bancaria (BIN). Al proporcionar los primeros seis dígitos de una tarjeta de crédito, la API puede detectar el banco emisor, la entidad emisora (por ejemplo, VISA, Mastercard), la ubicación de la tarjeta y si es una tarjeta de crédito válida o no.

La API sigue un enfoque seguro al requerir solo el Número de Identificación del Banco (BIN), que consiste en los primeros seis dígitos de una tarjeta de crédito. Este enfoque evita la necesidad de transmitir o almacenar detalles sensibles de la tarjeta de crédito.

La respuesta de la API incluye detalles completos sobre la tarjeta de crédito. Esto incluye información como la validez de la tarjeta (si es válida o no), el nombre del banco emisor, la marca de la tarjeta (por ejemplo, VISA), el tipo de tarjeta (por ejemplo, crédito), el nivel de la tarjeta (por ejemplo, compra con flota), la moneda asociada con la tarjeta y el país de emisión. Además, la respuesta proporciona información de contacto para el emisor, incluyendo su nombre, sitio web y número de teléfono.

Para acceder a la API, necesitas realizar una solicitud HTTP POST al endpoint de la API, proporcionando los primeros seis dígitos de la tarjeta de crédito (BIN) como parámetro. La API responderá con un objeto JSON que contiene la información solicitada sobre la tarjeta de crédito, incluyendo su validez, detalles del banco emisor y información de ubicación. Puedes integrar esta API en tu aplicación o sistema para aprovechar su funcionalidad y mejorar tus capacidades de procesamiento de tarjetas de crédito.

El chequeo POST por BIN y los endpoints GET Checker de BIN devuelven información detallada sobre una tarjeta de crédito basada en su BIN. Esto incluye la validez de la tarjeta, el banco emisor, la marca de la tarjeta (por ejemplo, VISA, Mastercard), el tipo de tarjeta (por ejemplo, crédito, débito) y el país emisor, entre otros detalles.

Los campos clave en la respuesta incluyen "válido" (que indica la validez de la tarjeta), "emisor" (el banco emisor), "marca de tarjeta" (por ejemplo, MASTERCARD), "tipo de tarjeta" (por ejemplo, DÉBITO) y "nombre del país ISO" (país de emisión). Estos campos ayudan a identificar la legitimidad y los detalles de la tarjeta.

Los datos de respuesta están estructurados en formato JSON, con un estado de nivel superior e indicador de éxito, seguidos de un objeto "data" que contiene detalles específicos sobre la tarjeta. Esta organización permite un fácil análisis e integración en aplicaciones.

Ambos puntos finales proporcionan información como la validez de la tarjeta, los detalles del banco emisor, el tipo de tarjeta, el nivel de la tarjeta, la marca de la tarjeta y el país de emisión. Estos datos ayudan a evaluar el riesgo de transacción y la elegibilidad para promociones.

Los datos provienen de instituciones financieras y redes de tarjetas, lo que garantiza una base de datos completa y confiable para la información de BIN. Las actualizaciones regulares y las asociaciones con bancos ayudan a mantener la precisión de los datos.

Los usuarios pueden personalizar las solicitudes proporcionando diferentes números BIN para recuperar detalles específicos de la tarjeta. Cada solicitud devolverá información relevante al BIN proporcionado, lo que permitirá realizar verificaciones de validación personalizadas.

Los casos de uso típicos incluyen validar transacciones de tarjetas de crédito durante pagos en línea, identificar bancos emisores para ofertas promocionales y prevenir transacciones fraudulentas verificando la legitimidad de la tarjeta.

Los usuarios pueden utilizar los datos devueltos para tomar decisiones informadas sobre las aprobaciones de transacciones, personalizar estrategias de marketing según los bancos emisores y mejorar las medidas de seguridad al identificar tarjetas potencialmente fraudulentas.

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). 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 paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

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.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

To see the maximum number of API requests your plan allows, check the 'X-Zyla-RateLimit-Limit' response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.

When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.

Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.