Disclosure information and coverage

A ready disclosure contains data.payment_arrangements. Iterate over the entire array: a disclosure can contain more than one arrangement. Each arrangement can include the payment service provider's legal name and other available identity details, merchant identifier (MID), virtual POS identifier (TID), settlement arrangement, currency, payment methods, receiving accounts, and a supporting accepted agreement. Treat identifiers as strings to preserve leading zeros. Agreement documents are references to accepted documents, not download grants; a public URL is included when available.

Receiving-account numbers is a typed object: scheme can be iban, aba, sort_code, or eft, with the fields for that scheme described in the API reference. Authorized retrieval can return complete bank identifiers. numbers_redacted is true when numbers are unavailable. Restrict access to this information, avoid logging it, and store or share it only where needed.

Coverage

coverage.scope is paypercut_managed_payment_information. complete means the information is complete within that scope; it does not determine all of the merchant's obligations. incomplete means one or more facts in that scope are unavailable or unverified. The ready disclosure and its PDF remain available. Review each issue and any available information before using it. Once information is corrected, create a fresh disclosure.

Issue code	Meaning and next step
`merchant_identifier_missing`	The MID is unavailable. Check your payment setup or contact support to have it reviewed.
`virtual_pos_identifier_missing`	The virtual POS identifier is unavailable. Check your payment setup or contact support.
`accepted_agreement_missing`	An accepted agreement reference is unavailable. Check the agreement status; contact support if it should be present.
`contractual_psp_ambiguous`	The contractual payment service provider could not be identified unambiguously. Contact support to review the agreement.
`contractual_party_attributes_not_retained`	Some contractual party details were not retained. Contact support for help confirming them.
`source_provenance_incomplete`	The available information does not establish all necessary references. Contact support to review the affected information.
`provider_outside_supported_scope`	A provider arrangement is outside the supported information scope. Obtain the relevant information from that provider.
`paynetics_reference_missing`	A Paynetics reference needed for the arrangement is unavailable. Contact support.
`payout_profile_missing`	Payout configuration is unavailable. Check your payout setup or contact support.
`payout_active_version_missing`	The active payout configuration is unavailable. Check your payout setup or contact support.
`payout_destination_missing`	The receiving destination is unavailable. Check the receiving account configuration or contact support.
`receiving_account_selection_unresolved`	The receiving account could not be selected unambiguously. Check the receiving account configuration or contact support.
`banking_scheme_unsupported`	The receiving account's banking scheme is not supported for this information. Contact support and obtain the information separately.
`bank_identification_incomplete`	Required bank identification details are unavailable. Check your receiving account details or contact support.
`receiving_currency_support_unresolved`	Paypercut could not verify the required receiving-account currency support from the available information. This does not mean the account is invalid. Check the account's supported currencies or contact support.

Some issues require Paypercut's help and may not be directly resolvable by the merchant. Do not assume that updating a setting resolves every issue.

Request errors

Errors use the Paypercut error object, including type and message and, when available, code, param, and trace_id. See error handling.

HTTP status	Action
`400`	Check the request fields, account ID, and pagination parameters.
`401`	Check the secret key and authentication.
`403`	Check account access and permissions.
`404`	Check the resource ID, selected account, and mode.
`409`	Check whether the idempotency key was used for different request details or the resource is in a conflicting state.
`500`, `503`, `504`	Retry with bounded backoff. For a create retry, retain the same idempotency key. Contact support with the `trace_id`, if available, if the problem persists.

Disclosure lifecycle

Fresh disclosures