# Managed Support programs

Review program-specific support coverage, authentication, and integration requirements.

Managed Support workflows and integration requirements vary by consumer program. The following sections describe how Managed Support applies to each program.

## Authentication factors 

Your product determines which identifiers customers must provide during phone authentication. Keep required identifiers visible in your application.

| Program | Identification factors and customer-facing requirements |
| --- | --- |
| Consumer credit and debit cards | Display the card’s last four digits. Confirm the customer’s phone, date of birth, postal code, and email verification flow during onboarding. |
| Stablecoin-backed cards | Display the card’s last four digits. The phone flow uses the calling phone number and card’s last four digits, with date of birth and postal code as fallback factors. |
| Treasury consumer wallets | Display the account’s last four digits with the wallet support number. The dedicated number identifies the platform, and the phone flow uses the caller’s phone number, date of birth, and agent email confirmation. |

Displaying an identifier doesn’t replace the [required authentication checks](https://docs.stripe.com/managed-support/set-up.md#authentication), including additional verification and multi-factor authentication for higher-risk actions. Agents can’t bypass these checks.

## Consumer credit and debit cards 

Managed Support provides branded, full-service support to Issuing credit cardholders. Stripe requires regulated support for Issuing debit cardholders and recommends full-service support.

Branded programs use a dedicated phone number and program-specific training, communications, and operating procedures. You must meet the [branded eligibility threshold](https://docs.stripe.com/managed-support.md#choose-a-support-model) and complete the [branded setup requirements](https://docs.stripe.com/managed-support/set-up.md#agent-preparation).

### Credit workflows

In addition to shared card servicing, the agreed credit scope can include the following workflows. Confirm which actions and approval rules apply before publishing them to cardholders.

| Workflow | Support scope |
| --- | --- |
| Payments and autopay | Help cardholders pay their balance and configure minimum-payment or full-balance autopay, including the agreed phone payment process. |
| Account information | Explain balances, due dates, payment history, statements, fees, interest, account status, authorized users, and dispute status. |
| Account operations | Support approved contact information changes, authorized-user removal, account closure, and card freezing or unfreezing. |
| Applications and identity verification | Explain application status and troubleshoot identity verification. Clearing credit fraud alerts is a separately scoped service. |
| Fees and credits | Handle requests to waive or credit eligible charges under approved program policies. Requests requiring your authorization follow the agreed escalation path. |
| Credit servicing | Explain loan or delinquency status and route credit-limit requests according to program policy. Don’t assume agents can approve a credit-limit increase. |
| Collections | Help with payments on accounts in collections and provide information about the collections provider. |
| Credit counseling | Provide information about independent credit counseling providers. |
| Bankruptcy, hardship, and bereavement | Take in reports and follow approved procedures, including documentation and escalation for a deceased cardholder’s account. |
| Other cardholder requests | Handle eligible emergency cash and data deletion requests through approved procedures. |

Credit billing errors and complaints follow the applicable consumer credit requirements. Don’t apply debit Regulation E procedures to credit disputes without confirming the correct program process with Stripe.

### Debit workflows

The scope for debit programs includes all the workflows listed for credit, plus support for:

- ATM withdrawal
- Supported network questions
- PIN setup or reset where applicable

Shared card support includes activation, lost or stolen cards, replacement, declines, and fraud challenges. Eligible unauthorized transactions and error notices follow the consumer debit dispute process, including Regulation E where applicable.

### Integrations and handoffs 

Follow the shared [authentication and data requirements](https://docs.stripe.com/managed-support/set-up.md#authentication) and [card dispute intake requirements](https://docs.stripe.com/managed-support/set-up.md#regulated-workflows). If your debit program includes a wallet, also display `account_last4`.

For an existing credit program migrating to Stripe, complete the bank-account validation risk assessment agreed upon with Stripe if agents take payments over the phone.

Your team handles rewards, promotions, platform policies, and unrelated products unless explicitly included in the approved scope. Agents follow your approved handoff process for decisions that require platform authorization or systems.

## Stablecoin-backed cards 

All stablecoin-backed card programs require Managed Support. The default is unbranded, full-service support. If you retain an existing support operation, you can agree on regulated-only coverage with Stripe. [Eligible](https://docs.stripe.com/managed-support.md#choose-a-support-model) programs can request branded support.

Unbranded programs share product-line phone numbers instead of receiving a dedicated platform number. Stripe provides the approved US and international support numbers for your program. Standard cards and statements include the support number. Also display the approved number in your card interface and help content.

### Stablecoin workflows

Full-service coverage includes the [shared card workflows](https://docs.stripe.com/managed-support.md#support-workflows-and-optional-services), excluding platform-specific rewards, promotions, or services that require your internal tooling.

Stripe applies consumer financial product support standards to the regulated workflows in these programs. Stripe must handle eligible unauthorized transactions, transaction-record errors, and regulatory complaints through the agreed upon process. Stripe money transmission obligations can also apply. Don’t assume that a stablecoin-backed program removes consumer protection or complaint-handling requirements.

For regulated-only coverage, your team retains other card servicing and platform questions. Merchandise or shipping issues don’t by themselves establish an unauthorized transaction. Route potentially regulated disputes and complaints to Stripe instead of deciding eligibility based entirely on the customer’s wording.

### Integrations and handoffs 

Use the [stablecoin-backed card authentication factors](https://docs.stripe.com/managed-support/programs.md#authentication-factors) and shared [card dispute intake requirements](https://docs.stripe.com/managed-support/set-up.md#regulated-workflows). Agree on the division of responsibilities for any platform-owned wallet, ledger, or money movement before launch. Card support doesn’t automatically cover every service connected to the wallet.

## Treasury consumer wallets 

For [consumer wallets for marketplaces](https://docs.stripe.com/treasury/connect/examples/closed-loop-respend-wallet.md), the default model is unbranded support for regulated disputes, errors, and complaints, not complete wallet servicing. Your team can retain other wallet inquiries and marketplace support. [Eligible](https://docs.stripe.com/managed-support.md#choose-a-support-model) programs can request branded support.

Stripe assigns a dedicated platform phone number. Standard communications use a generic consumer wallet support identity instead of your brand.

### Regulated scope and routing examples

Route potentially regulated wallet issues to Stripe for intake and investigation. The following examples distinguish wallet financial activity from marketplace or general service questions:

| Customer report | Route |
| --- | --- |
| Money left the consumer wallet without permission, including an account takeover. | Stripe dispute intake. |
| A wallet transaction amount is incorrect, or an eligible transaction is missing from a statement or transaction history. | Stripe notice-of-error or dispute intake. |
| A receipt or periodic statement is missing. | Stripe complaint intake. |
| A customer alleges the wallet dispute process violated their rights or threatens to contact a regulator. | Stripe complaint intake. |
| A customer requests a copy of an existing receipt or statement. | Your team, unless additional servicing is part of the agreed scope. |
| A customer asks about merchandise delivery, marketplace rewards, or a payout unrelated to the consumer wallet. | Your existing support channel. Assess any separate wallet transaction complaint and route it to Stripe when applicable. |

Stripe handles eligible Regulation E investigations, required communications, provisional credit where applicable, decisions, and outcome notifications. Your team handles other marketplace disputes and unrelated products. Don’t treat every general expression of dissatisfaction as unregulated if it concerns the financial product or potentially unfair practices.

### Integrations and handoffs 

Use the [wallet authentication factors](https://docs.stripe.com/managed-support/programs.md#authentication-factors) and shared [dispute and complaint intake processes](https://docs.stripe.com/managed-support/set-up.md#regulated-workflows). Wallet dispute API intake isn’t available, so direct customers to the Managed Support phone line. Customers can submit relevant evidence through the agreed process, including documents and the expected amount for an incorrect-amount report.

Maintain your existing support channel for questions outside the regulated scope and other handoffs.
