Update settings
Upload your Apple identity so Guardian can generate CSRs, serve the domain-association file, and validate merchant sessions. Provide your merchant_identifier, a display_name, the byte-exact domain_association_content Apple issued, and the csr_common_name to embed in generated CSRs.
The upload is a partial update: fields you omit keep their current values, and no field is individually required. All four must be set before the dependent flows work.
Available only on self_managed instances. On Starfish-operated (sf_operated) instances the Apple identity and certificates are managed by Starfish, and this endpoint returns 409 with the classifier APPLE_PAY_CERT_MANAGEMENT_UNAVAILABLE.
Authorizations
Body
The Apple identity Guardian uses on a self_managed instance. Every field is optional per request; omitted fields keep their current values.
Your Apple Pay merchant identifier.
"merchant.com.example"
The merchant display name shown in the Apple Pay sheet.
"Example Store"
The byte-exact body of the Apple-issued domain-association file, served verbatim at /.well-known/apple-developer-merchantid-domain-association.txt.
The common name (CN) to embed in the certificate signing requests Guardian generates.
"Example Store"
Response
Success response
The operating mode of this instance. self_managed means you upload and manage your own Apple identity and certificates; sf_operated means Starfish operates the Apple Developer relationship and mounts the identity and certificates.
self_managed, sf_operated "merchant.com.example"
"Example Store"
The body of the domain-association file served at /.well-known/apple-developer-merchantid-domain-association.txt.
"Example Store"