# Manage your stablecoin-backed card program

Use Issuing card features, generate statements, handle complaints, and support cardholders in a stablecoin-backed card program.

Manage your stablecoin-backed card program by providing cardholder support, generating monthly statements, and handling complaints. Use the Stripe and Bridge dashboards to monitor your program, and the Issuing guides to configure card features.

## Card features

Use the Issuing guides to set up each feature:

- [Physical cards](https://docs.stripe.com/issuing/cards/physical.md)
- [Digital wallets](https://docs.stripe.com/issuing/cards/digital-wallets.md)
- [Spending controls](https://docs.stripe.com/issuing/controls/spending-controls.md)
- [Spending restrictions and limits](https://docs.stripe.com/issuing/stablecoin-cards/spending-restrictions.md)
- [Disputes](https://docs.stripe.com/issuing/purchases/disputes.md)
- [Fraud management](https://docs.stripe.com/issuing/manage-fraud.md)

## Statements

Card network rules require you to provide cardholders with statements at least monthly. Generate statements with the Bridge API, which creates a PDF for a card and month. Statements aren’t available in the Stripe Dashboard.

Pass the Stripe cardholder ID, the Stripe card ID, and the statement period in `YYYYMM` format:

```shell
curl -X POST "https://api.bridge.xyz/v0/cardholders/{{CARDHOLDER_ID}}/cards/{{CARD_ID}}/statements/202603.pdf" \
  -H "Api-Key: {{BRIDGE_API_KEY}}" \
  -H "Accept: application/pdf"
```

See the Bridge [statements guide](https://apidocs.bridge.xyz/platform/cards/additional/statements) for details.

## Complaints 

You must give cardholders a clear way to submit complaints, and you’re responsible for resolving them. Follow the [complaint handling requirements](https://docs.stripe.com/treasury/connect/handle-complaints.md) for Issuing, which define complaint types and their acknowledgement and resolution times.

For stablecoin-backed card programs, report all complaints you received to Stripe each month, before the fifth calendar day of the following month. Stripe provides a secure form for these reports during onboarding.

## Dashboards

Use the Stripe Dashboard and the Bridge Dashboard for different parts of your program:

- **Stripe Dashboard**: View cards, cardholders, authorizations, and transactions. Manage disputes, spending controls, and fraud settings.
- **Bridge Dashboard**: In the [Customers section](https://dashboard.bridge.xyz/), review each customer’s verification status and `cards` endorsement. The customer page shows missing information, and shows cards access as `Pending` when the customer needs to confirm their information again. Bridge doesn’t offer a sandbox Dashboard, so use the Bridge sandbox API to check customers while you test.

## Cardholder support 

Your cardholder support must meet the servicing requirements and timeframes that apply in each market, such as Regulation E and Regulation Z in the US. Make sure your support team can handle common requests:

- Card actions, such as freezing, reporting a lost or stolen card, and closing an account.
- Balance and transaction history inquiries.
- [Disputes](https://docs.stripe.com/issuing/purchases/disputes.md) and charge errors.
- [Complaints](https://docs.stripe.com/issuing/stablecoin-cards/manage.md#complaints) and sensitive escalations.
- Digital wallet issues, such as one-time passcode verification and adding a card to a wallet.

Card network rules require you to provide phone support to cardholders of consumer programs. Phone support is optional for commercial programs. With [Managed Support](https://docs.stripe.com/managed-support.md), Stripe support agents handle cardholder inquiries on your behalf in English or Spanish, under a generic greeting or one that matches your brand.

For help with your integration, contact [Stripe support](https://support.stripe.com/contact).