Migrate to Pine Labs Payment Gateway

Move from your current payment gateway to Pine Labs Online without losing customers, transaction history, or uptime.

What you're building

By the end of this guide, you'll have:

• A migration plan tailored to your current setup
• Pine Labs integration running in parallel with your existing gateway
• Customers transitioned smoothly with no payment disruption
• Full operational readiness on Pine Labs Online

Before you begin

Migration overview

Phase 1 — Plan & prepare

Audit your current setup

Document what you're migrating:

Map features to Pine Labs equivalents

Get Pine Labs credentials

1. Sign up for a Pine Labs Online account
2. Complete KYC verification
3. Get UAT credentials from Dashboard → Settings → API Keys

Screenshot: Dashboard → Settings → API Keys — Your migration starts here

Phase 2 — Integrate Pine Labs

Update your backend

Replace your current gateway's API calls with Pine Labs equivalents:

Example: Replacing a checkout flow

Before (generic gateway):

// Old gateway
app.post('/checkout', async (req, res) => {
  const session = await oldGateway.createSession({
    amount: req.body.amount,
    currency: 'INR',
    successUrl: '/success',
    cancelUrl: '/cancel'
  });
  res.redirect(session.url);
});

After (Pine Labs Online):

// Pine Labs Online
app.post('/checkout', async (req, res) => {
  // Generate token
  const token = await getPineLabsToken();

  // Create order
  const order = await axios.post(
    'https://pluraluat.v2.pinepg.in/api/pay/v1/orders',
    {
      merchant_order_reference: `MIG-${Date.now()}`,
      order_amount: { value: req.body.amount, currency: 'INR' },
      pre_auth: false,
      allowed_payment_methods: ['CARD', 'UPI', 'NETBANKING', 'WALLET'],
      callback_url: 'https://your-domain.com/success',
      failure_callback_url: 'https://your-domain.com/cancel',
      purchase_details: {
        customer: {
          email_id: req.body.email,
          first_name: req.body.name,
          mobile_number: req.body.phone,
          country_code: '91'
        }
      }
    },
    {
      headers: {
        'Authorization': `Bearer ${token}`,
        'Content-Type': 'application/json',
        'Request-ID': crypto.randomUUID(),
        'Request-Timestamp': new Date().toISOString()
      }
    }
  );

  res.redirect(order.data.checkout_url);
});

Update webhook handlers

Map your existing webhook events to Pine Labs events:

E-commerce plugin migration

If you're using a platform plugin:

Phase 3 — Test on UAT

Run your full payment lifecycle on the Pine Labs UAT environment:

Phase 4 — Parallel run

Run both gateways simultaneously to de-risk the migration:

Recommended rollout

What to monitor during parallel run

Phase 5 — Full cutover

Once the parallel run is stable:

1. Switch 100% traffic to Pine Labs Online
2. Update production credentials — replace UAT URLs with production
3. Configure production webhooks — point to live endpoints
4. Verify first live transactions — make a real payment and refund
5. Update monitoring — point alerts to Pine Labs Dashboard

Go live checklist

• Production base URL: https://api.pluralonline.com
• Production Client ID and Client Secret configured
• Production webhook endpoints registered
• Signature verification working with production keys
• TLS 1.2+ enforced on all API calls
• Error handling tested for all payment methods
• Settlement bank account verified
• Statement descriptor configured

Phase 6 — Decommission old gateway

After running successfully on Pine Labs for 2–4 weeks:

Migrating subscriptions

Active subscriptions require special handling:

Option A: Gradual migration (recommended)

1. Stop creating new subscriptions on the old gateway
2. Create new subscriptions on Pine Labs
3. As old subscriptions come up for renewal, migrate them to Pine Labs
4. Notify customers of the payment processor change

Option B: Bulk migration

1. Export all active subscriptions from the old gateway
2. Create corresponding plans and subscriptions on Pine Labs
3. Send customers a one-time authorization for the new processor
4. Cut over all subscriptions simultaneously

Customer communication: Always inform customers when changing payment processors. A simple email explaining the transition prevents confusion and disputes.

FAQ

Need help with migration?

For complex migrations or enterprise setups, Pine Labs offers dedicated migration support:

• Email: pgsupport@pinelabs.com
• Migration support team: Contact your account manager for a dedicated migration engineer
• Technical documentation: API Reference

Next steps

• Quickstart Guide — core API concepts
• Checkout options — choose the right integration type
• Webhooks — configure payment event notifications
• Dashboard — monitor your payments