GitHub Start free

What does the RevenueDot webhook event TRANSFER mean?

The RevenueDot webhook event TRANSFER means a purchase moved from one customer to another because the second customer restored it.

Quick facts#
Event TRANSFER
Where RevenueDot webhook (event.type), RevenueCat's webhook format
Sent to Every enabled webhook whose filters match
Fields that are specific to it transferred_from, transferred_to
What it means A purchase moved to another customer because that customer restored it (transfer behaviour transfer or transfer_if_no_active).

When it is sent#

  • A customer restored purchases on a new app user id, and the project's transfer behaviour moves the purchase to that id.
  • transferred_from and transferred_to list the app user ids of both customers.
  • Besides these, the event has only store and environment and the subscriber attributes.

What your server should do#

  1. Move the entitlement in your own database from the transferred_from ids to the transferred_to ids.
  2. Do not treat it as a purchase: no money moves.
  3. Check the project's transfer behaviour if transfers surprise you.
  4. Deduplicate on event.id: deliveries can repeat, because anything but HTTP 200 is retried after 5, 10, 20, 40 and 80 minutes.

Example#

JavaScript
import { createHmac, timingSafeEqual } from "node:crypto";

// X-RevenueCat-Webhook-Signature: t=<unix seconds>,v1=<hex HMAC-SHA256 of "<t>.<raw body>">
function verify(rawBody, header, secret, toleranceSeconds = 300) {
  const m = /^t=(\d+),v1=([0-9a-f]{64})$/.exec(header ?? "");
  if (!m || Math.abs(Date.now() / 1000 - Number(m[1])) > toleranceSeconds) return false;
  const expected = createHmac("sha256", secret).update(`${m[1]}.${rawBody}`).digest();
  return timingSafeEqual(expected, Buffer.from(m[2], "hex"));
}

// Sign a sample delivery the way RevenueDot does, then handle it.
const secret = "whsec_test_secret";
const rawBody = JSON.stringify({ api_version: "1.0", event: {"id":"66339910-3BFF-49F4-B873-D1283D673DE2","type":"TRANSFER","app_user_id":"user_1","product_id":"pro_monthly","transferred_from":["$RCAnonymousID:a"],"transferred_to":["user_1"]} });
const t = Math.floor(Date.now() / 1000);
const header = `t=${t},v1=${createHmac("sha256", secret).update(`${t}.${rawBody}`).digest("hex")}`;

const seen = new Set(); // use a database table in production

function handle(rawBody, header) {
  if (!verify(rawBody, header, secret)) return "401 bad signature";
  const { event } = JSON.parse(rawBody);
  if (seen.has(event.id)) return "200 duplicate";
  seen.add(event.id);
  if (event.type !== "TRANSFER") return "200 ignored";
  return "move the entitlement from " + event.transferred_from.join(",") + " to " + event.transferred_to.join(",");
}

console.log(handle(rawBody, header));

Run-checked: npm run check:snippets runs this snippet with Node and compares its output with from $RCAnonymousID:a to user_1 (checked 2026-10-03).

How RevenueDot produces it#

When a purchase's owner changes, recordTransfer in services/purchases.ts records TRANSFER with the app user ids of both customers. A transfer made through the customer-extras API records it too.

Source#

Checked: 2026-10-03

Edit this page on GitHub ↗ View as Markdown Last updated