The documentation you point to is silent on whether this feature generates credit risk for a merchant - i.e. when the customer cancels their account what happens:

- The currently recorded/logged usage is charged before the cancellation is processed?

- Can a merchant allow their users (i.e. the merchant's client) to specify a cap on their usage charges?

- Can the vendor provide a webhook endpoint to receive account CRUD notifications, and be given a window (likely just seconds) in which to update the usage record.