New: MCP server monitoring is live. Start free trial
MollieSchemaAdditive

Enum values changed in GET /v2/customers/{customerId}/payments (payment-details-wallet-response)

Affected surface
GET /v2/customers/{customerId}/payments
Affected field
payment-details-wallet-response

What changed

Enum values changed in GET /v2/customers/{customerId}/payments (payment-details-wallet-response) Affected surface: GET /v2/customers/{customerId}/payments. Root cause: schema `payment-details-wallet-response`. Detected at Tue, 09 Jun 2026 17:00:28 UTC UTC.

Diff

{
  "added_enums": [
    "googlepay"
  ],
  "path": "GET /v2/customers/{customerId}/payments",
  "schema_path": "schema payment-details-wallet-response"
}

Likely impact

This is an additive change. Existing integrations are unaffected; this is mostly useful if you want to take advantage of the new surface.

Audit any switch/match statements over this enum. Removed values become unhandled paths.

Catch changes like this on every API you depend on.

Intello monitors 100+ APIs and tells you the moment something changes — before it breaks production.