Subscriptions Overview

Use subscriptions when you need to charge the same customer on a recurring schedule. Two payment methods are available:

	Card	Pix Automático
How the customer pays	card collected with Payment Element	authorizes once with a QR code in their bank app
Who starts each charge	Pagou	the payer’s bank
`payment_method`	`credit_card` (default)	`pix_automatic`
Guide	Create a Subscription	Pix Automático Subscriptions

How it works with a card

Create the customer with POST /v2/customers.
Collect the card with Payment Element in mode: "subscription".
Send the single-use pgct_ token to your backend.
Create the subscription with POST /v2/subscriptions.
Listen to subscription webhooks for renewals, failures, updates, and cancellation.

Create the customer with POST /v2/customers, including a CPF or CNPJ.
Create the subscription with POST /v2/subscriptions and payment_method: "pix_automatic".
Show the returned QR code to the payer, who authorizes the recurring debit in their bank app.
Listen to subscription webhooks for the authorization, each debit, failures, and cancellation.

Surface	Use it for
`/v2/customers`	customer record used by the subscription
Payment Element	secure card collection and `pgct_` tokenization, for card subscriptions
`/v2/subscriptions`	create, list, retrieve, update, and cancel subscriptions
Subscription webhooks	lifecycle events such as created, renewed, failed, and canceled

Create subscriptions only from your backend.
Store the Pagou subscription id, customer id, and latest transaction id.
Use webhooks as the normal source of truth for lifecycle changes.
Reconcile with GET /v2/subscriptions/{id} when a renewal or cancellation outcome is unclear.
Move a card subscription between plans with PATCH /v2/subscriptions/{id}; create a new subscription only to change the currency or the card. Pix Automático subscriptions cannot change plans.

See working, testable code for the card flow in the Subscriptions examples — runnable in seven languages against the sandbox.