Skip to main content
GET
List post-settlement documents

Overview

Once a B2B-services payment is settled, one more compliance step remains: evidence that the service was actually delivered. This endpoint reads the delivery proofs you have uploaded against the payment, and whether the set is locked. It is safe to call at any time — it reads, it never re-runs anything. That includes before the payment settles: it answers with is_settled: false rather than refusing. Only Submit Settlement Documents refuses on an unsettled payment.
B2B services only. A payment that is not a B2B-services payment is refused. B2B goods has no partner-API settlement path.

Response

An empty documents array means you have uploaded nothing yet — not that nothing is owed.
string
required
FRESH (nothing filed yet) or SUBMITTED (filed and locked). Two values, not three — there is no draft on this surface, because one submit files the set in a single call. documents is listed in both states, so FRESH means “this is what you are holding”, not “this is empty”. Read this before submitting: once it is SUBMITTED, a second submit is refused with ERR_B2B_SETTLEMENT_002.
boolean
required
Whether the payment has settled. Documents can only be filed after it has; submitting earlier is refused with ERR_B2B_SETTLEMENT_003. Uploading earlier is allowed, and so is this read.
boolean
required
true for B2B services. Read it together with required_doc_types — see below.
string[]
required
Every type this flow accepts. Because is_multi is true, the set is complete once one file of any listed type is filed — not one of each. A single-file flow (is_multi: false) would need one of every type.An upload under a type not listed here never reaches this set at all, so a ref from one is refused by the submit with ERR_B2B_SETTLEMENT_001.
string | null
required
ISO-8601 timestamp of the submission, or null while the set is still FRESH.
string
required
The document’s id — the same value as the ref Upload Document handed you. The upload writes this row, so there is only one id to hold on to.
string
required
The type the file was uploaded under — you never send a doc_type again after the upload. B2B services has exactly one, delivery_proof, and accepts many files under it. Goods is the opposite — one file per type — which is why the two flows do not share an endpoint.
string
required
The stored file’s name, for display.
string
required
A pre-signed, time-limited URL for the stored file. Fetch it if you need the document back; do not store the URL itself, as it expires.

What is listed

Only active documents, oldest upload first. A delivery proof appears here as soon as it is uploaded, so you can check what you are holding before you file it. Two things remove a document from this list: uploading is not filing, and refs on the submit is the whole set — a document you do not name there is deactivated and stops being listed. After a submit, this list is exactly what you filed.

Errors

Reading the set is refused only when the payment itself does not qualify. Both cases are a 400 carrying 40360; the details string says which.

Submit Settlement Documents

File the delivery proofs by ref and lock the set.

Upload Document

Upload each delivery proof and keep its ref.

B2B Services Verification

The whole flow, in order.

Authorizations

X-Client-ID
string
header
required

Client Application ID - Your unique application identifier used to authenticate API requests. You can find your Client ID in the Developer Settings section of the merchant dashboard.

X-Client-Secret
string
header
required

Client Secret Key - Your secret key used alongside the Client ID for secure authentication. Keep this confidential and never expose it in client-side code. Available in the Developer Settings section of the merchant dashboard.

X-Merchant-ID
string
header
required

Merchant Identifier - The unique ID for the merchant account. This is required for PSP (Payment Service Provider) merchants who manage multiple merchant accounts. You can find merchant IDs in the Merchant Management section of the dashboard.

X-API-Version
string
header
required

API Version - Specifies which version of the API to use (e.g., '1.X.X', '2.X.X', or '3.X.X'). This header allows you to control which API version your integration uses. Default version information is available in the Developer Settings.

Path Parameters

payment_id
string
required

UID of the settled B2B-services payment the documents belong to.

Response

The attached documents.

success
boolean
Example:

true

message
string
Example:

"Settlement documents"

data
object