Skip to main content
GET
Get one shipment's payment.

Authorizations

Authorization
string
header
required

OAuth 2.0 client_credentials grant via Keycloak service account. Clients are provisioned per IntegrationOrganization in the nt24-idp realm.

Path Parameters

sellerId
string<uuid>
required

UUID of the seller trade partner (must be in caller's authorized list).

uuid
string<uuid>
required
shipmentId
string<uuid>
required

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.

Response

OK

paymentDate
string<date>
required
bankAmount
object
required
cashAmount
object
required
sourceIban
string
Example:

"DE89370400440532013000"

sourceAccountComment
string

Why the payment came from a bank account that is not registered with Novatrade24. The payment is stored without it, but an order whose payment is not from a registered account (ibanConsistent: false) cannot be completed until a comment is on file — the same rule the platform applies to its own users. Absent or blank leaves any comment already on the payment untouched. On a response it is the comment on file, whether sent here or entered by NT24 staff.

Example:

"Paid from the managing director's private account; the company account was frozen."

status
enum<string>
Available options:
DRAFT,
SUBMITTED,
VALID,
INVALID
amountMatchesInvoice
boolean
ibanConsistent
boolean
readyForPickup
boolean

Payment recorded and evidenced: paymentDate is set and an active proof of payment — a PAYMENT_BANK_TRANSFER_SCREENSHOT or a PAYMENT_CONFIRMATION, either one — is filed against the order, plus a source-of-funds declaration once cash reaches €10,000. Derived on every read, and it can turn back to false — raising the cash amount past the threshold makes the order wait for the declaration. On an order split across several shipments, every shipment answers.

version
integer
updatedAt
string<date-time>