LogoLogo
Become a PartnerStatus Page
  • get started
    • Welcome to 360Dialog
    • Quickstarts
      • Register as a Meta Tech Provider
      • Add a WhatsApp Number
      • Set up Integrated Onboarding
      • Create a Message Template
      • Send a Message
      • (temp title) Getting started as a partner
    • Pricing & Billing
      • Payment Methods for BR: Pix & Boleto
      • Month Closing Invoice (MCI)
    • Get API Access
    • Tech Provider Program
      • Understanding the Meta Tech Provider Program
      • Becoming a Meta Tech Provider: A Step-by-Step Guide
  • MM Lite Beta Program
    • Onboarding
    • Sending Messages
    • Expected Errors & Programming Languages
    • MM Lite Sandbox Testing
      • Sending Messages using MM Lite Sandbox
      • Expected Erros & Programming Languages
  • Partner & Account Management
    • Solutions for Partners
      • Benefits for Partners
      • Partner Hub
      • WABA Management
    • Account Setup & Management
      • Prerequisites and best practices for account creation
      • Account Structure
      • Account Creation
  • Integrations & API Development
    • Webhook Events & Setup
      • Webhook Events (Partner & Messaging API)
      • Webhook Configuration & Management
    • Integration Best Practices
      • Architecture and Security
      • Best Practices for Designing Integrations
        • Design a Stable Webhook Receiving Endpoint
      • Sizing Your Environment Based on Expected Throughput
      • Design a Resilient Message Sending Service
      • Integrated Onboarding
        • Basic Integrated Onboarding
        • Custom Integrated Onboarding
        • Host Your Own Embedded Signup
      • API Key Authentication for the Partner API
  • API Reference
    • Messaging API
    • Messaging Health Status
    • Sandbox (Test API Key)
    • Differences Between Cloud API and On-Premise API for Partners
      • [will be deprecated] Messaging with On-Premise API
    • Partner API
  • WABA Management
    • Managing WABA Accounts
      • Using the Partner Hub to manage Clients and Channels
      • Using the Partner API to manage Clients and Channels
      • Partner Permission to Generate API Key
      • Checking Usage & Statistics
    • Phone Number & Hosting
      • Migrating a Phone Number
        • Migrate number from Meta or alternate BSP to 360Dialog
        • Migrate a phone number to a new WABA
        • Migrate a phone number to a new WABA to change messaging Currency
      • WhatsApp Coexistence
        • Coexistence Onboarding
        • Coexistence Webhooks
      • Hosting type Change (On-premise API to Cloud API)
    • WABA Profile & Compliance
      • Display Name Guidelines
      • WABA Profile Info
      • WABA Policy Enforcement
      • Business Account Verification
    • Partner change (between 360Dialog Partners)
    • WhatsApp Flows
    • Accelerated Onboarding
    • Business Account Verification
  • Messaging
    • Sending & Receiving Messages
      • Conversations
      • Receiving messages
      • Before sending a message
    • Message Types
      • Conversational Components
      • Checklist for Message Broadcasts and Campaigns
      • Text messages
      • Interactive messages
        • Single and Multi Product Messages
        • Location Request Messages
        • Address Messages (India and Singapore only)
      • Contacts & Location Messages
    • Template Messages
      • Template Library
      • Template Elements
      • Sending Template Messages
      • Authentication Templates
        • Zero-Tap Authentication Templates
        • One-Tap Autofill Authentication Templates
        • Copy Code Authentication Templates
      • Catalog Templates
      • Product Card Carousel Templates
      • Single-Product Message Templates
      • Coupon Code Templates
      • Limited-Time Offer Templates
      • Multi-Product Templates
    • Media Messages
      • Upload, retrieve or delete media
    • Messaging Health & Troubleshooting
      • Messaging Limits & Quality Rating
      • Errors While Messaging
      • Messages statuses
  • Commerce & Payments
    • Payments (India Only)
      • Receive WhatsApp Payments via Payments Gateway
      • Receive WhatsApp Payments via Payment Links
      • Order Details Template Message
    • Payments (Singapore Only)
      • Receive WhatsApp Payments via Stripe
    • Products and Catalogs
      • India Businesses: Compliance for Commerce
  • Support & Updates
    • Help & Troubleshooting
      • FAQ
      • Error Code Reference
      • User Support Documentation
        • Tutorials
          • Page How to Troubleshoot Login Issues in the 360dialog Hub
          • How to Report an Issue
          • How to Contact Support
        • How-To Guides
          • Raise a support request
          • Requesting a Status Update for Business Verification
        • Reference
          • Troubleshooting Embedded Signup Issues
          • Commerce Policy Checks for WhatsApp API Access
          • Support Availability & SLAs
          • Incident Issue Prioritization
          • Case Types Table
        • Explanation
          • Why Business Verification Takes Time
          • Why Some Issues Are Not Emergencies
          • Understanding the Support Process
      • Support with Meta
    • Imprint & Data Privacy
    • Product Updates & News
      • How to ensure your Template Messages will be received
      • Integrated Onboarding new look and Campaigns Best Practices
Powered by GitBook
On this page
  • Providing Business Information
  • If the WABA is registered in Cloud API
  • If the WABA is registered in On-premise API
  • Retrieving Business Compliance Info
  • If the WABA is registered in Cloud API
  • If the WABA is registered in On-premise API

Was this helpful?

  1. Commerce & Payments
  2. Products and Catalogs

India Businesses: Compliance for Commerce

Requirements for businesses from India with +91 phone numbers

PreviousProducts and CatalogsNextHelp & Troubleshooting

