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

# Payment methods

ipdunar accepts most major payment rails. Add one in **Billing → Payment methods → Add new**.

## What we accept

| Method                        | Notes                                                 |
| ----------------------------- | ----------------------------------------------------- |
| **Credit / debit card**       | Visa, Mastercard, American Express, Discover, JCB     |
| **Wire transfer (ACH/SWIFT)** | Pro+ plans; instructions on the invoice               |
| **PayPal**                    | All plans                                             |
| **USDT / USDC**               | TRC-20, ERC-20, BSC; manual confirmation up to 1 hour |
| **Alipay / WeChat Pay**       | For CNY billing accounts; coming via local PSP        |

## Adding a card

1. **Billing → Payment methods → Add card**.
2. Enter card details — handled by our PCI-DSS Level 1 PSP, ipdunar never sees the PAN.
3. The card is verified with a $1 hold that's released immediately.

## Default vs backup

You can store **multiple** payment methods. Mark one as **default** — that's the one charged for subscriptions and auto top-ups. Backups are used only if the default fails.

We recommend at least two on file: a primary card and a backup. A failed default during a renewal cascades into a `403 account-suspended` on the gateway if balance also runs out.

## Wire transfers

For Pro+ plans, wire instructions appear on each pending invoice:

```
Beneficiary:    ipdunar Inc.
Bank:           ...
Account:        ...
SWIFT/IBAN:     ...
Reference:      INV-2026-05-001234   ← MUST include this exact reference
```

Funds clear in 1–3 business days for ACH, 1–5 for international SWIFT. We email when received and apply to balance.

Wires for amounts >$10,000 typically include a small fee on your bank's side — factor that in.

## Cryptocurrency

USDT / USDC payments are processed via a self-service flow:

1. **Billing → Payment methods → Crypto top-up**.
2. Choose amount → choose chain (TRC-20 cheapest fees).
3. Send to the one-time address shown — **do not reuse**, the address changes per payment.
4. Balance is credited after 1–6 confirmations (typically <1 hour).

Refunds for crypto top-ups are paid back in the same currency, to the source address; allow 3 business days.

## Updating a card

If your card was reissued (same number, new expiry), the PSP usually auto-updates via card-network refresh. Otherwise:

**Payment methods → {card} → Update expiry / CVV** → re-verify with a $1 hold.

## Removing a payment method

Click the trash icon. You can't remove the **last** payment method if you have an active subscription — cancel the subscription first or add a replacement.

## Currency-method matching

Card networks settle in your card's native currency; we display the equivalent in your **default currency** (set in **Address & tax**). Cross-currency charges may incur a small bank FX fee.

For lowest cost: keep your billing currency aligned with your card's currency.

## API

```bash
# List
curl -H "Authorization: Bearer API_KEY" \
     https://api.ipdunar.com/v1/billing/payment-methods

# Set default
curl -X POST -H "Authorization: Bearer API_KEY" \
     -d '{"payment_method_id":"pm_01HX..."}' \
     https://api.ipdunar.com/v1/billing/default-payment-method
```

Cards can't be added via API for PCI-DSS reasons — that flow has to go through the hosted dashboard form.

## Common pitfalls

* **Card auto-renewal failure** — most often an expired card. Set a **calendar reminder** for your card's expiry month.
* **Wire without reference** — without the invoice reference in the wire memo, our reconciliation team has to manually match — expect 1–3 days extra to credit.
* **Wrong chain for crypto** — sending USDT-ERC20 to a TRC20 address loses the funds. Double-check the chain before sending.


---

# 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.ipdunar.com/account-and-billing/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.
