OptionalbillingAVS data for customer-present ("initial") charges — Paysafe rejects them without a zip (error 3004) when the stored token originated from browser tokenization. Merchant-initiated follow-ups don't need it.
OptionalidHost-app payment id, round-tripped via PSP metadata where supported.
OptionalmetadataOptionaloccurrenceCredential-on-file semantics: "initial" for the first charge in an agreement while the customer is present, "recurring" (default) for merchant-initiated follow-ups, "unscheduled" for irregular one-offs (top-ups). Networks require honest flags here.
SavedPaymentMethod.token (or PaymentInfo.savedPaymentMethodToken).
Optionalstatement
Off-session charge of a vaulted instrument — the primitive under recurring payments. No client, no card fields: the server charges the stored token.