Last updated 11 months ago

Was this helpful?

To sell products in India through WhatsApp, you must provide your business details via WhatsApp Business API. The business address can be added through the Profile Section in the 360dialog Hub or through WhatsApp Manager. If the company data is not provided, it will not be possible to send .

To send business information using WhatsApp Business API, you’re required to provide the following business information:

  1. Legal Name of Business: The full legal name of the business.

  2. Business Type: The options include:

    1. Limited liability partnership

    2. Sole proprietorship

    3. Partnership

    4. Public Company

    5. Private Company

    6. Other Note: If you select Partnership or Other as your business type, you will be asked if your Business is registered under applicable laws (Yes or No). Meta assumes that your Business is registered under applicable law for all other options.

  3. Business Address: The full address of the business.

  4. Applicable License/Registration: Enter the license or registration information for your business.

  5. Customer Care Information: Enter the contact information of the individual who will respond to and resolve the inquiries from your customers, such as returns or refunds.

  6. Grievance Officer Information: Enter the contact information of the individual who will respond to and resolve any complaints from your customers.

  7. Use the free text box to enter any other information that you are required to provide under applicable law(s).

See below how to provide a business' compliance information:

Providing Business Information

If the WABA is registered in Cloud API

Make a POST call to POST https://waba-v2.360dialog.io/business_compliance_info

If the WABA is registered in On-premise API

Make a POST call to POST https://waba.360dialog.io/v1/settings/business/compliance_info

In your call, include the D360-API-KEY and the parameters listed below:

Parameters

Name
Description

entity_name

Required.

A business' legal name.

entity_type

Required.

Available options are:

  • LIMITED_LIABILITY_PARTNERSHIP

  • SOLE_PROPRIETORSHIP

  • PARTNERSHIP

  • PUBLIC_COMPANY

  • PRIVATE_COMPANY

  • OTHER

entity_type_custom

Required in some cases.

Use when entity_type is set to "Other".

is_registered

type: Boolean

Required in some cases.

Use when entity_type is set to "Other" or "Partnership".

customer_care_details

Required.

grievance_officer_details

At least one contact field must be specified.

customer_care_details Object

Name
Description

email

Required.

An email customers can use to reach the business.

landline_number

Either landline_number or mobile_number must be provided.

A landline phone number customers can use to reach the business.

Phone numbers must be provided with a + sign and the country code.

mobile_number

Either landline_number or mobile_number must be provided.

A mobile phone number customers can use to reach the business.

Phone numbers must be provided with a + sign and the country code.

grievance_officer_details Object

Name
Description

name

Required.

The name of the business' grievance officer.

email

Either one of these contact methods (email, landline and mobile) is mandatory.

The email of the business' grievance officer.

landline_number

Either one of these contact methods (email, landline and mobile) is mandatory.

A landline phone number for the business' grievance officer.

Phone numbers must be provided with a + sign and the country code.

mobile_number

Either one of these contact methods (email, landline and mobile) is mandatory.

A mobile phone number for the business' grievance officer.

Phone numbers must be provided with a + sign and the country code.

Example On-premise payload:

{
      "entity_name": "NAME",
      "entity_type": "TYPE",
      "entity_type_custom": "",
      "is_registered": false,
      "customer_care_details": {
        "email": "EMAIL",
        "landline_number": "+00000000000",
        "mobile_number": "+00000000000"
      },
      "grievance_officer_details": {
        "name": "NAME",
        "email": "EMAIL",
        "landline_number": "+00000000000",
        "mobile_number": "+00000000000"
      }
}

Example Cloud API payload:

{
  "messaging_product": "whatsapp",
  "entity_name": "<ENTITY_NAME>",
  "entity_type": "<ENTITY_TYPE>",
  "is_registered": "<IS_REGISTERED>",
  "grievance_officer_details": {
    "name": "<GRIEVANCE_OFFER_NAME>",
    "email": "<GRIEVANCE_OFFER_EMAIL>",
    "landline_number": "<GRIEVANCE_OFFER_LANDLINE_NUMBER>",
    "mobile_number": "<GRIEVANCE_OFFER_MOBILE_NUMBER>"
  },
  "customer_care_details": {
    "email": "<CUSTOMER_CARE_EMAIL>",
    "landline_number": "<CUSTOMER_CARE_LANDLINE_NUMBER>",
    "mobile_number": "<CUSTOMER_CARE_MOBILE_NUMBER>"
  }
}

Retrieving Business Compliance Info

If the WABA is registered in Cloud API

Make a GET call to GET https://waba-v2.360dialog.io/business_compliance_info

If the WABA is registered in On-premise API

Make a GET call to GET https://waba.360dialog.io/v1/settings/business/compliance_info

A successful response includes the following information:

{
  "settings": {
    "business": {
      "compliance_info": {
      "customer_care_details": {
        "email": "EMAIL",
        "landline_number": "+00000000000",
        "mobile_number": "+00000000000"
        },
      "entity_name": "NAME",
      "entity_type": "TYPE",
      "entity_type_custom": "",
      "grievance_officer_details": {
          "email": "EMAIL",
          "landline_number": "+00000000000",
          "mobile_number": "+00000000000",
          "name": "NAME"
          },
      "is_registered": false,
      "meta": {
        "api_status": "stable",
        "version": "2.38.0"
        }
      }
    }
  }
}

More information is available in the Meta doc linked below:

single or multi-product messages
A customer_care_details object.
A grievance_officer_details object.
https://www.facebook.com/help/1104628230079278www.facebook.com
Meta doc: Comply with laws for selling online on WhatsApp Business Platform in India