> ## Documentation Index > Fetch the complete documentation index at: https://developers.novatrade24.com/llms.txt > Use this file to discover all available pages before exploring further. # Upload proof-of-payment document for one shipment. > Files the proof against the half the payment was recorded on, which is what lets `readyForPickup` become true for a split order. Allowed types: `PAYMENT_BANK_TRANSFER_SCREENSHOT`, `PAYMENT_CONFIRMATION`, `PAYMENT_SOURCE_OF_FUNDS_DECLARATION`. ## OpenAPI ````yaml /openapi-integration-v1.yaml post /partners/{sellerId}/orders/{uuid}/shipments/{shipmentId}/payment/documents openapi: 3.1.0 info: title: Novatrade24 Integration API version: 1.5.0-draft summary: Customer-facing integration API for the Novatrade24 compliance platform. description: > The Novatrade24 Integration API lets marketplaces, dealers, and financial partners embed EU VAT-compliant cross-border vehicle transactions into their own systems. The API is organized around the end-to-end compliance workflow: 1. **Buyer (KYC)**: create or sync a buyer, run VIES, upload KYC documents, optionally trigger NT24-led verification. 2. **Order**: register a VIN-based transaction linked to a buyer. 3. **Invoice**: submit VAT security deposit invoice (`PRELIMINARY`) and final invoice data and documents. 4. **Payment**: submit proof-of-payment; pickup readiness is derived from it. 5. **Transport**: confirm pickup and delivery with CMR / declarations. 6. **Compliance rollup**: poll the composed state of the five modules above, or subscribe to webhooks. The rollup is also where you see what is still missing: `blockers[]` names the artifact and the module waiting for it. There is no seventh step. Novatrade24 staff close an order once the artifacts are on file; the rollup reports that as `complianceStatus: VALID`. The final invoice is submitted through the invoice operation with `type: FINAL`, like the VAT security deposit invoice (`PRELIMINARY`). **Status:** Draft specification. The production endpoint `https://api.novatrade24.com/v1` is live, with access restricted to pilot customers: every request needs a bearer token obtained through the OAuth2 client credentials grant. A hosted mock is available at `https://mock.api.novatrade24.com` for integration design. termsOfService: https://novatrade24.com/terms-and-conditions contact: name: Novatrade24 Integration Support email: integration-support@novatrade24.com url: https://developers.novatrade24.com license: name: Proprietary url: https://novatrade24.com/terms-and-conditions servers: - url: https://api.novatrade24.com/v1 description: Production (pilot, restricted access) - url: https://api.stage.novatrade24.com/v1 description: Staging environment - url: https://mock.api.novatrade24.com description: Hosted mock server (Prism), spec-driven stub responses security: - oauth2ClientCredentials: [] tags: - name: Discovery description: Organization + capability discovery. - name: Buyers description: | Manage buyer (trade partner) records and KYC lifecycle. `COMPANY` buyers are upserted by `(sellerId, vatNumber)`. Natural-person (`CONSUMER`) buyers are onboarded through the prospect / Click2Comply flow rather than through this API, but they are read here on the same operations and carry the same `BuyerResponse`. - name: KYC description: KYC documents, VIES checks, Mode B verification, profile. - name: Self-service invitations description: | Orchestrate buyer-facing self-service links for KYC submission and prospect onboarding. - name: Orders description: | Register vehicle transactions. Orders may contain one or more VINs; single-VIN is the default. - name: Invoice description: >- Buyer's VAT security deposit invoice (PRELIMINARY) or final invoice (FINAL). - name: Payment description: Proof-of-payment data and documents; pickup readiness trigger. - name: Transport description: Pickup + delivery milestones and documents (CMR, declarations). - name: Compliance description: End-to-end compliance rollup per order. - name: Prospects description: | The seller's Click2Comply campaign links (prospect invitations), and the seller's prospects from every entry channel: the company link, a contact's personal link or a campaign link. - name: Documents description: Typed document download. - name: Webhooks description: Webhook endpoint registration, delivery history, test-fire. paths: /partners/{sellerId}/orders/{uuid}/shipments/{shipmentId}/payment/documents: parameters: - $ref: '#/components/parameters/SellerIdPath' - $ref: '#/components/parameters/OrderUuidPath' - $ref: '#/components/parameters/ShipmentIdPath' post: tags: - Payment summary: Upload proof-of-payment document for one shipment. description: > Files the proof against the half the payment was recorded on, which is what lets `readyForPickup` become true for a split order. Allowed types: `PAYMENT_BANK_TRANSFER_SCREENSHOT`, `PAYMENT_CONFIRMATION`, `PAYMENT_SOURCE_OF_FUNDS_DECLARATION`. operationId: uploadShipmentPaymentDocument parameters: - $ref: '#/components/parameters/IdempotencyKeyHeader' requestBody: required: true content: multipart/form-data: schema: $ref: '#/components/schemas/DocumentUploadMultipart' responses: '201': description: Document uploaded. content: application/json: schema: $ref: '#/components/schemas/DocumentResponse' 4XX: $ref: '#/components/responses/Problem' 5XX: $ref: '#/components/responses/Problem' components: parameters: SellerIdPath: name: sellerId in: path required: true description: UUID of the seller trade partner (must be in caller's authorized list). schema: type: string format: uuid OrderUuidPath: name: uuid in: path required: true schema: type: string format: uuid ShipmentIdPath: name: shipmentId in: path required: true description: | UUID of one live shipment of the order in the path, as the order's `shipmentIds` list them. A shipment that is not this order's live shipment is `404`, whether it belongs to another order or no longer exists. schema: type: string format: uuid IdempotencyKeyHeader: name: Idempotency-Key in: header required: true description: | Client-generated unique key (UUID recommended) for this write operation. Identical key + identical body within 24h returns the cached response. Identical key + different body returns `422`. schema: type: string minLength: 1 maxLength: 255 schemas: DocumentUploadMultipart: type: object required: - type - file properties: type: $ref: '#/components/schemas/DocumentType' documentDate: type: string format: date signedWet: type: boolean default: false file: type: string format: binary DocumentResponse: type: object required: - id - type - status - uploadDate - originalFilename - fileUrl properties: id: type: string description: Document identifier (also used as storage key). type: $ref: '#/components/schemas/StoredDocumentType' status: $ref: '#/components/schemas/DocumentStatus' documentDate: type: string format: date signedWet: type: boolean originalFilename: type: string uploadDate: type: string format: date-time fileUrl: type: string description: Relative URL to document-download endpoint. DocumentType: type: string description: | Document type enumeration reused from the NT24 platform taxonomy: the types a caller can file through this API. Only values relevant to the allowed set of each endpoint are accepted; `UNCATEGORIZED` and `*_ADDITIONAL_INFORMATION` variants are rejected at the API boundary. A stored document reports its type as `StoredDocumentType`, which also carries those. enum: - COC_EXTRACT - COC_COMPANY_ONLINE_PRESENCE - COC_LETTER_OF_AUTHORIZATION - BANK_ACCOUNT_DETAILS - BANK_ACCOUNT_LETTERHEAD - BANK_STATEMENT - VAT_STATEMENT - VAT_RETURN - CONTACT_DOCUMENT - CONTACT_FACE_PICTURE - CONTACT_ID_CARD - CONTACT_PASSPORT - CONTACT_DRIVERS_LICENSE - CONTACT_PICTURE_OF_MEETING - CONTACT_PROFILE_PICTURE - CONTACT_VERIFICATION_REPORT - TP_TRADEPARTNER_PICTURE - TP_PROFILE_PICTURE - ADDRESS_SCREENSHOT - ORDER_PURCHASING_CONTRACT - SHIPMENT_INVOICE - SHIPMENT_PRELIMINARY_INVOICE - SHIPMENT_DEPOSIT_AGREEMENT - PAYMENT_BANK_TRANSFER_SCREENSHOT - PAYMENT_CONFIRMATION - PAYMENT_SOURCE_OF_FUNDS_DECLARATION - TRANSPORT_CMR - TRANSPORT_CMR_DELIVERY - TRANSPORT_PICTURE_OF_TRANSPORT - TRANSPORT_CONFIRMATION_OF_ARRIVAL StoredDocumentType: type: string description: | The type of a document on file, as responses report it. Every value of `DocumentType`, plus the types the Novatrade24 web app files and this API refuses on upload: `UNCATEGORIZED` and the `*_ADDITIONAL_INFORMATION` variants. Such a document can sit on one of your orders or buyers, and archiving or restoring it through `PATCH /documents/{id}` returns it with its type as stored. Response-only: never accepted as a request value. enum: - COC_EXTRACT - COC_COMPANY_ONLINE_PRESENCE - COC_LETTER_OF_AUTHORIZATION - COC_ADDITIONAL_INFORMATION - BANK_ACCOUNT_DETAILS - BANK_ACCOUNT_LETTERHEAD - BANK_STATEMENT - BANK_ADDITIONAL_INFORMATION - VAT_STATEMENT - VAT_RETURN - VAT_ADDITIONAL_INFORMATION - CONTACT_DOCUMENT - CONTACT_FACE_PICTURE - CONTACT_ID_CARD - CONTACT_PASSPORT - CONTACT_DRIVERS_LICENSE - CONTACT_PICTURE_OF_MEETING - CONTACT_PROFILE_PICTURE - CONTACT_VERIFICATION_REPORT - CONTACT_ADDITIONAL_INFORMATION - TP_TRADEPARTNER_PICTURE - TP_PROFILE_PICTURE - TP_ADDITIONAL_INFORMATION - ADDRESS_SCREENSHOT - ADDRESS_ADDITIONAL_INFORMATION - ORDER_PURCHASING_CONTRACT - ORDER_ADDITIONAL_INFORMATION - SHIPMENT_INVOICE - SHIPMENT_PRELIMINARY_INVOICE - SHIPMENT_DEPOSIT_AGREEMENT - PAYMENT_BANK_TRANSFER_SCREENSHOT - PAYMENT_CONFIRMATION - PAYMENT_ADDITIONAL_INFORMATION - PAYMENT_SOURCE_OF_FUNDS_DECLARATION - TRANSPORT_CMR - TRANSPORT_CMR_DELIVERY - TRANSPORT_PICTURE_OF_TRANSPORT - TRANSPORT_CONFIRMATION_OF_ARRIVAL - UNCATEGORIZED DocumentStatus: type: string enum: - ACTIVE - ARCHIVED Problem: type: object required: - type - title - status properties: type: type: string format: uri title: type: string status: type: integer detail: type: string instance: type: string traceId: type: string responses: Problem: description: | RFC 9457 problem detail. Default fallback for any status not explicitly enumerated on the operation. Concrete status is in `status` field. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' securitySchemes: oauth2ClientCredentials: type: oauth2 description: | OAuth 2.0 client_credentials grant via Keycloak service account. Clients are provisioned per `IntegrationOrganization` in the `nt24-idp` realm. flows: clientCredentials: tokenUrl: >- https://auth.novatrade24.com/realms/nt24-idp/protocol/openid-connect/token scopes: {} ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.