Skip to main content
Checkout pages are the hosted payment forms you create in Nova.Pay. Each page can carry one or more products, accept multiple payment methods, and be customised with your brand colours and logo. The endpoints below let you programmatically list your pages, fetch their full configuration, and inspect the payments that have been made through them. Base URL: https://yourcompany.pay.nova.money/api/v1

List checkout pages

Authentication is required for all checkout-page endpoints. Pass your API key in the Authorization header as a Bearer token.
Retrieve a paginated list of your checkout pages. You can narrow the results with the optional query parameters below.

Query parameters

string
Free-text search string. Matches against the page title and other indexed fields.
boolean
When true, only returns pages that have at least one product attached. When false, returns pages with no products.
array of integers
Filter pages to only those that include any of the specified product IDs. Pass multiple values as repeated query params: product_ids[]=1&product_ids[]=2.

Response

Returns an array of CheckoutPageSummary objects.
Example response

Complete JSON response

This example includes every response property defined for this operation in the OpenAPI schema.

Retrieve a checkout page

Fetch the full configuration for a single checkout page by its UUID.

Path parameters

string
required
The UUID of the checkout page.

Response

Returns a CheckoutPageShow object, which extends CheckoutPageSummary with the full set of fields listed below.
string (uuid)
Unique identifier for the checkout page.
string
Specifies at which step of the checkout flow customer data is collected. Typical values are "start" or "end".
string
The payment gateway configured for this page (e.g. "stripe", "pagarme").
string
Hex colour code used as the primary brand colour on the hosted page.
string
The display title shown to customers on the checkout page.
URL of the logo image displayed on the checkout page.
string
ISO 4217 currency code (e.g. "BRL", "USD").
array
Navigation menu items configured for the page.
string
The gateway public key used to tokenise card data on the client side.
boolean
Whether the checkout page is configured for recurring / subscription billing.
boolean
Whether coupon code entry is enabled on this page.
boolean
When true, the hosted page allows indexing by search engine crawlers.
boolean
When true, the customer must select a scheduled date before completing checkout.
boolean
When true, the customer may split the payment across two credit cards.
integer
ID of the Nova.Pay company that owns this checkout page.
object
An optional product offered as an upsell after the main purchase.
string
Arbitrary HTML/JS snippet injected into the hosted page (e.g. tracking pixels).
object
The pre-selected payment plan shown to the customer on page load.
object
Third-party integration configuration (webhooks, analytics, CRM connections, etc.).
array
The products attached to this checkout page.

Complete JSON response

This example includes every response property defined for this operation in the OpenAPI schema.

Get the Belluno card hash key

Retrieve the RSA public key required to encrypt card data before creating a payment through Belluno.
This endpoint is available only when the checkout page uses the belluno gateway and its company has a configured Belluno integration.

Path parameters

string
required
The CheckoutPage UUID.

Response

Returns the Belluno CardHashKey object exactly as provided by Belluno.
integer
Identifier of the generated card hash key.
string
RSA public key in PEM format. Use it to encrypt card data in the client, then submit the resulting hash as the card token to POST /payments.
string
ISO 8601 datetime when the key was created.
Example response

Errors

A 422 response contains an errors field as either a string or an array of strings.

List payments for a checkout page

Returns all payments submitted through a given checkout page.

Path parameters

string
required
The UUID of the checkout page.

Query parameters

array
Filter the results to specific payments. Each value may be either a gateway_id (e.g. "pay_abc123") or an internal payment ID. Pass multiple values as repeated query params: ids[]=pay_abc123&ids[]=pay_def456.

Response

Returns an array of PaymentStatus objects, or HTTP 204 No Content if no payments have been made through this page yet.
Example response
string
The payment identifier issued by the gateway (e.g. a Stripe PaymentIntent ID).
string
Current status of the payment. Common values: paid, waiting_payment, failed, cancelled.