> For the complete documentation index, see [llms.txt](https://anticode.gitbook.io/templates/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://anticode.gitbook.io/templates/plugins/bubble-credit-card-validator-plugin.md).

# Bubble - Credit Card Validator Plugin

### Overview

This is a simple Plugin that allows you to check the validity, card type and length validity of a credit card number that is entered by an user into an input field.

For a demo please visit: <https://creditcardvalidator.bubbleapps.io/>

### Instructions

Simply drag the Card Validator element to your page and go to settings->general and tick the box to add an ID attribute to HTML elements. Drag an input onto your page and enter an ID attribute of your choice. Enter the same ID attribute into the "input\_id" field of the Card Validator element. You should have access to the card validity, card type and length validity by using the exposed states of the Card Validator element. For example: CardValidator's A Card Type.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://anticode.gitbook.io/templates/plugins/bubble-credit-card-validator-plugin.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.