Monitoring & alerts

Payment failures, webhook backlogs, and disputes rarely announce themselves — they show up as a slow drift in your numbers. This page covers the metrics VINR exposes, how to wire them into alerts, and how to keep webhook delivery healthy so you find out before your customers do.

Key metricsAskCopy

VINR computes rolling metrics across your account and exposes them through the Metrics API and the dashboard. Each metric is a time series you can window by minute, hour, or day.

import { Vinr } from '@vinr/sdk';
const vinr = new Vinr({ secretKey: process.env.VINR_SECRET_KEY });

// Pull the last 24h of authorization rate, bucketed hourly.
const series = await vinr.metrics.query({
  metric: 'payments.authorization_rate',
  interval: 'hour',
  start: '2026-05-29T00:00:00Z',
  end: '2026-05-30T00:00:00Z',
});

for (const point of series.points) {
  console.log(point.timestamp, point.value); // value is 0.0 - 1.0
}

Configuring alertsAskCopy

An alert binds a metric to a threshold and a delivery channel. When the metric crosses the threshold for the configured window, VINR opens an alert, notifies your channels, and emits an event you can act on programmatically.

const alert = await vinr.alerts.create({
  metric: 'payments.decline_rate',
  condition: { operator: 'gt', threshold: 0.15 }, // 15%
  window: '15m',                                   // sustained for 15 minutes
  channels: ['we_slack_ops', 'email:ops@acme.com'],
  severity: 'high',
});
// VINR emits "alert.triggered" and "alert.resolved" as the metric crosses.

Webhook delivery healthAskCopy

Most operational blind spots are really webhook blind spots — if your endpoint silently fails, your systems drift out of sync with VINR. Monitor delivery the same way you monitor payments.

const failures = await vinr.webhooks.deliveries.list({
  endpoint: 'we_1a2b3c',
  status: 'failed',
  limit: 20,
});
// Each delivery includes the response code, body, and attempt count.

curl -X POST https://api.vinr.com/v1/webhooks/deliveries/replay \
  -H "X-Api-Key: $VINR_SECRET_KEY" \
  -d 'endpoint=we_1a2b3c' \
  -d 'since=2026-05-30T08:00:00Z'

Incident responseAskCopy

When an alert fires, the goal is to triage fast and avoid making things worse.

1. Confirm scope. Open the alert in the dashboard and check whether the metric moved account-wide or for a single payment method, currency, or region.
2. Check the status page. Rule out a VINR-side incident (below) before chasing your own integration.
3. Mitigate. For collection failures, let dunning run rather than retrying manually. For webhook outages, fix the endpoint and replay.
4. Resolve. VINR auto-resolves the alert and emits alert.resolved once the metric returns within threshold for the window. Record the root cause in your own runbook.

Status pageAskCopy

VINR publishes platform health at status.vinr.com, covering the API, dashboard, webhook delivery, and settlement processing. Subscribe there for component-level incident notifications, and consume the machine-readable feed if you want to suppress your own alerts during a known upstream incident.

curl https://api.vinr.com/v1/status \
  -H "X-Api-Key: $VINR_SECRET_KEY"
# { "api": "operational", "webhooks": "degraded", ... }

Next stepsAskCopy