> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/references/references/credit-card-payments.md).
# Credit card payments (Administrator)
Credit cards are the payment method for your eMarketeer subscription.
eMarketeer bills in arrears, so your subscription is charged at the end of each month of use. You register a credit card on the account, and eMarketeer captures the amount owed at the end of each month for as long as the subscription runs. When you cancel the subscription or register a different card, the old card is removed from the system.
### Does eMarketeer store my credit card information on its servers?
No. eMarketeer uses a secure, trusted vendor for all credit card information and transactions: .
Your card is stored in DIBS' secure, certified system. eMarketeer only receives a reference to the card so it can capture your subscription payment. eMarketeer never has access to your card number and cannot use it for anything else.
### What happens when I register a card?
When you enter card details, you are no longer on the eMarketeer server. All card information is captured on the DIBS secure server and is not revealed to eMarketeer. DIBS checks the card for validity, and after a successful registration eMarketeer receives:
* Masked card number, with only the last 4 digits visible
* Expiry date
* Card type
* A reference ID that allows eMarketeer to capture funds from your card
eMarketeer stores no information that could be used in fraudulent activity by us or anyone else.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://support.emarketeer.com/references/references/credit-card-payments.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.