Record an externally verified settled customer payment
Generated from the checked-in source. Do not edit this reference by hand.
POST /api/v1/organizations/{organization}/billing/funding/settled
Installation write access only. Trusted administration must verify external payment settlement before calling. This is not a customer self-credit endpoint or a payment-channel callback integration. The channel/payment reference credits funds once; changed organization, currency or amount is a conflict. Pending payments must not be submitted. No commercial payment channel is implied by this administrative record API.
Operation: recordSettledCustomerFunding.
Authentication
Section titled “Authentication”Use the credential and permission scope described above. Each object below is an alternative; schemes within one object are required together.
[ { "adminBearerAuth": [] }]HTTP request
Section titled “HTTP request”Set NIU_ORIGIN to your installation origin (without /v1). Replace path, query and header placeholders with the required values. Query examples use curl 7.87 or newer to encode values with --url-query. Use the credential scope described above; a bearer token must have the authority required by this operation.
curl --fail-with-body -X POST "$NIU_ORIGIN/api/v1/organizations/{organization}/billing/funding/settled" \ -H "Authorization: Bearer $NIU_ADMIN_TOKEN" \ -H 'Content-Type: application/json' \ --data @request.jsonParameters
Section titled “Parameters”organization
Section titled “organization”Location: path. Required.
{ "type": "string", "format": "uuid"}Request body
Section titled “Request body”application/json
Section titled “application/json”Required.
{ "type": "object", "additionalProperties": false, "required": [ "currency", "amount_nanos", "channel", "payment_reference" ], "properties": { "currency": { "type": "string", "pattern": "^[A-Z]{3}$" }, "amount_nanos": { "type": "string", "pattern": "^[0-9]+$", "description": "Positive signed-64-bit nanounit amount" }, "channel": { "type": "string", "minLength": 1, "maxLength": 100 }, "payment_reference": { "type": "string", "minLength": 1, "maxLength": 200 } }}Responses
Section titled “Responses”HTTP 200
Section titled “HTTP 200”Recorded or identical receipt replay
Content type: application/json.
{ "type": "object", "properties": { "data": { "type": "object", "properties": { "recorded": { "type": "boolean", "const": true } } } }}HTTP 400
Section titled “HTTP 400”Invalid funding details
HTTP 401
Section titled “HTTP 401”Authentication required
HTTP 403
Section titled “HTTP 403”Installation write access required
HTTP 409
Section titled “HTTP 409”Unknown organization or conflicting payment reference
Behavior and supported scope
Section titled “Behavior and supported scope”Installation write access only. Trusted administration must verify external payment settlement before calling. This is not a customer self-credit endpoint or a payment-channel callback integration. The channel/payment reference credits funds once; changed organization, currency or amount is a conflict. Pending payments must not be submitted. No commercial payment channel is implied by this administrative record API.