# Jupico

## Docs

- [Authentication](https://docs.jupico.com/api-reference/authentication.md): Authenticate every Jupico API request with HTTP Basic credentials issued to your platform.
- [Authorize a card](https://docs.jupico.com/api-reference/card-transactions/authorize-a-card.md): An authorization confirms the cardholder's ability to pay and reserves the amount without charging it. Use it when the final amount is unknown or fulfillment is deferred — for example, tips at a restaurant or a card on file at a hotel. Complete the charge later with **Capture**.
- [Capture an authorization](https://docs.jupico.com/api-reference/card-transactions/capture-an-authorization.md): A capture confirms a previous authorization and initiates settlement, charging the customer. The capture amount may exceed the authorized amount up to an allowable excess limit determined by the issuing bank.
- [Process a card sale](https://docs.jupico.com/api-reference/card-transactions/process-a-card-sale.md): A sale combines authorization and capture in one transaction. Use it when purchases are fulfilled immediately, such as retail or e-commerce checkout. If the issuing bank approves, an approval code is returned; if it declines, the response includes the decline reason.
- [Refund a card transaction](https://docs.jupico.com/api-reference/card-transactions/refund-a-card-transaction.md): Returns funds to the customer's card for a previously settled transaction. Use refunds for returns, cancellations, or to resolve disputes. For unsettled transactions, use **Void** instead.
- [Roll back a card transaction](https://docs.jupico.com/api-reference/card-transactions/roll-back-a-card-transaction.md): A rollback (communications/system reversal) cancels a transaction whose response you never received — for example, after a timeout. As the original requestor, you are responsible for generating a rollback for every transaction that does not receive a response, to prevent duplicate or inconsistent ch…
- [Void a card transaction](https://docs.jupico.com/api-reference/card-transactions/void-a-card-transaction.md): Cancels a transaction that has not yet settled, so the customer is never charged. Once a transaction has settled, use **Refund** instead.
- [Create a checkout session](https://docs.jupico.com/api-reference/checkouts/create-a-checkout-session.md): Creates a hosted checkout session where the customer completes payment on a Jupico-hosted page. Configure accepted payment methods, data collection, and redirect behavior through the hosted session settings.
- [Deactivate a checkout session](https://docs.jupico.com/api-reference/checkouts/deactivate-a-checkout-session.md): Deactivates a checkout session so it can no longer be used to pay. Deactivated sessions can be reactivated.
- [Delete a checkout session](https://docs.jupico.com/api-reference/checkouts/delete-a-checkout-session.md): Permanently deletes a checkout session. This cannot be undone; to disable a session temporarily, use **Deactivate** instead.
- [Update a checkout session](https://docs.jupico.com/api-reference/checkouts/update-a-checkout-session.md): Updates the configuration of an existing checkout session.
- [Create a customer](https://docs.jupico.com/api-reference/customer/create-a-customer.md): Creates a customer record that payments, subscriptions, installments, and invoices can be linked to. Returns the created customer.
- [Delete a customer](https://docs.jupico.com/api-reference/customer/delete-a-customer.md): Deletes a customer record. Returns the deleted customer.
- [Update a customer](https://docs.jupico.com/api-reference/customer/update-a-customer.md): Updates an existing customer's details. Returns the updated customer.
- [Process an eCheck sale](https://docs.jupico.com/api-reference/echeck-transactions/process-an-echeck-sale.md): Initiates a direct debit (ACH) from the customer's bank account. If the debit request is accepted, the transaction proceeds to settlement; otherwise the response includes the failure reason. Note that ACH returns can occur days after acceptance.
- [Refund an eCheck transaction](https://docs.jupico.com/api-reference/echeck-transactions/refund-an-echeck-transaction.md): Returns funds to the customer's bank account for a previously settled eCheck debit. Use refunds for returns, cancellations, or to resolve disputes.
- [Roll back an eCheck transaction](https://docs.jupico.com/api-reference/echeck-transactions/roll-back-an-echeck-transaction.md): A rollback (communications/system reversal) cancels an eCheck transaction whose response was not reliably delivered. Generate a rollback for any eCheck transaction that does not receive a response, to prevent duplicate or inconsistent charges. To return funds for a settled transaction, use **Refund*…
- [Tokenize a bank account](https://docs.jupico.com/api-reference/echeck-transactions/tokenize-a-bank-account.md): Tokenizes a customer's bank account details. Use the returned token in place of raw account data for eCheck sales and recurring payments.
- [Void an eCheck transaction](https://docs.jupico.com/api-reference/echeck-transactions/void-an-echeck-transaction.md): Cancels an eCheck transaction that has not yet been submitted for settlement, so no debit occurs. Once settled, use **Refund** instead.
- [Environments & Testing Data](https://docs.jupico.com/api-reference/environments-testing-data.md): Sandbox and production environments, plus test cards, bank accounts, and identity data you can use to build against Jupico safely.
- [Error Codes](https://docs.jupico.com/api-reference/error-codes.md): Catalog of every stable error code returned by the Jupico API, with cause and remediation.
- [Error Handling](https://docs.jupico.com/api-reference/error-handling.md): Error response shape, retry rules, and best practices for handling failures in the Jupico API.
- [Go-Live Checklist](https://docs.jupico.com/api-reference/go-live-checklist.md): Everything to verify before switching your Jupico integration from sandbox to production.
- [Activate an installment plan](https://docs.jupico.com/api-reference/installments/activate-an-installment-plan.md): Reactivates a previously deactivated installment plan, resuming scheduled payments.
- [Create an installment plan](https://docs.jupico.com/api-reference/installments/create-an-installment-plan.md): Creates an installment plan that splits a total amount into scheduled payments for a customer. The initial charge depends on the deposit and start date: with no deposit and no future start date, the first payment is charged immediately; with a future start date and no deposit, only card validation i…
- [Deactivate an installment plan](https://docs.jupico.com/api-reference/installments/deactivate-an-installment-plan.md): Pauses an active installment plan, suspending scheduled payments until reactivated.
- [Delete an installment plan](https://docs.jupico.com/api-reference/installments/delete-an-installment-plan.md): Permanently deletes an installment plan and stops all future payments. This cannot be undone; to pause payments, use **Deactivate** instead.
- [Update an installment payment token](https://docs.jupico.com/api-reference/installments/update-an-installment-payment-token.md): Replaces the payment token charged for an existing installment plan — for example, when the customer changes cards.
- [Create an invoice](https://docs.jupico.com/api-reference/invoices/create-an-invoice.md): Creates an invoice with line items, due date, and payment terms. Deliver it to the customer with **Send an invoice**.
- [Delete an invoice](https://docs.jupico.com/api-reference/invoices/delete-an-invoice.md): Permanently deletes an invoice. This cannot be undone; to cancel an invoice while keeping the record, use **Void** instead.
- [Send an invoice](https://docs.jupico.com/api-reference/invoices/send-an-invoice.md): Emails the invoice to the customer with a link to pay online.
- [Update an invoice](https://docs.jupico.com/api-reference/invoices/update-an-invoice.md): Updates the details of an existing invoice, such as items, amounts, or dates.
- [Void an invoice](https://docs.jupico.com/api-reference/invoices/void-an-invoice.md): Voids an invoice so it can no longer be paid. Voided invoices remain visible for record-keeping.
- [Cancel an invite](https://docs.jupico.com/api-reference/onboarding-invites/cancel-an-invite.md): Cancels an onboarding invite. The invite link can no longer be used to onboard.
- [Create an additional-MID invite](https://docs.jupico.com/api-reference/onboarding-invites/create-an-additional-mid-invite.md): Creates an invite that adds a new submerchant for an existing applicant — an additional MID request. Optionally scope the invite to an existing application with `invitedToSmAppId`.
- [Create an invite](https://docs.jupico.com/api-reference/onboarding-invites/create-an-invite.md): Creates an onboarding invite without sending it. Pre-fill identity, fees, and payout bank account data to shorten the hosted onboarding flow for the merchant. Send the invite later with **Send an invite**.
- [Create and send an invite](https://docs.jupico.com/api-reference/onboarding-invites/create-and-send-an-invite.md): Creates an onboarding invite and immediately emails it to the merchant. Equivalent to **Create an invite** followed by **Send an invite** in a single call.
- [Create multiple invites](https://docs.jupico.com/api-reference/onboarding-invites/create-multiple-invites.md): Creates multiple onboarding invites in a single request, for bulk merchant migrations. Set `dryRun` to `true` to validate the batch without creating any invites.
- [Send an invite](https://docs.jupico.com/api-reference/onboarding-invites/send-an-invite.md): Emails a previously created invite to the merchant. Use this after **Create an invite** when you want to control the timing of delivery.
- [Update an invite](https://docs.jupico.com/api-reference/onboarding-invites/update-an-invite.md): Updates the details of an existing invite, such as the invitee's contact information or reference.
- [API Overview](https://docs.jupico.com/api-reference/overview.md): Get started with the Jupico API to onboard merchants, process payments, manage payouts, and run your platform.
- [Create a payment link](https://docs.jupico.com/api-reference/payment-links/create-a-payment-link.md): Creates a shareable payment link. Each customer who opens the link pays on a Jupico-hosted page — no integration code required at the point of sharing.
- [Deactivate a payment link](https://docs.jupico.com/api-reference/payment-links/deactivate-a-payment-link.md): Deactivates a payment link so it can no longer be used to pay. Deactivated links can be reactivated.
- [Delete a payment link](https://docs.jupico.com/api-reference/payment-links/delete-a-payment-link.md): Permanently deletes a payment link. This cannot be undone; to disable a link temporarily, use **Deactivate** instead.
- [Update a payment link](https://docs.jupico.com/api-reference/payment-links/update-a-payment-link.md): Updates the amount, items, or settings of an existing payment link.
- [Create a card-balance payout](https://docs.jupico.com/api-reference/payouts/create-a-card-balance-payout.md): 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**.
- [Create a payout instruction](https://docs.jupico.com/api-reference/payouts/create-a-payout-instruction.md): Creates a payout instruction that sends funds from the submerchant's available balance to a tokenized bank account. Check the balance first with **Check available balance** under Reporting & Queries.
- [Create an eCheck-balance payout](https://docs.jupico.com/api-reference/payouts/create-an-echeck-balance-payout.md): Creates a payout instruction that draws only from the submerchant's balance originated by eCheck (ACH) transactions. Check the eCheck balance first with **Check available eCheck balance**.
- [Void a payout instruction](https://docs.jupico.com/api-reference/payouts/void-a-payout-instruction.md): Voids a payout instruction that has not yet been executed, returning the funds to the submerchant's available balance.
- [Create a submerchant](https://docs.jupico.com/api-reference/provisioning/create-a-submerchant.md): Creates a submerchant linked to an application, with the business identity, fee configuration, and payout bank accounts. The submerchant is the entity that processes transactions once approved.
- [Create an applicant](https://docs.jupico.com/api-reference/provisioning/create-an-applicant.md): Creates an applicant — the individual who owns the merchant application. This is the first step in the provisioning chain: applicant → application → submerchant.
- [Create an application](https://docs.jupico.com/api-reference/provisioning/create-an-application.md): Creates a merchant application linked to an applicant. The application carries the entity type and ownership details used in underwriting.
- [Update a submerchant](https://docs.jupico.com/api-reference/provisioning/update-a-submerchant.md): Updates an existing submerchant. The submerchant must be in `review` status; once activated, it cannot be modified. All `identity.business` fields are optional. `feesTemplateId` and `payoutBankAccounts` are optional, but if `payoutBankAccounts` is provided, `accountRouting`, `accountNumber`, `accoun…
- [Update an application](https://docs.jupico.com/api-reference/provisioning/update-an-application.md): Updates an existing application. The application must be in `review` status; once activated, it cannot be modified.
- [Query Capabilities](https://docs.jupico.com/api-reference/query-capabilities.md): Sort, page, and filter results across all Query API endpoints.
- [Check available balance](https://docs.jupico.com/api-reference/query/check-available-balance.md): Returns the submerchant's total available balance for payouts.
- [Check available card balance](https://docs.jupico.com/api-reference/query/check-available-card-balance.md): Returns the submerchant's available payout balance originated by card transactions.
- [Check available eCheck balance](https://docs.jupico.com/api-reference/query/check-available-echeck-balance.md): Returns the submerchant's available payout balance originated by eCheck (ACH) transactions.
- [Get a plan](https://docs.jupico.com/api-reference/query/get-a-plan.md): Returns a single subscription plan by its `planId`, including schedules and pricing configuration.
- [Get a transaction timeline](https://docs.jupico.com/api-reference/query/get-a-transaction-timeline.md): Returns a chronological timeline of transaction events, showing how activity evolved over time.
- [Get dispute history](https://docs.jupico.com/api-reference/query/get-dispute-history.md): Returns the event timeline for disputes, detailing each stage and status change.
- [List checkout sessions](https://docs.jupico.com/api-reference/query/list-checkout-sessions.md): Returns checkout sessions, both active and past, with their configuration and status.
- [List disputes](https://docs.jupico.com/api-reference/query/list-disputes.md): Returns disputes filed against transactions, including dispute status and resolution details.
- [List fees](https://docs.jupico.com/api-reference/query/list-fees.md): Returns fee records assessed against merchants, including per-transaction and recurring fees. Supports the standard query envelope.
- [List installment plans](https://docs.jupico.com/api-reference/query/list-installment-plans.md): Returns installment plans, both active and inactive, including payment schedules and statuses.
- [List invoices](https://docs.jupico.com/api-reference/query/list-invoices.md): Returns invoices with amounts, statuses, and associated customers and submerchants.
- [List merchant applications](https://docs.jupico.com/api-reference/query/list-merchant-applications.md): Returns provisioning applications with their status, applicant information, and associated submerchants. Use this to track onboarding progress.
- [List merchant bank accounts](https://docs.jupico.com/api-reference/query/list-merchant-bank-accounts.md): Returns the bank accounts registered to your merchants, including account details and status.
- [List merchants](https://docs.jupico.com/api-reference/query/list-merchants.md): Returns the merchants under your platform, including profile details and operational status.
- [List onboarding invites](https://docs.jupico.com/api-reference/query/list-onboarding-invites.md): Returns onboarding invites and their current status — created, sent, completed, or cancelled.
- [List payment links](https://docs.jupico.com/api-reference/query/list-payment-links.md): Returns payment links with usage details and status.
- [List payout instructions](https://docs.jupico.com/api-reference/query/list-payout-instructions.md): Returns payout instructions and their statuses.
- [List plans](https://docs.jupico.com/api-reference/query/list-plans.md): Returns subscription plans with their schedules and pricing configuration.
- [List Service Provider settlements](https://docs.jupico.com/api-reference/query/list-service-provider-settlements.md): Returns settlement records at the Service Provider level, including settlement timing and amounts.
- [List submerchant settlements](https://docs.jupico.com/api-reference/query/list-submerchant-settlements.md): Returns settlement records for your submerchants, including settlement timing and amounts.
- [List subscriptions](https://docs.jupico.com/api-reference/query/list-subscriptions.md): Returns subscriptions, both active and inactive, including their schedules and billing status.
- [List transactions](https://docs.jupico.com/api-reference/query/list-transactions.md): Returns transactions matching the supplied filters. Supports the standard query envelope for filtering (including `metadata.<key>`), sorting, and pagination.
- [Responses](https://docs.jupico.com/api-reference/responses.md): Structure, envelope, and conventions for every Jupico API response.
- [Create a browser session](https://docs.jupico.com/api-reference/session/create-a-browser-session.md): Creates a browser authorization session for the Jupico web components. Call this from your backend, then pass the returned session to the component so card or bank account data is tokenized client-side and never touches your servers.
- [Status Codes](https://docs.jupico.com/api-reference/status-codes.md): HTTP status codes and transaction status values returned by the Jupico API.
- [Check API status](https://docs.jupico.com/api-reference/status/check-api-status.md): Returns `200` when the API is reachable. Use this endpoint for health checks and uptime monitoring; it requires no request body.
- [Activate a plan](https://docs.jupico.com/api-reference/subscriptions/activate-a-plan.md): Activates a plan so customers can subscribe to it.
- [Activate a subscription](https://docs.jupico.com/api-reference/subscriptions/activate-a-subscription.md): Activates a subscription, resuming scheduled billing.
- [Create a plan](https://docs.jupico.com/api-reference/subscriptions/create-a-plan.md): Creates a subscription plan — the reusable template customers subscribe to. A plan contains one or more billing schedules, each with its own frequency and pricing model (flat, tiered, per-module, or usage-based), plus optional hosted session settings for customer-facing signup.
- [Create a subscription](https://docs.jupico.com/api-reference/subscriptions/create-a-subscription.md): Subscribes a customer to one or more plan schedules, billed against a stored payment token. Billing runs automatically at each schedule's frequency.
- [Deactivate a plan](https://docs.jupico.com/api-reference/subscriptions/deactivate-a-plan.md): Deactivates a plan so no new subscriptions can be created from it. Existing subscriptions are not affected.
- [Deactivate a subscription](https://docs.jupico.com/api-reference/subscriptions/deactivate-a-subscription.md): Deactivates a subscription, pausing scheduled billing until reactivated.
- [Delete a plan](https://docs.jupico.com/api-reference/subscriptions/delete-a-plan.md): Permanently deletes a plan. This cannot be undone; to stop new signups temporarily, use **Deactivate** instead.
- [Delete a subscription](https://docs.jupico.com/api-reference/subscriptions/delete-a-subscription.md): Permanently deletes a subscription and stops all future billing. This cannot be undone; to pause billing, use **Deactivate** instead.
- [Update a plan](https://docs.jupico.com/api-reference/subscriptions/update-a-plan.md): Updates an existing subscription plan's details, schedules, or hosted session settings.
- [Update a subscription payment token](https://docs.jupico.com/api-reference/subscriptions/update-a-subscription-payment-token.md): Replaces the payment token billed for an existing subscription — for example, when the customer changes cards.
- [Timeout Handling](https://docs.jupico.com/api-reference/timeout-handling.md): How to handle network timeouts, lost responses, and rollbacks safely without double-charging customers.
- [Convert a one-time token](https://docs.jupico.com/api-reference/tokenization/convert-a-one-time-token.md): Converts a one-time token (OTT) produced by the web component into a permanent Jupico token that you can store and reuse for future charges, subscriptions, and installments.
- [Tokenize raw card data](https://docs.jupico.com/api-reference/tokenization/tokenize-raw-card-data.md): Securely tokenize raw credit card information. The resulting token can be used in place of raw card data in future transactions, improving security and simplifying PCI compliance.
- [Transaction Status Handling](https://docs.jupico.com/api-reference/transaction-status-handling.md): How to interpret and act on each transaction status returned by the Jupico API.
- [Webhooks](https://docs.jupico.com/api-reference/webhooks.md): Receive real-time notifications for transaction, onboarding, payout, and dispute events from Jupico.
- [Hosted Checkout: Collect Payments Without Custom Forms](https://docs.jupico.com/docs/hosted/checkout.md): Collect payments via Jupico's hosted checkout page — no custom form required. Configure merchant, amount, and payment methods, then redirect customers.
- [Installments: Finite Payment Plans with Auto-Charge](https://docs.jupico.com/docs/hosted/installments.md): Offer buy-now-pay-later payment plans with Jupico installments. Define total amount, deposit, schedule, and cycles — Jupico handles charges and retries.
- [Invoicing: Structured Payment Requests with Tracking](https://docs.jupico.com/docs/hosted/invoicing.md): Create, send, and track invoices with Jupico. Use invoicing for B2B payment requests, accounts-receivable workflows, and itemized charges with due dates.
- [Payment Links: Send Shareable Payment Requests Instantly](https://docs.jupico.com/docs/hosted/payment-links.md): Create and share payment links via email, SMS, or chat. Use Backoffice for manual links or the API to automate payment link creation in your product.
- [Subscriptions: Recurring Billing Plans and Enrollments](https://docs.jupico.com/docs/hosted/subscriptions.md): Build recurring billing with Jupico subscriptions. Create reusable plans, enroll customers, and manage the full lifecycle from activation to cancellation.
- [Flex Onboarding: Invites and Pre-filled Applications](https://docs.jupico.com/docs/onboarding/flex-onboarding.md): Use Jupico's Flex onboarding with Backoffice invites or the Invites API to pre-fill merchant data, send trackable links, and assist onboarding operations.
- [Hosted Onboarding: Launch Merchants Without Custom Forms](https://docs.jupico.com/docs/onboarding/hosted-onboarding.md): Use Jupico's hosted onboarding flow to get merchants live quickly. Share a link and let Jupico handle the onboarding UI, validation, and compliance.
- [Integration Levels: Rapid, Flex, and Custom Explained](https://docs.jupico.com/docs/onboarding/integration-levels.md): Compare Jupico's three integration levels — Rapid, Flex, and Custom — to choose the right merchant experience, branding model, and engineering effort.
- [Merchant Onboarding: Overview for Jupico Platforms](https://docs.jupico.com/docs/onboarding/overview.md): Learn how to onboard merchants into Jupico. Compare integration levels and onboarding setups to choose the right path for your platform.
- [Provisioning API: Fully Custom Merchant Onboarding](https://docs.jupico.com/docs/onboarding/provisioning-api.md): Build fully embedded merchant onboarding with Jupico's Provisioning API. Create an Applicant, Application, and Submerchant in a structured sequence.
- [Enhanced Card Verification: AVS and CVV Code Reference](https://docs.jupico.com/docs/operations/enhanced-card-verification.md): Use Jupico's Enhanced Card Verification to automate AVS and CVV decisioning. Reference the complete code tables to understand pass and decline behavior.
- [Payments Glossary: Key Terms for Jupico Integrations](https://docs.jupico.com/docs/operations/glossary.md): Definitions of key payments industry terms used throughout Jupico documentation, from ACH and acquirer to tokenization, void, and wire transfer.
- [Go-Live Checklist: Launching Your Jupico Integration](https://docs.jupico.com/docs/operations/go-live-checklist.md): Complete every requirement before switching to production: environment, payments, webhooks, onboarding, security, monitoring, and post-launch validation.
- [Security Overview: Protecting Your Jupico Integration](https://docs.jupico.com/docs/operations/security.md): Secure your Jupico integration with TLS encryption, API credential management, IP allowlisting, PCI DSS compliance, and webhook security best practices.
- [Tax Withholding and Release for Marketplace Platforms](https://docs.jupico.com/docs/operations/tax-withholding.md): Manage sales tax for marketplace platforms using Jupico's tax withholding API. Learn the taxWithHold, taxWithHoldRelease, and taxAmountRelease parameters.
- [Jupico Overview: Embedded Payments for Software Platforms](https://docs.jupico.com/docs/overview.md): Learn how Jupico helps platforms embed payment acceptance, merchant onboarding, and payout workflows. Understand the core roles and integration paths.
- [ACH and eCheck Payments with Jupico Web Components](https://docs.jupico.com/docs/payments/ach-echeck.md): Accept ACH and eCheck payments with Jupico's echeck-form component. Tokenize bank account details securely without exposing sensitive data to your servers.
- [Card Transactions: Sale, Authorization, Capture, Void](https://docs.jupico.com/docs/payments/card-transactions.md): Reference for Jupico card transaction types: Sale, Authorization, Capture, Void, Refund, and Rollback. Includes use cases and API endpoints for each.
- [Accept Payments with Jupico: Cards, ACH, and Wallets](https://docs.jupico.com/docs/payments/overview.md): Choose your Jupico payment path: hosted products for fast launch, custom tokenization flows for native checkout, or in-person terminal payments.
- [Tokenization: Secure Payment Collection with Jupico](https://docs.jupico.com/docs/payments/tokenization.md): Learn how Jupico tokenization replaces card and bank data with secure tokens. Covers the authorization session, one-time tokens, and permanent tokens.
- [Apple Pay and Google Pay with Jupico Web Components](https://docs.jupico.com/docs/payments/wallets.md): Add Apple Pay and Google Pay to your checkout with Jupico wallet web components. Each component returns a tokenized result for secure backend processing.
- [Jupico Payment Web Components: Cards, ACH, and Wallets](https://docs.jupico.com/docs/payments/web-components.md): Embed Jupico's secure payment web components for card, bank account, Apple Pay, and Google Pay. Each handles collection, validation, and tokenization.
- [API Payouts: Send On-Demand Transfers to Merchants](https://docs.jupico.com/docs/payouts/api-payouts.md): Use Jupico's Dynamic Payouts API to send funds to merchants on demand. Submit payout instructions, check balances, and void pending transfers.
- [Jupico Payout Options: Scheduled and API Transfers](https://docs.jupico.com/docs/payouts/overview.md): Learn how Jupico payouts work. Compare scheduled payouts for predictable intervals and API-driven dynamic payouts for on-demand fund transfers.
- [Scheduled Payouts: Automate Merchant Fund Transfers](https://docs.jupico.com/docs/payouts/scheduled-payouts.md): Set up Jupico scheduled payouts to automatically transfer merchant funds on a daily, weekly, or monthly cycle with no manual intervention.
- [Jupico Quickstart: Run Your First Test Transaction](https://docs.jupico.com/docs/quickstart.md): Set up sandbox credentials, create a browser authorization session, render a web component, and run a test card transaction with Jupico in minutes.
- [Supported Countries and Regions for Jupico Payments](https://docs.jupico.com/docs/supported-countries.md): Jupico supports platforms and merchants across 83 countries. See which regions are live, available in 2–4 weeks, or coming in 4–6 months.

## OpenAPI Specs

- [openapi](https://docs.jupico.com/openapi.json)