Trip-Insurance PDF eSIM QR: The 15-Minute Integration for Policy Admin Systems (2026)

Integration flow (three nodes)

1. PAS fires policy.issued webhook to your middleware.
2. Your middleware extracts destination + dates, calls POST /v1/orders, gets back activationUrl + qrCodeUrl.
3. Your PDF renderer injects the URL/QR into the policy PDF template + emails to policyholder.

Full handler (~40 lines)

// on-policy-issued.ts
import crypto from 'crypto';

export async function POST(req: Request) {
  const raw = await req.text();
  const sig = req.headers.get('x-pas-signature') ?? '';
  const expected = crypto
    .createHmac('sha256', process.env.PAS_WEBHOOK_SECRET!)
    .update(raw)
    .digest('hex');
  if (!crypto.timingSafeEqual(Buffer.from(sig), Buffer.from(expected))) {
    return new Response('bad signature', { status: 401 });
  }

  const event = JSON.parse(raw);
  if (event.type !== 'policy.issued') return new Response('ok');

  const destination = event.data.trip.destinationCountry;   // 'ES'
  const tripDays = event.data.trip.durationDays;             // 10
  const policyholder = event.data.policyholder.email;
  const policyNumber = event.data.policyNumber;

  // Provision the eSIM
  const yonoRes = await fetch('https://api.yonosim.com/v1/orders', {
    method: 'POST',
    headers: {
      'Authorization': `Bearer ${process.env.YONOSIM_API_KEY}`,
      'Content-Type': 'application/json',
      'Idempotency-Key': `policy-${policyNumber}`,
    },
    body: JSON.stringify({
      planId: pickRegionalPlan(destination, tripDays),   // eu_5gb_30d for ES
      customerEmail: policyholder,
      metadata: { policyNumber, insurer: 'acme_ins' },
    }),
  });
  const order = await yonoRes.json();

  // Trigger PDF generation with the activation URL variable
  await regeneratePolicyPdf(policyNumber, {
    esimActivationUrl: order.activationUrl,
    esimQrPngUrl: order.qrCodeUrl,
    esimIccid: order.iccid,
  });
  return new Response('ok');
}

PDF template snippet

In your PAS PDF template (Duck Creek, Guidewire, or plain HTML→PDF via Puppeteer/WeasyPrint), add a Schedule of Benefits section variable for the eSIM:

<!-- Schedule of Benefits — Connectivity Bundle -->
<h3>International Data Connectivity</h3>
<p>Your policy includes 5 GB of international mobile data
valid for 30 days at your destination.</p>

<div class="esim-activation">
  <img src="{{esimQrPngUrl}}" alt="Install eSIM" width="180" height="180" />
  <p>Scan QR to install, or visit:<br>
    <strong>{{esimActivationUrl}}</strong></p>
  <p class="fine-print">ICCID: {{esimIccid}}</p>
</div>

Cancellation handling (~20 lines)

// on-policy-cancelled.ts
export async function POST(req: Request) {
  // ... signature verification ...
  const event = JSON.parse(raw);
  if (event.type !== 'policy.cancelled') return new Response('ok');

  const esimOrderId = await lookupEsimForPolicy(event.data.policyNumber);
  if (!esimOrderId) return new Response('no esim to refund');

  await fetch(`https://api.yonosim.com/v1/orders/${esimOrderId}/refund`, {
    method: 'POST',
    headers: { Authorization: `Bearer ${process.env.YONOSIM_API_KEY}` },
  });
  // order.refunded webhook fires — insurer's ledger is credited
  return new Response('ok');
}

Total size + timeline

Policy-issued handler: 40 lines. Cancellation handler: 20 lines. PDF template variable: 10 lines. YonoSIM webhook listener for order.refunded → insurer ledger: 20 lines. Total: ~90 lines. Timeline: 2–3 engineer-weeks under standard PAS release cadence.

FAQ

Bottom line

Adding an eSIM to a trip-insurance policy PDF is ~90 lines of code and 2–3 engineer-weeks — well within a single PAS release cycle. The sandbox at api.yonosim.com/docs lets you validate the full lifecycle including auto-refund before writing the integration ticket. Back to the Travel insurance hub.