Skip to content

// e-commerce and billing

Via API

BigCommerce email verification with pingutil

BigCommerce webhooks tell you an order or customer was created but carry only its id, so nothing checks the address the buyer typed. A handler that fetches the order, verifies the billing email with pingutil and writes the result to staff notes gives your team a clear warning before a confirmation or invoice disappears.

Where it connects: BigCommerce webhooks (store/order/created, store/customer/created) plus the Orders v2 API staff_notes field

What goes wrong without it

  • B2B buyers mistype their work address and our invoices bounce until someone calls them.
  • New customer accounts with temp-mail addresses keep claiming the welcome coupon.
  • Support cannot tell whether "I never got my receipt" is a spam folder or an address that does not exist.

What you can do with BigCommerce and pingutil

  • Warn staff on the order

    Write a line like "pingutil: invalid (mailbox_not_found)" into staff_notes, which appears on the order in the control panel but not to the shopper.

  • Separate business buyers from personal accounts

    For B2B stores, a /v1/lookup call returns category company with a company profile, or free for webmail. Use it to route new customers to a sales rep.

  • Review welcome-coupon abuse

    Flag new customers whose address comes back disposable or with verdict.is_spam before approving a customer group or a coupon.

Set it up

  1. 1

    Create an API key in the pingutil dashboard, and a BigCommerce API account with read and modify access to Orders.

  2. 2

    Create webhooks for store/order/created (and store/customer/created if you want account checks) with a custom headers object holding a shared secret.

  3. 3

    In the handler, check the secret header, respond 200 immediately, then process the event.

  4. 4

    Fetch the order with GET /v2/orders/{id} to read billing_address.email.

  5. 5

    Call pingutil /v1/verify and write a summary to the order staff_notes with PUT /v2/orders/{id}.

Webhook handler for store/order/created
import express from 'express';

const app = express();
const STORE = process.env.BC_STORE_HASH;
const BC = { 'X-Auth-Token': process.env.BC_ACCESS_TOKEN, accept: 'application/json', 'content-type': 'application/json' };

app.post('/webhooks/bigcommerce', express.json(), (req, res) => {
  // The secret is the custom header you set when creating the webhook.
  if (req.get('x-webhook-secret') !== process.env.BC_WEBHOOK_SECRET) return res.sendStatus(401);
  res.sendStatus(200);
  if (req.body.scope === 'store/order/created') checkOrder(req.body.data.id).catch(console.error);
});

async function checkOrder(orderId) {
  const base = 'https://api.bigcommerce.com/stores/' + STORE + '/v2/orders/' + orderId;
  const order = await (await fetch(base, { headers: BC })).json();
  const email = order.billing_address && order.billing_address.email;
  if (!email) return;

  let result;
  try {
    const res = await fetch('https://pingutil.com/v1/verify', {
      method: 'POST',
      headers: { authorization: 'Bearer ' + process.env.PINGUTIL_KEY, 'content-type': 'application/json' },
      body: JSON.stringify({ email }),
      signal: AbortSignal.timeout(30000),
    });
    if (!res.ok) return; // fail open
    result = await res.json();
  } catch {
    return;
  }
  if (result.status === 'valid') return;

  let note = 'pingutil: ' + result.status + ' (' + result.reason + ')';
  if (result.did_you_mean) note += '. Suggested: ' + result.did_you_mean;
  const staff_notes = [order.staff_notes, note].filter(Boolean).join('\n');
  await fetch(base, { method: 'PUT', headers: BC, body: JSON.stringify({ staff_notes }) });
}

app.listen(3000);

What to do with each result

pingutil resultAction in BigCommerce
status: "invalid"Add a staff note and contact the buyer by phone before relying on email for invoices or shipping.
did_you_mean is setPut the suggestion in the staff note so staff can correct the customer email.
checks.disposable: trueHold coupon-driven or high-value orders for a manual look.
category: "company" (from /v1/lookup)Assign the customer to a B2B customer group or notify the account owner.
status: "risky" or "unknown"Leave a note only, do not cancel.

Limits to plan for

  • BigCommerce webhook payloads carry only the resource id, so every event costs one API call back to the store before you can verify.
  • BigCommerce retries failed callbacks and blocklists a destination whose success rate drops below 90 percent, so answer 200 before calling pingutil.
  • pingutil verifies up to 300 addresses a day (3,000 a month) per account and 60 requests a minute. Queue checks on stores with large order spikes. Those are Free plan limits; Enterprise has custom limits.

BigCommerce documentation

BigCommerce is a trademark of its owner. This integration uses BigCommerce's documented extension points; it is not an official BigCommerce app.

Common questions

Does BigCommerce sign webhook payloads?
Its webhook docs describe securing callbacks with custom headers you set when creating the webhook, such as a shared secret or basic auth credentials. Check that header before doing any work.
Can I check addresses before the order is placed?
Only from your own storefront code, for example a headless checkout calling your backend, which calls pingutil. Webhooks fire after creation.

Stop bad addresses in BigCommerce today

Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your BigCommerce setup will receive.