Integrations
The Integrations page lets you connect external services that power your white-label platform. These include payment processing, email delivery, and authentication providers.
Payment Gateways
You need at least one active payment gateway so your clients can pay for plans and wallet recharges. Three providers are supported:
Razorpay
| Field | Description |
|---|---|
| Key ID | Your Razorpay API Key ID (starts with rzp_) |
| Key Secret | Your Razorpay API Key Secret |
| Webhook Secret | Secret for verifying Razorpay webhook signatures |
PhonePe
| Field | Description |
|---|---|
| Merchant ID | Your PhonePe Merchant ID |
| Salt Key | Your PhonePe Salt Key |
| Webhook Secret | Secret for verifying PhonePe callbacks |
PayU
| Field | Description |
|---|---|
| Merchant Key | Your PayU Merchant Key |
| Salt | Your PayU Salt value |
Managing Gateways
- Click Add to configure a new gateway
- Click Update to modify existing credentials
- Click the delete icon to remove a gateway
- Set one gateway as Default — this is used when clients make payments
Important: You must have at least one active payment gateway for clients to purchase plans. Without it, the checkout process will fail.
Google OAuth 2.0
Let your clients sign up and log in with their Google account on your white-labeled app.
Setup
| Field | Description |
|---|---|
| Google Client ID | Your Google OAuth 2.0 Client ID |
How to Get a Google Client ID
- Go to Google Cloud Console
- Create a new project or select an existing one
- Navigate to APIs & Services > Credentials
- Click Create Credentials > OAuth 2.0 Client ID
- Set application type to Web application
- Add your domain to Authorized JavaScript origins:
https://app.yourdomain.com(your custom domain)https://app.splashifypro.com(platform domain)
- Add to Authorized redirect URIs:
https://app.yourdomain.comhttps://app.splashifypro.com
- Copy the Client ID and paste it in the integration settings
Once configured, your clients see a Continue with Google button on login/signup pages that uses your Google project, showing your brand name in the Google consent screen.
SMTP Email
Configure a custom SMTP server to send transactional emails (OTP verification, ticket notifications, password resets) from your own email address.
Settings
| Field | Description |
|---|---|
| SMTP Host | Email server hostname (e.g., smtp.gmail.com) |
| SMTP Port | Server port (587 for TLS, 465 for SSL) |
| Username | SMTP login username (usually your email) |
| Password | SMTP login password or app-specific password |
| From Name | Sender name shown in emails (e.g., “WppBot Support”) |
| From Email | Sender email address |
| Enabled | Toggle to activate SMTP |
Testing
After saving SMTP settings, click Send Test Email to verify the configuration. A test email is sent to your registered email address.
Common SMTP Providers
| Provider | Host | Port |
|---|---|---|
| Gmail | smtp.gmail.com | 587 |
| Outlook | smtp-mail.outlook.com | 587 |
| Zoho | smtp.zoho.com | 587 |
| SendGrid | smtp.sendgrid.net | 587 |
Gmail Note: If using Gmail, you need to create an App Password — your regular Gmail password won’t work.
WhatsApp OTP
Send OTP verification codes to clients via WhatsApp during signup and login.
Settings
| Field | Description |
|---|---|
| Phone Number ID | Your WhatsApp Business phone number ID |
| Access Token | Permanent access token from Meta Developer Portal |
| Template Name | Name of the approved OTP template |
| Language Code | Template language (e.g., en_US) |
Testing
Click Send Test OTP to verify the configuration works. An OTP message is sent to a test number.
Note: WhatsApp OTP requires an approved message template on your WABA. Contact the platform admin if you need help setting this up.