> ## Documentation Index > Fetch the complete documentation index at: https://docs.genuka.com/llms.txt > Use this file to discover all available pages before exploring further. # Add order payment > Add a new payment record to a specific order. This endpoint allows you to register manual or external payments, update the order’s payment status, and ensure accurate tracking of completed or pending transactions. ## OpenAPI ````yaml POST /2023-11/admin/orders/{id}/payments openapi: 3.0.3 info: title: Genuka V2 - API version: 1.0.0 contact: {} servers: - url: https://api-staging.genuka.com - url: https://api.genuka.com security: - bearerAuth: [] tags: - name: Public Routes - name: Pages - name: Collections - name: Shops - name: Products - name: Articles - name: Discounts - name: Blogs - name: Company - name: Review description: |- ``` json { "title": "", "quantity": "", "product_variant": "", "date": "", "company_id": "", "shops": [] } ``` - name: Private Routes - name: Authentication - name: Apps - name: Accounting - name: Addresses - name: Customer - name: Analytics - name: Articles1 - name: Availabilities - name: API Keys - name: Orders - name: Bills - name: Blogs1 - name: Calendar Events - name: Collections1 - name: Company1 - name: Customers - name: Deliveries description: |- ``` json { "title": "", "quantity": "", "product_variant": "", "date": "", "company_id": "", "shops": [] } ``` - name: Discount - name: Domains description: |- ``` json { "domain": "", "company_id": "" } ``` - name: Analytics1 - name: Orders1 - name: Payments - name: Pages1 - name: Production - name: Bill of Materials - name: Payments1 - name: Payments Methods - name: Workflows - name: New Folder - name: Wallet - name: Marketing - name: Campaigns - name: Templates - name: Products1 - name: Product Variants - name: Analytics12 - name: Services description: >- Services are "Products" that have a duration in minutes, a buffer time and a list of users able to provide the service. - name: SupplierProducts - name: Shops1 description: >- Shops are sort of subsidiary of companies. A Company can have many Shops. Each shop can have 0 or more . But all of them are properties of a Company. - name: Warehouses description: >- Warehouses are places where stocks are placed. Shop which are physical or virtual point of sales can be attached to one or many warehouses to take their products. - name: Stocks description: |- ``` json { "title": "", "quantity": "", "product_variant": "", "date": "", "company_id": "", "shops": [] } ``` - name: Review1 description: |- ``` json { "title": "", "quantity": "", "product_variant": "", "date": "", "company_id": "", "shops": [] } ``` - name: ReviewCriterion description: |- ``` json { "title": "", "quantity": "", "product_variant": "", "date": "", "company_id": "", "shops": [] } ``` - name: StockMovements description: |- ``` json { "title": "", "quantity": "", "product_variant": "", "date": "", "company_id": "", "shops": [] } ``` - name: Suppliers - name: Treasury Accounts description: Comptes de trésorerie - name: Users - name: Wrapped - name: Returns - name: Webhooks - name: Customer Routes - name: Authentication1 - name: Addresses1 - name: Orders12 - name: Payments12 - name: Review12 description: |- ``` json { "title": "", "quantity": "", "product_variant": "", "date": "", "company_id": "", "shops": [] } ``` - name: Developer Routes - name: Authentication12 - name: Apps1 - name: Apps Shortcut - name: Products12 description: Developer can access a company product through its app paths: /2023-11/admin/orders/{id}/payments: parameters: - name: id in: path required: true schema: type: string post: tags: - Private Routes - Orders1 - Payments summary: Add Payment description: Add Payment operationId: addPayment parameters: - name: x-company in: header schema: type: string example: '{{companyId}}' requestBody: content: application/json: examples: Add Payment: value: |- { "amount": 160, "method": "bank", // Comming from treasory account "treasury_account_id": "01k1amyq08htzkeg79xd7f9pct" // Comming from treasory account } responses: '200': description: 200 OK headers: Cache-Control: schema: type: string example: no-cache, private Connection: schema: type: string example: keep-alive Content-Encoding: schema: type: string example: gzip Date: schema: type: string example: Fri, 10 Oct 2025 11:31:02 GMT Server: schema: type: string example: nginx/1.18.0 (Ubuntu) Transfer-Encoding: schema: type: string example: chunked Vary: schema: type: string example: Origin X-RateLimit-Limit: schema: type: string example: '6000' X-RateLimit-Remaining: schema: type: string example: '5999' content: application/json: schema: type: object properties: code: type: number example: 200 message: type: string example: Payment added successfully status: type: string example: success examples: 200 OK: value: code: 200 message: Payment added successfully status: success '500': description: '500' headers: Cache-Control: schema: type: string example: no-cache, private Connection: schema: type: string example: keep-alive Date: schema: type: string example: Fri, 10 Oct 2025 11:29:49 GMT Server: schema: type: string example: nginx/1.18.0 (Ubuntu) Transfer-Encoding: schema: type: string example: chunked Vary: schema: type: string example: Origin X-RateLimit-Limit: schema: type: string example: '6000' X-RateLimit-Remaining: schema: type: string example: '5999' content: application/json: schema: type: object properties: code: type: number example: 500 data: nullable: true example: null message: type: string example: >- Failed to add payment: Failed to create a payment with the given payload. Error: The amount to pay is less than or equal to 0 status: type: string example: error examples: '500': value: code: 500 data: null message: >- Failed to add payment: Failed to create a payment with the given payload. Error: The amount to pay is less than or equal to 0 status: error components: securitySchemes: bearerAuth: type: http scheme: bearer ````