# Manage bank payment return risk

Use Radar to predict and prevent bank-initiated returns before you submit a bank debit.

Bank debits fail differently from card payments. A card decline is immediate, but a bank debit can appear to succeed and then be returned days later because the account has insufficient funds, is closed, or has incorrect details. These bank-initiated returns mean the account can’t fund the payment.

Customer-initiated returns occur when your customer tells their bank that a debit was unauthorized. Radar’s fraud tools handle this separate risk. See [How Radar works](https://docs.stripe.com/radar/how-radar-works.md) for details.

This feature is in private preview and available only to invited users. The API and Dashboard behavior described here can change before general availability. Contact your Stripe account team or fill out the form to request access.

[Request access](https://docs.stripe.com/.md#request-radar-for-bank-payments-access)

## What Radar for bank payments provides 

Use Radar to assess bank return risk, flag payments for review, and monitor returns:

- **Risk signal for non-fraud failures**: Radar scores each bank payment for the likelihood of a bank-initiated return. This signal is available for payments you process on Stripe and payments you evaluate through the Radar Payment Evaluations API.
- **Review action**: For payments processed on Stripe, you can place a high-risk bank payment in review instead of rerouting it. Review flags the payment for your team without stopping the debit, so use it as a secondary response. The Payment Evaluations API doesn’t return a review recommendation.
- **Return analytics in the Dashboard**: See your overall return rate, break it down by return code and institution, and get notified when your return rate deviates from normal.

## Permitted and prohibited uses 

Radar’s bank payment score and the bank account information available in rules predict whether an individual debit is likely to clear. They don’t assess your customer. Use them to manage risk for individual bank payments by rerouting a high-risk payment, placing it in review, or asking the customer to relink their bank account.

Use Dashboard analytics to monitor return patterns across your bank payments. Use the institution attribute to respond to specific situations, such as a spike in returns from a particular bank, rather than to reroute all payments from that bank’s customers.

Don’t use the score, risk level, recommended action, bank account information, or any other output from this feature to:

- Block or decline a payment. Reroute high-risk payments so customers can pay another way. Radar rejects block rules that use `bank_initiated_return_score` or a bank account attribute.
- Make or inform a decision about someone’s eligibility for credit, housing, employment, or insurance. This includes loan underwriting, rental applications and deposit amounts, hiring and compensation, and insurance pricing.
- Set or change the rates, fees, or terms you offer a customer.
- Build or add to a customer profile, score, or dataset. Each score and attribute applies only to the payment evaluated. Don’t store or reuse them to evaluate the customer later.
- Share, sell, or sublicense outputs or attributes to a third party for any use that isn’t allowed on this page.

## Before you enroll 

Stripe reviews how you plan to use this feature before and during the preview, and can limit or remove your access based on that review. You need Stripe’s approval before you enroll if either of the following applies:

- Your business is primarily a consumer lender, a buy now, pay later provider, a residential landlord or property manager, or an employer making employment-related payment decisions. Stripe might approve a limited scope of use for businesses in these or similar categories, and can change or revoke that approval at any time.
- You accept only bank payments at checkout.

Contact your Stripe account team to request approval.

## Supported payment methods 

Radar’s bank payment risk signals apply to ACH Direct Debit and SEPA Direct Debit using the `us_bank_account` and `sepa_debit` payment method types. SEPA Direct Debit is available only for bank payments you process on Stripe. Radar supports bank accounts collected through Financial Connections and bank accounts entered manually as account and routing numbers. The legacy `ach_debit` payment method type isn’t supported.

## Availability

Radar for bank payments works both for bank payments you process on Stripe and for bank payments you process through another provider.

| Capability | Payments processed on Stripe | Payments processed elsewhere |
| --- | --- | --- |
| `bank_initiated_return_score` in Radar rules | Supported | Supported |
| Reroute rule action | Supported, enforced by Stripe | Returned as a recommendation for you to act on |
| Review rule action | Supported, enforced by Stripe | Unsupported |
| Risk signals in the API | `outcome.radar_scores` on the charge | `signals` on the payment evaluation |
| Rule backtesting | Supported | Supported |

One set of Radar rules applies to both. When you create a rule in the Dashboard, it applies to payments you process on Stripe and payments you evaluate through the API.

### Payments processed on Stripe

Radar evaluates a bank payment automatically when you confirm a `PaymentIntent` or `SetupIntent` using a `us_bank_account` payment method. This applies whether you use Checkout, elements, Billing, or the API directly. You don’t need an additional API call.

### Payments processed elsewhere

If you process bank payments through another provider or want to evaluate risk before you create a `PaymentIntent`, call the Payment Evaluations API. Pass a payment method and an amount, and Radar returns risk signals and a recommended action. Report the outcome afterward so Radar’s models can learn from your payments.

### Connect

Radar checks external charges only. It doesn’t evaluate fund transfers between Stripe accounts.

Which account’s rules apply depends on the charge type:

- **Direct charges**: Payments go directly to a connected account. Stripe applies only the collecting account’s Radar configuration and rules.
- **Transferred charges**: Payments go to the platform account and are transferred to a connected account. This includes destination charges and separate charges and transfers. Stripe applies only the platform account’s Radar configuration and rules.

Where you configure bank payment rules depends on the connected account’s Dashboard access:

| Dashboard access of the connected account | Configure in the connected account Dashboard | Configure in the platform Dashboard Connect page |
| --- | --- | --- |
| Connected accounts with access to the Stripe Dashboard | Supported | Unsupported |
| Connected accounts with access to the Express Dashboard | Unsupported | Supported |
| Connected accounts with no Dashboard access | Unsupported | Supported |

Connected accounts can’t define their own Radar rules without access to the full Stripe Dashboard. To configure rules for those accounts, use **View Dashboard as this account** from your platform Dashboard.

For more details, see [Use Radar with Connect](https://docs.stripe.com/connect/radar.md).

## Types of bank returns 

### Bank-initiated returns 

Banks return some payments days after submission because the account has insufficient funds, is closed, or has incorrect details. These bank-initiated returns mean the account can’t fund the payment. They don’t indicate that the customer or bank account is fraudulent.

These types of returns are represented by Radar’s `bank_initiated_return` score, which estimates the likelihood that the account won’t fund this payment for non-fraud reasons.

This category includes the following return codes:

| Payment method | Return code | Label | Description |
| --- | --- | --- | --- |
| ACH Direct Debit | R01 | Insufficient funds | There are not enough funds in the account to cover the transaction. |
| ACH Direct Debit | R02 | Account closed | The account holder has closed the account being accessed. |
| ACH Direct Debit | R03 | No account or unable to locate account | The account or routing information doesn’t match any accounts at the RDFI. |
| ACH Direct Debit | R04 | Invalid account number | The account number has incorrect digits, fails validation, or doesn’t match the RDFI’s records. |
| ACH Direct Debit | R06 | Returned per ODFI request | The ODFI has returned the transaction for various reasons. |
| ACH Direct Debit | R08 | Payment stopped | The account holder placed a stop payment order on this specific transaction. |
| ACH Direct Debit | R09 | Uncollected funds | Deposits haven’t yet cleared, resulting in insufficient funds. |
| ACH Direct Debit | R12 | Account sold to another RDFI | The customer’s account has been transferred to another RDFI. |
| ACH Direct Debit | R13 | Invalid ACH routing number | The ACH routing number is incorrect. |
| ACH Direct Debit | R14 | Representative payee deceased or unable to continue in that capacity | The representative payee is deceased or can’t perform their duties. |
| ACH Direct Debit | R15 | Beneficiary or account holder deceased | The beneficiary or account holder is deceased. |
| ACH Direct Debit | R16 | Account frozen | The account is frozen because of legal action or bank policy. |
| ACH Direct Debit | R17 | File record edit criteria | The entry contains invalid formatting or data, suggesting questionable circumstances. |
| ACH Direct Debit | R18 | Improper effective entry date | The transaction used an incorrect effective entry date. |
| ACH Direct Debit | R19 | Amount field error | The amount entered in the Amount field is invalid. |
| ACH Direct Debit | R20 | Non-transaction account | Policies or regulations prevent ACH transactions on this account. |
| ACH Direct Debit | R21 | Invalid company identification | The company ID information is incorrect or outdated. |
| ACH Direct Debit | R22 | Invalid individual ID number | The individual ID number entered was invalid. |
| ACH Direct Debit | R23 | Credit entry refused by receiver | The RDFI refused the credit entry, possibly because of a dispute. |
| ACH Direct Debit | R24 | Duplicate entry | The same transaction was submitted more than once. |
| ACH Direct Debit | R25 | Addenda error | The addenda record is incorrect or out of sequence. |
| ACH Direct Debit | R26 | Mandatory field error | A required field is missing information. |
| ACH Direct Debit | R27 | Trace number error | The trace numbers submitted aren’t consistent with the addenda record. |
| ACH Direct Debit | R28 | Routing number check digit error | The check digit in the routing number is incorrect. |
| ACH Direct Debit | R30 | RDFI not a participant in check truncation program | The RDFI doesn’t participate in the check truncation program. |
| ACH Direct Debit | R32 | RDFI non-settlement | The RDFI isn’t able to settle the entry for various reasons. |
| ACH Direct Debit | R33 | Return of XCK entry | The RDFI returned an entry for a lost, destroyed, or damaged check. |
| ACH Direct Debit | R34 | Limited participation DFI | A federal or state regulator has limited the RDFI’s ability to process ACH transactions. |
| ACH Direct Debit | R35 | Return of improper debit entry | A debit entry was improperly submitted. |
| ACH Direct Debit | R36 | Return of improper credit entry | A credit entry was improperly submitted. |
| ACH Direct Debit | R37 | Source document presented for payment | A duplicate payment attempt was made through the related source document. |
| ACH Direct Debit | R38 | Stop payment on source document | The receiving account holder requested to stop payment on a converted check. |
| ACH Direct Debit | R39 | Improper source document | The source document related to the ACH payment is incorrect or inadequate. |
| ACH Direct Debit | R40 | Return of ENR entry by federal government agency | A federal government agency has returned an automated enrollment entry. |
| ACH Direct Debit | R41 | Invalid transaction code | The transaction code relating to direct deposit or payment enrollment with a federal agency is incorrect. |
| ACH Direct Debit | R42 | Routing number check digit error | The check digit in the routing number is incorrect in a federal government ENR entry. |
| ACH Direct Debit | R43 | Invalid DFI account number | The RDFI account number is incorrect. This return code applies only to ENR entries. |
| ACH Direct Debit | R44 | Invalid individual ID number | The individual identification number provided doesn’t match the ID number on record. |
| ACH Direct Debit | R45 | Invalid individual name | The account holder’s name is incorrect or misspelled. |
| ACH Direct Debit | R46 | Invalid representative payee indicator | The representative payee indicator code is incorrect. |
| ACH Direct Debit | R47 | Duplicate enrollment | The same ENR entry was submitted more than once. |
| ACH Direct Debit | R50 | State law affecting RCK acceptance | The RDFI’s state law disallows digital payments or requires timely return of checks. |
| ACH Direct Debit | R51 | Item related to RCK entry is ineligible or RCK entry is improper | The item is ineligible, or the RCK entry was improperly prepared. |
| ACH Direct Debit | R52 | Stop payment on item related to RCK entry | The account holder placed a stop payment order on a bounced check being reprocessed. |
| ACH Direct Debit | R53 | Item and RCK entry presented for payment | Both the original transaction and its corresponding RCK entry were submitted. |
| ACH Direct Debit | R61 | Misrouted return | A reversed transaction was sent to the incorrect institution. |
| ACH Direct Debit | R62 | Return of erroneous or reversing debit | A debit entry was sent in error or needs to be reversed. |
| ACH Direct Debit | R63 | Incorrect dollar amount | The dollar amount specified in the transaction is wrong. |
| ACH Direct Debit | R64 | Incorrect individual identification | The individual ID in the return doesn’t match the one in the original entry. |
| ACH Direct Debit | R65 | Incorrect transaction code | The transaction code isn’t correct for the type of transaction. |
| ACH Direct Debit | R66 | Incorrect company identification | The company ID doesn’t match the ID number in the batch header record. |
| ACH Direct Debit | R67 | Duplicate return | The return entry was already processed, resulting in a duplicate. |
| ACH Direct Debit | R68 | Untimely return | The return wasn’t processed within the required time frame. |
| ACH Direct Debit | R69 | Field errors | One or more fields contain incorrect information, such as an account number or name mismatch. |
| ACH Direct Debit | R70 | Permissible return entry not accepted or return not requested by ODFI | A valid return wasn’t processed properly, or the ODFI didn’t request it. |
| ACH Direct Debit | R71 | Misrouted dishonored return | A dishonored return entry wasn’t sent to the correct institution. |
| ACH Direct Debit | R72 | Untimely dishonored return | A dishonored return wasn’t processed within the required time frame. |
| ACH Direct Debit | R73 | Timely original return | The RDFI confirms that the original return was processed within the required time frame. |
| ACH Direct Debit | R74 | Corrected return | A previously improperly processed return has since been corrected. |
| ACH Direct Debit | R75 | Return not a duplicate | The RDFI contests an improper dishonor of a return entry by the ODFI. |
| ACH Direct Debit | R76 | No errors found | The RDFI disputes an R69 return, stating that the claimed errors don’t exist. |
| ACH Direct Debit | R77 | Non-acceptance of R62 dishonored return | The RDFI indicates it already returned the transaction or can’t recover the funds. |
| ACH Direct Debit | R80 | IAT entry coding errors | Coding errors exist in the IAT entry. |
| ACH Direct Debit | R81 | Non-participant in IAT program | The RDFI doesn’t participate in the IAT program. |
| ACH Direct Debit | R82 | Invalid foreign RDFI identification | The foreign RDFI’s identification is incorrect. |
| ACH Direct Debit | R83 | Foreign RDFI unable to settle | The foreign RDFI can’t complete the transaction. |
| ACH Direct Debit | R84 | Entry not processed by gateway | The entry hasn’t been processed by the designated gateway. |
| ACH Direct Debit | R85 | Incorrectly coded outbound international payment | An outbound international payment was incorrectly coded. |

### Customer-initiated returns 

Other bank returns occur when your customer tells their bank that a debit was unauthorized.

These types of returns are represented by Radar’s `fraudulent_dispute` score, which estimates the likelihood that the payment results in a dispute (customer-initiated bank return) with reason code `fraudulent`.

This category includes the following return codes:

| Payment method | Return code | Label | Description |
| --- | --- | --- | --- |
| ACH Direct Debit | R05 | Unauthorized debit to consumer account using corporate SEC code | A corporate Standard Entry Class (SEC) code was incorrectly used for a consumer account. |
| ACH Direct Debit | R07 | Authorization revoked by customer | The customer has revoked the authorization of the transaction. |
| ACH Direct Debit | R10 | Customer advises not authorized | The customer has stated the transaction wasn’t authorized. |
| ACH Direct Debit | R11 | Customer advises entry not in accordance with the terms of the authorization | The customer states that the debit doesn’t match the agreed authorization, such as the wrong amount or date. |
| ACH Direct Debit | R29 | Corporate customer advises not authorized | A corporate account holder notified the RDFI that the transaction isn’t authorized. |
| ACH Direct Debit | R31 | Permissible return entry | The RDFI asked, and the ODFI agreed, to allow return of a CTX payment. |

### How Radar scores bank return risk 

Radar produces two scores for each bank payment:

- `bank_initiated_return`
- `fraudulent_dispute`

The two scores are independent: a bank payment can have a high risk of a return and a low risk of fraud.

Each signal has a score from 0 to 100, where a higher score means the outcome is more likely, and a risk level derived from that score: `low`, `normal`, `elevated`, or `highest`. When Radar can’t assess a signal, the risk level is `not_assessed` or `unknown`.

Scores reflect a specific transaction. The same bank account can score differently for a 50 USD payment and a 5,000 USD payment because the prediction is about whether this debit will clear, not about the account holder.

## Choose how to respond to bank return risk 

A high bank-initiated return score predicts that this payment is likely to be returned, not that your customer or their bank account is fraudulent. You can’t use `bank_initiated_return_score` in a block rule. Radar rejects the rule when you try to save it.

We recommend rerouting payments with a high risk of failure before submitting the debit. To flag a bank debit for manual review after submission, you can place it in [review](https://docs.stripe.com/radar/transaction-risk-prevention/bank-payments.md#place-high-risk-payments-in-review).

### What rerouting does

Stripe doesn’t submit a rerouted payment to the bank, and no funds move. Rerouting is a final state for the charge, so you can’t retry it. Your customer completes the purchase by paying with a different payment method.

## Create a reroute rule 

Create a rule to reroute payments that meet your bank return risk threshold:

1. In the Dashboard, go to **Radar**, then select **Rules**.
2. In the transaction rules section, select **Add rule**.
3. For the action, select **Reroute bank payment if**.
4. Enter a condition, such as `:bank_initiated_return_score: >= 75`.
5. Backtest the rule, then save it.

Start with a threshold of 75 and adjust it based on your backtest results.

> #### Live mode evaluation
> 
> Radar evaluates bank payment risk signals in live mode only. You can create rules in a sandbox, but rules that use `bank_initiated_return_score` evaluate only live bank payments.

### Backtest a rule

Before you activate a rule, backtest it to estimate how many returns it would have prevented and how many payments it would have rerouted.

Backtest results and rule performance metrics count rerouted payments separately from blocked payments. The **Blocked or rerouted payments** metric on the rule details page includes a **Rerouted by Radar** breakdown.

Backtesting uses your historical bank payments. If your account was recently enabled for the preview, ask your Stripe account team to confirm how far back your backtesting window reaches.

## Handle a rerouted payment in your integration 

When a reroute rule matches, Stripe doesn’t submit the debit. The `PaymentIntent` transitions to `requires_payment_method`, and the charge records the reroute in [outcome](https://docs.stripe.com/api/charges/object.md#charge_object-outcome):

| Property | Value |
| --- | --- |
| `outcome.type` | `rerouted` |
| `outcome.reason` | `rule` |
| `outcome.radar_scores.bank_initiated_return.score` | The score that triggered the rule |
| `outcome.radar_scores.bank_initiated_return.risk_level` | The risk level derived from that score |

Because the `PaymentIntent` returns to `requires_payment_method`, you can prompt your customer to choose a different payment method and confirm the same `PaymentIntent` again with that payment method.

To distinguish a reroute from other declines, check for an `outcome.type` of `rerouted`.

### Recommended handling

Don’t automatically retry the same bank account. The score reflects the likelihood of a bank-initiated return on this payment, so an immediate retry is likely to be returned as well.

In a Checkout or elements flow, present your other enabled payment methods and let your customer retry immediately. Your customer sees a generic payment failure message that doesn’t mention the bank account or suggest paying another way. Use your own message to explain that the bank account can’t be used for this payment.

In an off-session or invoice flow, email your customer to ask them to update their payment method. Check your retry settings so that automatic retries don’t attempt to debit the same bank account again.

## Evaluate a bank payment through the API 

Use the [Payment Evaluations API](https://docs.stripe.com/api/radar/payment-evaluation.md) when you process bank payments through another provider or want a risk evaluation before you create a `PaymentIntent`.

### Create a payment method

Convert a Financial Connections account into a payment method:

```curl
curl https://api.stripe.com/v1/payment_methods \
  -u "<<YOUR_SECRET_KEY>>:" \
  -d type=us_bank_account \
  -d "us_bank_account[financial_connections_account]=fca_456" \
  -d "billing_details[name]=Test Customer"
```

If your customer entered their bank details manually, use the resulting bank account token instead:

```curl
curl https://api.stripe.com/v1/payment_methods \
  -u "<<YOUR_SECRET_KEY>>:" \
  -d type=us_bank_account \
  -d "us_bank_account[token]=btok_abc" \
  -d "billing_details[name]=Test Customer"
```

### Evaluate the payment

Next, [create a payment evaluation](https://docs.stripe.com/api/radar/payment-evaluation/create.md?api-version=2026-08-26.preview&rds=1):

```curl
curl https://api.stripe.com/v1/radar/payment_evaluations \
  -u "<<YOUR_SECRET_KEY>>:" \
  -H "Stripe-Version: 2026-10-28.preview; payment_evaluations_beta=v1" \
  -d "payment_details[payment_method_details][payment_method]=pm_456" \
  -d "payment_details[amount]=100" \
  -d "payment_details[currency]=usd" \
  -d "payment_details[money_movement_details][money_movement_type]=us_bank_account" \
  -d "payment_details[money_movement_details][us_bank_account][customer_presence]=on_session" \
  -d "payment_details[money_movement_details][us_bank_account][payment_type]=one_off" \
  --data-urlencode "customer_details[email]=jenny.rosen@example.com" \
  -d "client_device_metadata_details[radar_session]=rse_123"
```

The `customer_details` parameter is required. You can also include these optional parameters:

- `client_device_metadata_details`: Include `radar_session` when you have one so that Radar can use browser and device context. If you pass `client_device_metadata_details`, you must include either `radar_session` or `data` with `ip` and `user_agent`.
- `money_movement_details`: Include this parameter to improve the evaluation and provide a more useful breakdown in your Dashboard analytics. If you pass it, you must include `money_movement_type`, set it to match the payment method type, and include the matching object. Set `customer_presence` to `on_session` or `off_session`, and `payment_type` to `one_off` or `recurring`.

Radar returns the evaluation:

```json
{
  "id": "peval_123",
  "object": "radar.payment_evaluation",
  "created_at": 1704067200,
  "livemode": true,
  "recommended_action": "reroute",
  "signals": {
    "bank_initiated_return": {
      "evaluated_at": 1704067200,
      "risk_level": "elevated",
      "score": 82.5
    },
    "fraudulent_dispute": {
      "evaluated_at": 1704067200,
      "risk_level": "normal",
      "score": 8.2
    },
    "fraudulent_payment": {
      "evaluated_at": 1704067200,
      "risk_level": "normal",
      "score": 8.2
    }
  }
}
```

The `recommended_action` based on `bank_initiated_return` is either `continue` or `reroute`. Handle `reroute` by asking your customer to pay another way. A high fraud score can produce a `block` recommendation, which takes precedence over a recommendation based on `bank_initiated_return`. Radar doesn’t return `review` as a recommended action.

For bank payments, Radar populates the `bank_initiated_return` and `fraudulent_dispute` signals. Stripe also copies `fraudulent_dispute` to `fraudulent_payment` so that integrations that already read `fraudulent_payment` continue to work.

### Report the outcome

When you process payments on Stripe, Stripe records outcomes and events automatically. You don’t need to report them.

If you process bank payments through another provider, report outcomes so that Stripe can learn from those payments. If you attempted the payment, [report the result](https://docs.stripe.com/api/radar/payment-evaluation/radar/report-outcome/report.md?api-version=2026-08-26.preview&rds=1):

```curl
curl https://api.stripe.com/v1/payment_records/report_payment \
  -u "<<YOUR_SECRET_KEY>>:" \
  -H "Stripe-Version: 2026-10-28.preview; payment_evaluations_beta=v1" \
  -d "amount_requested[value]=100" \
  -d "amount_requested[currency]=usd" \
  -d initiated_at=1704067200 \
  -d "description=Test payment" \
  -d "payment_method_details[type]=us_bank_account" \
  -d "payment_method_details[us_bank_account][return_code]=R01" \
  -d outcome=failed \
  -d "failed[failed_at]=1704240000" \
  -d "failed[payment_evaluations][]=peval_123"
```

Pass the NACHA return code in `payment_method_details[us_bank_account][return_code]` to get a breakdown of failures by return code in your analytics. You can pass a return code only when `outcome` is `failed`. If a later call to the same payment record omits `return_code`, Stripe clears the stored value, so include it every time you update the record.

To report a customer-initiated dispute on a bank payment, call [report_dispute](https://docs.stripe.com/api/payment-record/report-dispute.md) on the payment record with a reason of `debit_not_authorized`.

If you followed a `reroute` recommendation and didn’t attempt the debit, first create a payment record by calling `report_payment` without an outcome, then use the returned payment record ID to report the attempt as canceled:

```curl
curl https://api.stripe.com/v1/payment_records/pr_123/report_payment_attempt_canceled \
  -u "<<YOUR_SECRET_KEY>>:" \
  -H "Stripe-Version: 2026-10-28.preview; payment_evaluations_beta=v1" \
  -d canceled_at=1704067200 \
  -d reason=rerouted \
  -d "payment_evaluations[]=peval_123"
```

Report outcomes for bank payments within four business days of the evaluation, which allows time for settlement.

## Review bank payment returns in the Dashboard 

The [Radar overview page](https://dashboard.stripe.com/radar) shows your bank return rate, which is the overall failure rate for your bank payments. Select the tile to see a breakdown of bank-initiated and customer-initiated returns. Select a chart to view a category by reason code and other contributing factors, along with a list of affected transactions.

On the [transactions page](https://dashboard.stripe.com/payments), a rerouted payment shows a **Rerouted** badge and the timeline records that a Radar rule rerouted the payment, with a link to the rule. The bank-initiated return score appears with the payment’s other risk scores.

## Test your integration

Financial Connections provides test bank accounts:

| Test account | Result |
| --- | --- |
| **Success** under **Test Bank** | Low risk level, `continue` recommendation, payment succeeds |
| **Account Closed** under **Test Bank** | Normal fraud risk, high bank-initiated return risk, `continue` recommendation, payment fails |
| **Highest Risk Rerouted by Radar** under **Radar Accounts** | Highest bank-initiated return risk level, `reroute` recommendation |
| **High Fraud Low Return Risk** under **Radar Accounts** | Highest fraud risk level, low bank-initiated return risk level, `block` recommendation |

You can also use test payment method IDs:

| Payment method | Result |
| --- | --- |
| `pm_usBankAccount_success` | Low risk level, `continue` recommendation, payment succeeds |
| `pm_usBankAccount_insufficientFunds` | Normal fraud risk, high bank-initiated return risk, payment fails |
| `pm_usBankAccount_riskLevelHighest` | Highest risk level, `reroute` recommendation |

## Optional: Place high-risk bank payments in review

We recommend rerouting payments with a high bank-initiated return score. If you also want your team to review high-risk payments, you can write a rule that places them in review after Stripe submits the debit.

## Review doesn’t stop the payment

ACH Direct Debit and SEPA Direct Debit don’t have separate authorization and capture steps, so there’s no pending authorization for a review to hold. When a review rule matches:

- Stripe submits the debit.
- The `PaymentIntent` moves to `processing`, then `succeeded` if the debit clears.
- The charge records an `outcome.type` of `manual_review`, an `outcome.network_status` of `approved_by_network`, and an `outcome.seller_message` of `This payment was placed in manual review`.
- A review opens on the payment and appears in your Radar review queue.

Review flags the payment without holding it, so a bank return might still occur. Your team can refund the payment or contact the affected customer after submission.

The most common use case is an off-session payment, such as a subscription or invoice debit, where the customer isn’t present to choose a different payment method and rerouting would fail the payment. You can also flag on-session payments for review.

## Create a review rule

Create a rule to flag payments that meet your bank return risk threshold:

1. In the Dashboard, go to **Radar**, then select **Rules**.
2. In the transaction rules section, select **Add rule**.
3. For the action, select **Review if**.
4. Enter a condition using `bank_initiated_return_score`.
5. Backtest the rule, then save it.

Set your threshold based on your backtest results.

## Backtest a review rule

Backtest the rule before you activate it to see how many of your historical bank payments it would have matched.

A reroute backtest estimates how many returns you would have prevented. A review backtest estimates how many payments your team would have needed to review. Those payments would have proceeded whether or not your team reviewed them.

## Handle a payment in review

Because Stripe has already submitted the debit, the payment continues during review:

- Don’t hold fulfillment because of the review unless you intend to. The payment continues whether or not anyone processes the review queue.
- Approve the review to close it and leave the payment in place.
- Refund the payment if you decide not to accept it. Refunding is how you reverse a bank payment you’ve already accepted.
- Decide who processes the review queue and how quickly. Bank debits settle over several days, so an unresolved review usually resolves itself when the payment succeeds or is returned.

To bring reviews into your own tools, listen for the `review.opened` and `review.closed` events. The `review.opened` event tells you a payment needs attention. The `review.closed` event tells you the review was resolved. [Verify webhook signatures](https://docs.stripe.com/webhooks.md#verify-events) to confirm that events came from Stripe.

To resolve reviews in the Dashboard, go to **Radar**, then select **Reviews**. You can also use the Reviews API.
