> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/volume-themes/faq/cart-and-checkout/payment-icons-are-missing-grey-or-the-wrong-ones.md).

# Payment icons are missing, grey, or the wrong ones

Where Volume's payment icons come from, why you cannot pick them individually, and the two separate blocks that show them.

The icons are not a list you edit. Volume renders **whatever payment methods your store has actually enabled**, straight from Shopify — which is also what the block's own note in the Theme Editor says: *to add payment methods, go to your payment settings*.

That means:

* you cannot add an icon for a method you do not accept;
* you cannot remove a single icon while keeping the rest;
* if an icon is missing, the method is not enabled under **Settings → Payments**;
* if an unwanted icon appears, that method *is* enabled — turn it off in Shopify and the icon goes.

### Two separate blocks with the same name

Both are called **Payment methods**, they live in different sections, and changing one does nothing to the other.

The one in the **Product overview** section has **Black and white**, **Icon width** (38–64px, 38 by default), **Top spacing** and **Mobile top spacing**.

The one in the **Footer** section has **Heading**, **Center content**, **Desktop horizontal alignment**, **Desktop vertical alignment** and **Desktop padding** — but **no Black and white and no Icon width**. If you are hunting for the monochrome toggle in the footer, it is not there; that setting belongs to the product-page block only.

{% hint style="warning" %}
On the product page the block hides itself entirely when the store has no enabled payment types — you get no empty row and no placeholder, so a block that seems not to have been added at all may simply have nothing to show.
{% endhint %}

{% hint style="warning" %}
Icons that render grey or as plain outlines on a dark background are usually the brand SVGs themselves — several card networks ship monochrome marks. If the whole row looks washed out on the product page, check whether **Black and white** is ticked.
{% endhint %}

{% hint style="warning" %}
Test payment gateways and Shopify's bogus gateway do not produce icons. A development store with no real payment provider connected will show nothing.
{% endhint %}

{% hint style="success" icon="lightbulb" %}
See [Announcement Bar & Footer](/docs/volume-themes/navigation/announcement-bar-and-footer.md) for the rest of the footer blocks.
{% endhint %}


---

# 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://staylime.com/docs/volume-themes/faq/cart-and-checkout/payment-icons-are-missing-grey-or-the-wrong-ones.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.