Payment Services Data & Events

The Payment Services drop-in does not define its own namespaced events (for example, payment-services/…) for vault or payment UI. Instead, checkout integrations typically use the Checkout drop-in’s values and events. See the Vaulted cards at checkout tutorial for how the Commerce boilerplate combines StoredCards and CreditCard.

Network errors and the error event

GraphQL requests used in vault flows (for example, loading customer payment tokens) can share a common fetch error handler. If a request fails—and the error is not due to an abort—the handler can emit the global error event on the Adobe Commerce event bus with a payload such as:

{
  "source": "payment-services",
  "type": "network",
  "error": { }
}

Subscribe to error if you need to correlate network failures with Payment Services. For broader patterns, see Common events.

Note

There is no separate catalog of Payment Services–specific event names for stored-card selection or card form state. Instead, the host block coordinates the containers and cart APIs.