View as Markdown

llms.txt

The API reference isn't available right now

This instance couldn't load its API specification. The reference returns as soon as the specification is readable again.

Back to the API reference

No such model

This instance publishes no model under that name. It may have been renamed, or no operation this installation serves uses it.

Back to the API reference

This reference may be out of date

This instance couldn't reach its API specification on the last attempt, so this page shows the copy fetched before that. Anything added or changed since then is missing here, and the reference updates itself as soon as the specification is readable again. Last fetched 2026-10-26 23:26 UTC.

API reference Models

WalletMerchantOnboardingInput

A model the API reference uses in a request or a response. The operation pages link every field typed as this model here.

Optional richer onboarding details carried on a create/update DTO for wallet providers whose registration shape exceeds Apple's (Paze: structured address, merchant category code, self-assigned profile id). The merchant name is not here: every provider takes it from the shared `WalletProviderRegistrationCreateOrUpdateDtoBase.MerchantDisplayName`. One name per registration is deliberate, so Paze has no separate legal/trade name input. Provider-neutral by name. Null for Apple Pay, which uses only the flat identifier, display name, URL and domain fields.

Values

Values: Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.

Fields

Field Type Description
merchantCategoryCode required string Merchant category code, ISO 18245 (Paze `profile[].merchantCategoryCode`). nullablepattern ^[0-9]{4}$
Values: Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
profileId required string Self-assigned profile id. Optional: the provider generates a stable one when omitted. Paze is single-domain / single-profile (the HPP SDK initializes with one profile id), so there is exactly one profile id per registration. nullable
Values: Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
address required WalletMerchantAddressInput WalletMerchantAddressInput Business address (Paze `data.address`). Defaulted to a non-null instance so the create form's always-mounted Paze address fields can two-way-bind without a null-deref on the first render (see `WalletProviderRegistrationCreateOrUpdateDtoBase.Onboarding`). Conditional: When Address is not null.
Values: Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.

Fields of WalletMerchantAddressInput:

Field Type Description
line1 required string nullablemax length 256
Values: Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
line2 required string nullable
Values: Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
city required string nullablemax length 128
Values: Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
state required string nullablepattern ^US-[A-Z]{2}$
Values: Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
zipCode required string nullablemax length 16
Values: Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.

This body has no documented fields.

This model has no documented fields.

Reconnecting to the server

Could not reconnect

This session has ended

Attempt 1

Your work on this page is still here. Retrying keeps it; reloading starts the page again.

The server no longer holds this page's state, so it has to be loaded again.