> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getruba.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Map Ruba Events to Application Decisions
> Subscribe to the smallest set of state changes your application can act on
export const RubaSocials = () => {
if (typeof document === "undefined") {
return null;
}
const inject = () => {
const footer = document.getElementById("footer");
if (!footer || document.getElementById("ruba-socials")) {
return false;
}
const isDark = document.querySelector("html.dark") || document.querySelector('html[class*="dark"]');
const lineColor = isDark ? "#383838" : "#e8e8ed";
const iconColor = isDark ? "#8e8e93" : "#86868b";
const markColor = isDark ? "#ffffff" : "#08080c";
const hoverColor = "#0071e3";
const div = document.createElement("div");
div.id = "ruba-socials";
div.style.cssText = `display:flex;align-items:center;gap:20px;padding-top:20px;margin-top:20px;border-top:1px solid ${lineColor};width:100%`;
const logo = `Ruba`;
const spacer = ``;
const ig = ``;
const li = ``;
const x = ``;
const github = ``;
div.innerHTML = logo + spacer + ig + li + x + github;
footer.appendChild(div);
return true;
};
if (!document.documentElement.dataset.rubaSocialsObserver) {
document.documentElement.dataset.rubaSocialsObserver = "true";
const observer = new MutationObserver(() => {
if (!document.getElementById("ruba-socials")) {
inject();
}
});
observer.observe(document.body, {
childList: true,
subtree: true
});
}
setTimeout(() => {
if (!inject()) {
const interval = setInterval(() => {
if (inject()) {
clearInterval(interval);
}
}, 500);
setTimeout(() => clearInterval(interval), 10000);
}
}, 300);
return null;
};
Webhook names are grouped by the record that changed. Prefer outcome events such as `order.paid` for fulfillment, and use broad `updated` events only when the application genuinely needs every mutation.
## Customer and revenue lifecycle
### Before payment: checkout
A session reached expiry without completing.
### Customer identity and access snapshot
A customer record now exists.
Stored customer details changed.
The customer record was removed.
The combined access snapshot changed, including subscriptions or benefit grants.
### Recurring relationship
A recurring relationship was created; this alone does not prove collection.
Collection failed and the customer may recover by replacing the payment method.
Catch-all mutation signal also emitted around active, canceled, uncanceled, past-due, and revoked transitions.
Inspect `billing_reason` to distinguish `purchase`, `subscription_create`, `subscription_cycle`, and `subscription_update`. A renewal uses `subscription_cycle`.
#### Cancellation timelines
The default cancellation schedules the end of access at period end. Immediately after the customer or merchant requests it, Ruba emits:
1. `subscription.updated`
2. `subscription.canceled`
Both payloads show `active` with `cancel_at_period_end: true`. At period end, billing stops, benefits are removed, and Ruba emits:
3. `subscription.updated`
4. `subscription.revoked`
Those payloads show `canceled`. With immediate merchant revocation, the complete transition arrives together:
1. `subscription.updated`
2. `subscription.canceled`
3. `subscription.revoked`
All three payloads describe the now-canceled subscription.
#### Renewal timeline
At the renewal boundary, enabled endpoints first receive:
1. `subscription.updated`
2. `order.created`
The subscription carries its new `current_period_start` and `current_period_end`. The pending order contains the upcoming-cycle amount plus any prior-period usage. After successful collection, Ruba emits:
3. `order.updated`
4. `order.paid`
Both contain the order in `paid` state. Fulfillment should normally key off `order.paid`, not the earlier pending record.
### Collected transaction
### Returned money
### Customer entitlement
## Configuration lifecycle
### Benefit definitions
### Product catalog
### Organization settings