> ## Documentation Index > Fetch the complete documentation index at: https://docs.jupico.com/llms.txt > Use this file to discover all available pages before exploring further. # Create a card-balance payout > Creates a payout instruction that draws only from the submerchant's balance originated by card transactions. Check the card balance first with **Check available card balance**. ## OpenAPI ````yaml /openapi.json post /v1/payouts/creditcard/instruction openapi: 3.0.0 info: title: Jupico - OpenAPI 3.0 description: >- The Jupico API lets Service Providers onboard merchants, process card and eCheck (ACH) payments, run hosted payment pages, manage recurring billing, send payouts, and query every resource. All endpoints use HTTPS with Basic authentication and accept and return JSON. Endpoints are grouped by workflow: onboard merchants first, then accept payments, then move funds and report. termsOfService: https://help.jupico.com/references-and-resources/legal contact: email: support@jupico.com license: name: Jupico License url: https://jupico.com version: 1.0.5 servers: - url: https://sandbox-platform.jupico.com security: - basicAuth: [] tags: - name: Status description: Health check for the Jupico API. - name: Onboarding Invites description: >- Create and send invites that onboard merchants through the Jupico-hosted flow, with optional pre-filled identity, fees, and payout bank account data. - name: Provisioning description: >- Onboard merchants from your own UI. Collect onboarding data and submit it through the provisioning chain: applicant → application → submerchant. - name: Session description: >- Create browser authorization sessions for the Jupico web components, so card and bank account data is tokenized client-side and never touches your servers. - name: Tokenization description: >- Convert one-time tokens from the web components into permanent Jupico tokens, or tokenize raw card data if your systems are PCI DSS compliant. - name: Customer description: >- Create and manage customer records that payments, subscriptions, installments, and invoices link to. - name: Card Transactions description: >- Process credit and debit card transactions using tokenized card data: sale, authorization, capture, void, refund, and rollback. - name: eCheck Transactions description: >- Debit customer bank accounts via eCheck (ACH): sale, void, refund, rollback, and bank account tokenization. - name: Checkouts description: >- Hosted checkout sessions where customers complete payment on a Jupico-hosted page. - name: Payment Links description: >- Shareable links that open a Jupico-hosted payment page — no integration code needed at the point of sharing. - name: Invoices description: Create and email invoices that customers pay online. - name: Subscriptions description: >- Recurring billing. Plans define billing schedules and pricing models; subscriptions enroll customers against a stored payment token. - name: Installments description: Split a fixed total into scheduled payments with an optional deposit. - name: Payouts description: >- Send funds from a submerchant's available balance to a tokenized bank account with on-demand payout instructions. - name: Query description: >- Search and report across every resource: transactions, merchants, settlements, balances, disputes, fees, and more. All query endpoints accept the same filter, sort, and pagination envelope — see the Query Capabilities guide. paths: /v1/payouts/creditcard/instruction: post: tags: - Payouts summary: Create a card-balance payout description: >- Creates a payout instruction that draws only from the submerchant's balance originated by card transactions. Check the card balance first with **Check available card balance**. requestBody: $ref: '#/components/requestBodies/createPayout' responses: '201': $ref: '#/components/responses/createPayout' security: - basicAuth: [] components: requestBodies: createPayout: description: create a payouts if sumerchant is in dynamic payouts. required: true content: application/json: schema: $ref: '#/components/schemas/createPayout' examples: createPayout: $ref: '#/components/examples/createPayout' responses: createPayout: description: Successfuly create a payout content: application/json: schema: type: object properties: success: type: boolean description: >- Whether the request was processed successfully. Declines return HTTP 200 with `success: false`. code: type: string description: Machine-readable result code. See the Error Codes reference. message: type: string description: Human-readable result message. data: type: object properties: subMerchantId: type: string description: Unique identifier of the submerchant. facId: type: string description: Facilitator identifier assigned by Jupico. spProductId: type: string description: >- Identifier of the Service Provider product the merchant belongs to. amount: type: number description: The amount of the transaction. type: type: string description: The type. beneficiary: type: string description: Name of the payout beneficiary. status: type: string description: Current status. batchPayoutId: type: string description: >- Identifier of the payout batch this instruction was grouped into. bankAccountToken: type: string description: Token of the bank account that receives the payout. mode: type: string description: Payout mode. payoutId: type: string description: Unique identifier of the payout instruction. accRoutingNum: type: number description: Routing number of the destination account. accountNumber: type: number description: Bank account number. accountType: type: string description: Bank account type, such as `checking`. sourceType: type: string description: Balance source the payout draws from. description: The response payload. schemas: createPayout: type: object properties: amount: type: number description: The amount to pay out. bankAccountToken: type: string description: Token of the bank account that receives the payout. subMerchantId: type: string description: Unique identifier of the submerchant. required: - amount - bankAccountToken - subMerchantId examples: createPayout: summary: Create a manual payouts example value: amount: 100 bankAccountToken: >- 36373c28d4da12feb9bb54fd3753d434:41dec2092b58351f55ad26fa5d75035ddb9fcef4ca767b5cdbf45074cf652402 subMerchantId: '874767775004' securitySchemes: basicAuth: type: http scheme: basic ````