# How to block payments from non billing country sources

Out of the box, Stripe implements a lot of security features for you, making payments safe and secure by default. You may still have a need to provide additional security steps of your own.

If you are based in the EU selling digital goods it would be a requirement to capture two forms of proof of a customer's location for VAT purposes. One recommended way is to capture the customer's billing country, and bank country, and ensure these are the same. The Stripe payment provider allows you to set this up in a few steps.

## Step 1: Capture the customer's billing country

The first step is to ensure you are capturing the customer's billing address or more specifically, the billing address country. Learn how to do this in the core Umbraco Commerce documentation.

## Step 2: Pass the billing country to Stripe

As long as you have populated your orders billing country, it will automatically be sent to Stripe using custom metadata on the transactions customer entity. This will be passed via a metadata entry on the Stripe customer with the key `billingCountry`, with the value of the two-letter ISO code of the given country.

## Step 3: Sign up for Radar for Fraud Teams

In order to configure custom Radar rules you need to sign up for the [Radar for Fraud Teams](https://stripe.com/radar/fraud-teams) added feature. This does incur an additional fee per transaction, however, the added security will outweigh the minimal expense.

To enable **Radar for Fraud Teams** follow these steps:

1. Log in to your Stripe dashboard.
2. Navigate to the **Settings > Product Settings > Radar Settings** section.

![Stripe Product Settings](https://3206860037-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO8zV7PYqNxSkuGGGYa3P%2Fuploads%2Fgit-blob-d29146563bc366aeff5e2798305a606ffcbf6884%2Fstripe_product_settings.png?alt=media)

3. Enable the **Radar for Fraud Teams** feature, allowing us to define custom Radar rules.

![Stripe Radar for Fraud Teams Setting](https://3206860037-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO8zV7PYqNxSkuGGGYa3P%2Fuploads%2Fgit-blob-54677737f0e923f1629f50570d0c4b173cec08f4%2Fstripe_radar_for_fraud_teams.png?alt=media)

## Step 4: Setup a Stripe Radar rule

To set up a new Stripe Radar rule, follow these steps:

1. Navigate to the **Radar > Rules** section.
2. Locate the **Then, when should a payment be blocked?** panel.
3. Click the **Add rule** button to add a new rule.
4. Enter the following rule in the dialog:

```
Block if ::customer:billingCountry:: != :card_country:
```

![Stripe Radar for Fraud Teams Setting](https://3206860037-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO8zV7PYqNxSkuGGGYa3P%2Fuploads%2Fgit-blob-423e30b9dd315cacab32e6db2f06de582b537da9%2Fstripe_block_country_rule2.png?alt=media)

5. Click the **Test rule** button to test the rule.
6. Click the **Add and enable** button to add the rule to the list of block rules.

![Stripe Radar blocking rules](https://3206860037-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO8zV7PYqNxSkuGGGYa3P%2Fuploads%2Fgit-blob-370e0e470f75ec87f7aedb9798d808f87cae6396%2Fstripe_block_rules2.png?alt=media)

{% hint style="info" %}
The rule test may fail when you click the **Test rule** button due to there being no transaction with the given metadata being attached to them. You will, however, be able to continue regardless.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.umbraco.com/umbraco-commerce-payment-providers/stripe/how-to-guides/radar-billing-country-rule.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.