Skip to main content
PUT
Manage public payment acceptance
Set publicReceiveEnabled to turn the UPA’s reusable public payment page on or off. Enabling it requires all three of: an active qualified payment handle, an eligible preferred settlement destination, and an enabled app-level public Payment policy. Send the account’s current paymentAcceptance.version (from the account bundle) as expectedVersion, and a reason of 10 to 500 characters. If the setting was changed by another request in the meantime, the call returns 409. Public crypto receiving does not require KYC by default. Existing Payments stay immutable when this setting changes. Payers’ browsers read the page through Resolve a public payment page.

Authorizations

Authorization
string
header
required

HTTP Basic auth. Username is the Stableyard app ID. Password is the app secret. The optional Stableyard-Version request header must match the environment pin.

Headers

Stableyard-Version
enum<string>

Optional contract-version assertion. Omit it to use the app environment's pinned version. A different supported version is accepted only after that environment is explicitly migrated.

Available options:
2026-09-09

Path Parameters

accountId
string
required

Canonical account id returned by the Accounts API.

Example:

"acct_123"

Body

application/json
publicReceiveEnabled
boolean
required
expectedVersion
integer
required
Required range: x >= 0
reason
string
required
Required string length: 10 - 500

Response

Updated account bundle

account
object
required
connectedWallets
object[]
required
paymentHandle
object
settlementProfile
object