Go Live

Once all features are tested and working in staging, you are ready to move to production. This guide covers getting your production credentials and deploying your integration.

Get Production Credentials

Contact the Hubble team or use the integration portal to obtain your production credentials:

• Production clientId — Your unique partner identifier for production
• Production appSecret — Your application secret for the production SDK URL
• Production X-Hubble-Secret — The secret for authenticating server-to-server calls
• Production Webhook Secret — The secret for verifying webhook signatures (if using webhooks)

Production vs. Staging Credentials

Production and staging credentials are completely separate. Using staging credentials in production (or vice versa) will result in authentication failures. Double-check that all credential references in your production deployment point to the correct environment.

What You Need to Update

When switching from staging to production, update the following in your application:

Setting	Staging Value	Production Value
SDK Base URL	sdk.dev.myhubble.money	sdk.myhubble.money
API Base URL	api.dev.myhubble.money	api.myhubble.money
clientId	Staging clientId	Production clientId
appSecret	Staging appSecret	Production appSecret
X-Hubble-Secret	Staging secret	Production secret

Production URL Registration

You must provide the Hubble team with your production backend URLs:

• Production Integration Base URL — The root URL for your SSO and coins APIs

  • Example: https://api.yourapp.com/hubble
  • Hubble will call /sso, /balance, /debit, and /reverse at this base URL

• Production Webhook URL — The endpoint where Hubble sends transaction and brand update webhooks

  • Example: https://api.yourapp.com/hubble/webhook

Separate Registration Required

Production URLs must be registered separately from staging URLs. Your staging SSO and webhook URLs will not work in production.

Steps to Go Live

1. Request Production Credentials

Contact the Hubble team to receive your production clientId, appSecret, and X-Hubble-Secret. These are different from your staging credentials.

2. Register Your Production URLs

Provide your production integration base URL (for SSO, coins APIs) and production webhook URL to the Hubble team.

3. Configure Environment Variables

Store production credentials in environment variables or a secrets manager — never hardcode them. Your code should switch between staging and production credentials based on the environment.

// Example: Environment-based configuration
const config = {
  sdkBaseUrl: process.env.NODE_ENV === 'production'
    ? 'https://sdk.myhubble.money'
    : 'https://sdk.dev.myhubble.money',
  apiBaseUrl: process.env.NODE_ENV === 'production'
    ? 'https://api.myhubble.money'
    : 'https://api.dev.myhubble.money',
  clientId: process.env.HUBBLE_CLIENT_ID,
  appSecret: process.env.HUBBLE_APP_SECRET,
  hubbleSecret: process.env.HUBBLE_SECRET,
};

4. Deploy Your Backend

Ensure your SSO endpoint, coins APIs (if applicable), and webhook endpoint are deployed and publicly accessible on your production domain.

Verify that:

• HTTPS is enabled with TLS 1.2 or higher
• The X-Hubble-Secret validation uses the production secret
• Webhook signature verification uses the production webhook secret

5. Update the SDK URL

Switch the SDK URL from the staging domain to the production domain:

- const sdkUrl = `https://sdk.dev.myhubble.money/?clientId=${clientId}&appSecret=${appSecret}&token=${token}`;
+ const sdkUrl = `https://sdk.myhubble.money/?clientId=${clientId}&appSecret=${appSecret}&token=${token}`;

6. Verify Theme and Catalog

Open the SDK in production and verify that:

• Your theme customization is applied correctly
• The brand catalog matches what you tested in staging
• Discount configurations are correct

7. End-to-End Test

Perform a complete purchase flow on a real device in production to confirm everything works end-to-end:

1. Open the SDK with a valid SSO token
2. Browse brands and select a gift card
3. Complete a real purchase (small amount)
4. Verify the voucher is delivered
5. Check that SDK events are received
6. Check that webhooks are received
7. (If applicable) Verify coins were debited correctly

---

Post-Launch Monitoring

After going live, set up monitoring to detect issues early:

Key Metrics to Track

Metric	What It Indicates
payment_success / payment_initiated ratio	Payment success rate. A drop indicates payment gateway or configuration issues.
Webhook delivery success rate	Reliability of transaction notifications
SSO error rate	Authentication health
Voucher generation failure rate	Gift card delivery issues

Recommended Alerts

• Payment success rate drops below 90% — May indicate payment gateway issues
• Webhook delivery failures — Your endpoint may be down or misconfigured
• SSO error spike — Token generation or validation issues
• Voucher generation failures increase — Brand-side or Hubble-side issues

Build a Monitoring Dashboard

Track the ratio of payment_initiated to payment_success events to monitor your payment success rate. A sudden drop in this ratio can indicate payment gateway issues, UPI configuration problems, or SDK integration bugs. Setting up an alert on this metric is one of the highest-value monitoring actions you can take.

---