> For the complete documentation index, see [llms.txt](https://docs.publicit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.publicit.com/advertiser/billing-and-finance/payment-methods.md).

# Payment methods

Publicit processes all campaign payments securely through Stripe, one of the world's leading payment infrastructure providers.

***

## Accepted payment methods

Publicit currently accepts **credit and debit cards**:

* Visa
* Mastercard
* American Express

{% hint style="info" %}
Card data is handled entirely by Stripe. Publicit never stores your card number on our servers. All transactions are PCI-DSS compliant.
{% endhint %}

***

## Adding a payment method

1. Go to **Dashboard → Payments**.
2. Click **Add Payment Method**.
3. Enter your card number, expiry date, and security code.
4. Click **Save**.

Your card is securely stored and available for future campaigns.

***

## Managing multiple cards

You can save multiple cards to your account. This is useful if you have different cards for different projects or clients.

| Action           | How                                                    |
| ---------------- | ------------------------------------------------------ |
| Set default card | Click the menu (⋯) next to a card → **Set as default** |
| Remove a card    | Click the menu (⋯) next to a card → **Delete**         |
| View saved cards | **Dashboard → Payments → Payment Methods**             |

The default card is charged automatically when you submit a campaign.

***

## When your card is charged

Payment is taken at the point of campaign submission — **before** publisher approval. This confirms your intent to run the campaign and releases the inventory for the publisher's review.

If a publisher rejects your campaign after payment, see [How campaign payments work](/advertiser/billing-and-finance/adding-funds.md) for what happens to your payment.

***

## Card security

Publicit uses Stripe's SetupIntent flow for saving cards. This means:

* Your card is verified at the time of saving without charging it
* Subsequent charges use the tokenised reference — not your actual card details
* You can revoke access at any time by removing the card from your account


---

# 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://docs.publicit.com/advertiser/billing-and-finance/payment-methods.md?ask=<question>&goal=<user_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.