PAS Vendor eSIM Webhook Integration: Duck Creek, Guidewire & Majesco (2026)

Field mapping across the three PAS platforms

Insurer-side middleware pattern

A thin translator layer normalizes each PAS's event into a common shape, then routes to the shared provisioning function. Same insurers already run this for TMC + analytics integrations.

// middleware/normalize.ts
interface NormalizedPolicyEvent {
  policyNumber: string;
  destinationCountry: string;
  tripDurationDays: number;
  policyholderEmail: string;
  eventType: 'issued' | 'cancelled';
}

export function normalizeDuckCreek(payload: any): NormalizedPolicyEvent {
  return {
    policyNumber: payload.data.policyNumber,
    destinationCountry: payload.data.trip.destinationCountry,
    tripDurationDays: payload.data.trip.durationDays,
    policyholderEmail: payload.data.policyholder.email,
    eventType: payload.type === 'policy.issued' ? 'issued' : 'cancelled',
  };
}

export function normalizeGuidewire(payload: any): NormalizedPolicyEvent {
  return {
    policyNumber: payload.policyRef,
    destinationCountry: payload.policy.trip.destCountry,
    tripDurationDays: payload.policy.trip.days,
    policyholderEmail: payload.insured.contact.email,
    eventType: payload.eventType === 'PolicyBound' ? 'issued' : 'cancelled',
  };
}

export function normalizeMajesco(payload: any): NormalizedPolicyEvent {
  return {
    policyNumber: payload.PolicyKey,
    destinationCountry: payload.PolicyDetails.TripDestination,
    tripDurationDays: payload.PolicyDetails.TripDurationDays,
    policyholderEmail: payload.Policyholder.EmailAddress,
    eventType: payload.EventName === 'PolicyIssuedEvent' ? 'issued' : 'cancelled',
  };
}

Shared downstream provisioning function

// provisioning/esim.ts — same for all three PAS platforms
export async function provisionEsimForPolicy(evt: NormalizedPolicyEvent) {
  if (evt.eventType === 'cancelled') {
    const esimOrderId = await lookupEsimForPolicy(evt.policyNumber);
    if (esimOrderId) {
      await fetch(`https://api.yonosim.com/v1/orders/${esimOrderId}/refund`, {
        method: 'POST',
        headers: { Authorization: `Bearer ${process.env.YONOSIM_API_KEY}` },
      });
    }
    return;
  }

  // eventType === 'issued'
  const res = 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-${evt.policyNumber}`,
    },
    body: JSON.stringify({
      planId: pickPlanForDestination(evt.destinationCountry, evt.tripDurationDays),
      customerEmail: evt.policyholderEmail,
      metadata: { policyNumber: evt.policyNumber },
    }),
  });
  const order = await res.json();
  await storeEsimForPolicy(evt.policyNumber, order.id, order.activationUrl);
  await triggerPolicyPdfRegen(evt.policyNumber, order);
}

FAQ

Bottom line

The three biggest PAS platforms — Duck Creek, Guidewire, Majesco — all support outbound webhooks natively. Adding eSIM provisioning is field-mapping work in a thin middleware layer, then a shared downstream function that calls the YonoSIM API. 2–3 engineer-weeks per PAS. The playground at api.yonosim.com/docs validates the YonoSIM side; the PAS side is your team's mapping work. Back to the Travel insurance hub.