# braintree subscription failed processor declined error

## TL;DR
The decline came from the customer's bank, not Braintree: read the processor response code and text on the failed transaction. Map the code (do_not_honor means the bank said no), ask the customer to contact their bank or use another card, then update the payment method and retry. Do not hammer hard declines with retries.

```text
braintree subscription failed processor declined error
```

## Use this when

- Braintree subscription transactions fail with processor declined
- The decline reason references the processor or the issuing bank
- Retrying the same card keeps failing

## Not for this skill when

- Braintree gateway rejections (validation or risk rules, not the bank)
- Processor errors that are actually timeouts (try again, different cause)
- Subscription setup failures before any charge attempt

## Steps

### Step 1: Read the processor response

Open the failed transaction in Braintree and note the processor response code and text. Expected: you can quote the bank's reason.

### Step 2: Map the decline code

Look up what the code means: do_not_honor, insufficient funds, lost card, and so on. Expected: you know whether it is soft (retryable) or hard (needs a new card).

### Step 3: Contact the customer

Tell the customer the bank declined the charge and suggest contacting the bank or using another card. Expected: the customer acts on the actual cause.

### Step 4: Update the payment method

Add the new card to the Braintree customer or subscription. Expected: a valid payment method is on file.

### Step 5: Retry once, deliberately

Retry the charge a single time on the new method. Expected: the subscription goes active; no retry storms on hard declines.

## Tool compatibility

Braintree subscriptions and transactions; processor response codes; Braintree control panel.

## Variant phrasings

### Variant 1

braintree processor declined subscription

### Variant 2

braintree transaction declined do_not_honor

### Variant 3

braintree subscription failed card declined fix

## Why it happens

In card processing there are two layers of refusal, and they need opposite responses. The gateway layer (Braintree) rejects for validation, fraud rules, or configuration, and those are yours to fix. The processor layer is the issuing bank saying no, and no gateway setting overrides it. Processor declined with codes like do_not_honor is the bank's verdict, often for reasons it will not fully disclose: risk scoring, daily limits, or a flag on the account. Retrying the same card is the instinct and it is wrong for hard declines; the only path forward runs through the customer and their bank.

## Edge cases / pitfalls

- AVS and CVV rules can turn soft mismatches into declines; check those settings before blaming the bank.
- Hard declines should never be auto-retried aggressively; that pattern looks like fraud testing.
- Some declines resolve when the customer approves the merchant with their bank; suggest that explicitly.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_9sb9V7xSM8VQg1Ef_ASK_g