New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingPaymentsRevRecGrowthReveal
Support

Product Updates

  • Release Notes

Getting Started

  • Overview
  • Chargebee Billing Data Centers
  • Object Relationship Model
  • Understanding Sites
  • Chargebee Tech Glossary
  • Articles and FAQ

Implementing Chargebee

  • Implementation Guide
  • Go-live Checklist
  • Articles and FAQ

AI in Chargebee

  • Chargebee Agents
  • Chargebee Copilot
  • Chargebee MCP Server (Model Context Protocol)

Developer Resources

  • Developer Resources Overview
  • Articles and FAQ

Product Catalog

  • Product Catalog Overview
  • Coupons
  • Articles and FAQ

Subscriptions

  • Working with Subscriptions
  • Billing
  • Orders
  • Articles and FAQ

Customers

  • Managing Customers
  • Account Hierarchy
  • Email Notifications
  • Branding
  • Configure Multiple Languages
  • Articles and FAQ

Entitlements

  • Entitlements Overview
  • Features Overview
  • Feature Management
  • Managing Product Entitlements
  • Subscription Entitlements
  • Customer Entitlements
  • Grandfathering Entitlements
  • Articles and FAQ

Usage Based Billing

  • Understanding Usages
  • Setting up Usage Based Billing
  • Usage Alerts
  • Metered Billing
  • Articles and FAQ

Chargebee CPQ

  • Chargebee CPQ
  • Chargebee CPQ for Salesforce
  • Chargebee CPQ for HubSpot

Invoices, Credit Notes, and Quotes

  • Invoices
  • Credit Notes
  • Quotes [Legacy]
  • Transactions
  • Articles and FAQ

Taxes

  • Overview
  • Configuring Taxes
  • Country-specific Taxes
  • Articles and FAQ

Hosted Capabilities

  • Overview
  • Hosted Checkout
  • Hosted Self-Serve Portal
  • Hosted Pages Features
  • Additional Hosted Pages
  • Payment Components
  • Pricing Table
  • Managing Payments with Chargebee.js
  • Mobile-Optimized Hosted Pages
  • Articles and FAQ

Site Configuration

  • Users & Roles
  • Custom Fields & Metadata
  • Approvals
  • Mandatory Fields
  • File Attachments & Comments
  • Advanced Filter Options
  • Multicurrency Pricing
  • Multi-decimal Support
  • Configuring Reason Codes
  • Events and Webhooks
  • API Keys
  • Time Zone
  • Time Machine
  • Transfer Configurations
  • Articles and FAQ

Multi Business Entity

  • Multi Business Entity Overview
  • Customer Transfer Overview
  • Articles and FAQ

Mobile Subscriptions

  • Overview
  • Omnichannel Subscriptions
  • Omnichannel One-Time Orders
  • Mobile Subscriptions (Legacy)

Reports and Analytics

  • RevenueStory
  • Home Dashboard
  • Frequently Asked Questions
  • FAQs for Classic Reports Sunset
  • Articles and FAQ

Integrations

  • Sales
  • Customer Support and Success
  • Finance
  • Tax
  • eInvoicing
  • Marketing
  • Stitch
  • Collaboration
  • Contract Management
  • Ecommerce Management
  • Articles and FAQ

Data Privacy & Security

  • Two Factor Authentication
  • SAML Single Sign-On
  • System for Cross-Domain Identity Management (SCIM)
  • EU-GDPR
  • Consent Management
  • Personal Data Management
  • Compliance Certificates
  • HIPAA Guidelines
  • PCI Recommendations and Integration Types
  • Articles and FAQ

Data Operations

  • Bulk Operations
  • Migration
  • Articles and FAQ
  1. Billing
  3. Taxes
  5. Articles and FAQ
  6. EU VAT
  1. Billing
  3. Taxes
  5. Articles and FAQ
  6. EU VAT

This customer's location couldn't be validated as required by the new EU VAT 2015 rules

Problem Statement

This article helps you understand this customer's location couldn't be validated as required by the new eu vat 2015 rules.

Scope

This customer's location couldn't be validated as required by the new EU VAT 2015 rules

Solution

Step 1: Locate such customers. You could filter the customer whose address is not validated by using the filter "Is location valid" "is not" "true".

image

This filter would give you the list of all customers whose location is not validated according to EU VAT rules.

When you open the customer record you would see a banner as in the screenshot below.

image

Step 2: If you are using API so you would have to pass the data for verification using API.

Customer's IP Address:

  • API: If you use the Chargebee API, you have to pass the IP Address of the customer to Chargebee using the User Details Header API.

  • The IP address can be updated by APIs using the Update a subscription API using the parameter "card[ip_address]". After the IP address is updated, you can call the "re-activate subscription" API.

  • You would need to use Chargebee's Update a Card Payment Source API and pass the correct IP address using the parameter card [ip_address]. The card's IP address HAS TO BELONG TO the customer's billing or shipping address.

Card BIN of the Customer:

The first six digits of a card carry the Bank Identification Number (BIN). BIN gives us information about the card-issuing bank and hence can be used as a way to determine the customer's location.

  • API: If you use the Chargebee API, you have to pass the BIN of the customer using the card [number] parameter in the Create a customer API.

Step 3: Check if all the customers who were not imported but created via API have their validation status as false.

You could send them the updated payment method link and ask them to update their card from their corresponding countries which would then update the IP and the BIN numbers.

image

Refer to this link for more information.

Related Articles

Use local currency to display VAT in Invoices
Can I configure taxes for both digital and physical products if I am selling within the EU?
Apply taxes without collecting address in checkout

Was this article helpful?