Skip to main content
Use the Nova.Pay Checkout Skill with an AI coding agent to generate a branded payment page from a prompt. The generated checkout runs on your own server, follows your website’s design, and connects directly to Nova.Pay for products, payment plans, customers, coupons, payments, Pix, boleto, and card processing.

Download the Checkout Skill

Get the skill package, including its complete Nova.Pay API reference.

Explore the Checkout API

Understand the pages, payment plans, customer, and payment resources used by the generated checkout.

Before You Start

Have these details ready before asking the AI agent to build the checkout:
Never place a private API key or raw card data in browser code. The public checkout endpoints are protected by the allowed-host configuration, and card data must be tokenized client-side with the payment gateway SDK.

Create the Checkout

1

Download and install the skill

Download the Nova.Pay Checkout Skill, extract it, and add the folder to the skills directory used by your AI coding agent. The package contains:
  • SKILL.md — the checkout-building workflow and safety requirements
  • references/api-reference.md — the request and response schemas used during implementation
Restart or reload your agent if it does not discover newly installed skills automatically.
2

Authorize your checkout domain

Open your tenant’s integrations page and add the domain that will serve the checkout:
For local development, use checkout.lvh.me and run the site at:
lvh.me resolves to 127.0.0.1, while preserving a hostname that can be registered as an allowed host. If the form expects a complete origin, add http://checkout.lvh.me:5173.
3

Prompt the AI agent

Open the project where the checkout should be created and give the agent your tenant and checkout page UUID. Start with a simple prompt:
The agent should inspect the existing design system, ask for missing information, and use the installed skill to implement the complete purchase flow.
4

Review the generated experience

Confirm that the page loads products and payment methods from Nova.Pay rather than hardcoding them. Depending on the checkout configuration, the generated UI can include:
  • product quantities and order bumps
  • coupons and recalculated payment plans
  • customer and billing-address fields
  • credit-card installments and two-card payments
  • Pix QR code, copy-and-paste code, expiry, and status polling
  • boleto download and payment-status polling
  • scheduling, subscriptions, upsells, and tracking parameters
  • branding from the checkout page’s logo, colors, title, and custom code
5

Test before publishing

Run the local server on port 5173, open http://checkout.lvh.me:5173, and verify the checkout with your Nova.Pay test configuration.Check the browser console for actionable API diagnostics. A 403 response normally means the current hostname is not registered as an allowed host. A 422 response contains validation messages that the checkout should show without clearing the customer’s form.
6

Deploy on your own server

Deploy the generated site to the authorized production domain. Add the exact production hostname or origin to the tenant’s allowed hosts, then run an end-to-end payment test before sending traffic to the page.

What the Skill Implements

The skill instructs the agent to build this flow in order:
The AI agent generates the interface and integration code; Nova.Pay remains the source of truth for products, prices, payment plans, checkout settings, and payment results.

Launch Checklist

  • The API base URL is derived from the tenant: https://{tenant}.pay.nova.money/api/v1
  • The production origin is registered in the tenant’s allowed hosts
  • Products, order bumps, payment methods, and installments come from Nova.Pay responses
  • Card data is tokenized with Pagar.me or Stripe and never sent raw to Nova.Pay
  • Pix and boleto screens poll until the payment reaches a final status
  • Coupon, UTM, scheduling, subscription, and upsell behavior match the checkout configuration
  • Customer-facing errors are concise and the browser console contains safe diagnostics
  • Logs exclude card data, tokens, CPF/CNPJ, customer details, and full payment request bodies
Keep the installed skill in the project while iterating. You can ask the agent to restyle the page, add fields, or troubleshoot the integration without losing the Nova.Pay-specific implementation rules.