Managed cards

Card payment update

Sent each time a card payment (the aggregate of related authorizations, settlements, reversals, refunds, and original credits) is created or updated. The payload carries the full current state of the CardPayment, including its complete event history with running-total snapshots after each event.

Use this instead of subscribing to the per-event-type webhooks — Card authorization, Card settlement — when you want to track the overall card payment from a single webhook.

Enable and configure webhooks in the Embedder Portal; recent events are listed on its Webhook Logs page. Weavr sends this event to {Webhook URL}/managed_cards/payments/watch.

postWebhook/managed_cards/payments/watch

Headers

call-refstring

A call reference generated by the caller and unique to the caller to provide correlation between the caller and system with a maximum length of 255

published-timestampinteger required

The timestamp, expressed in Epoch timestamp using millisecond precision, when this event was published.

signaturestring required

The signature to verify the authenticity of this request. This is the base64 hash (HmacSHA256) of the published-timestamp using your API key.

signature-v2string required

The signature to verify the authenticity of this request. This is the base64 hash (HmacSHA256) of the call-ref + payload + published-timestamp using your API key.

Payload

eventType'AUTHORISATION' | 'SETTLEMENT' | 'REFUND' | 'ORIGINAL_CREDIT' required

Type of event recorded against a CardPayment. The reversal flag on each event distinguishes a reversal from the original action.

Example payload

{
  "cardPayment": {
    "id": "123456789",
    "profileId": "10001",
    "card": {
      "id": "234567890",
      "friendlyName": "Travel card",
      "nameOnCard": "Alex Smith",
      "cardNumberFirstSix": "453201",
      "cardNumberLastFour": "0366",
      "linkedUserId": "987654321",
      "parentManagedAccountId": "123456789"
    },
    "merchant": {
      "id": "MID123456",
      "name": "Coffee Corner",
      "nameOther": "Coffee Corner Ltd",
      "networkId": "NET123456",
      "categoryCode": "5812",
      "description": "Coffee shop",
      "street": "1 High Street",
      "city": "London",
      "state": "Greater London",
      "postalCode": "W1A 1AA",
      "country": "GB",
      "telephone": "+442079460000",
      "url": "https://www.coffeecorner.example",
      "contact": "info@coffeecorner.example",
      "reference": "ORD-20260803-0001",
      "logoUrl": "https://www.coffeecorner.example/logo.png"
    },
    "displayAmount": {
      "currency": "GBP",
      "amount": 1250
    },
    "relatedCardPaymentId": "987654321",
    "creationTimestamp": 1786118400000,
    "lastUpdatedTimestamp": 1786118401250
  }
}

Response

Event received.

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.