Subscription

ℹ️
Payment Plan Subscription: Sandbox integration already available
The new Subscription payment plan is already ready for integration and testing. Merchants can build, test and refine the subscription flows right now using the sandbox environment.
Please note: The official production release is scheduled for September 2026, meaning the payment plan will only become active and usable in the merchant production environment starting then.

Payment Flow

Endpoints

Action	Endpoint
Request Payment	`POST /payments`
Retrieve Consent	`GET /consents`
Request Authorization	`POST /authorizations`
Retrieve Authorization	`GET /authorizations`
Retrieve Capture	`GET /captures`
Make Refund	`POST /{paymentId}/refunds`
Retrieve Refund	`GET /{paymentId}/refunds`
Initiate Payment	`POST /{paymentId}/authorizations`
Cancel Subscription	`DELETE /{paymentId}/consents`

Description

A Subscription (or Recurring Payment) is an agreement that allows a merchant to initiate subsequent, automatic payments from a payer's account at pre-defined intervals (e.g., WEEKLY, MONTHLY or YEARLY). After the payer grants the initial consent and their bank authorizes the mandate, all future transactions are executed automatically without requiring the payer's manual intervention for each billing cycle.

Typical use cases/scenarios

Subscriptions are beneficial for all merchants who arrange recurring payments with their customers at fixed amounts and fixed time intervals (i.e., classic subscriptions).

Merchant provides a service or a product to be paid regularly
- Example: insurance premiums, utility installments, magazine subscriptions
The business model relies on regular, physical deliveries to the customer's doorstep
- Example: Monthly curation boxes (e.g., pet food, coffee beans, or cosmetics)
The payer wants continuous, uninterrupted access to a digital service
- Example: Video or music streaming platforms
The customer secures long-term membership benefits or local services
- Example: Gym memberships or public transport season tickets (e.g., monthly/yearly commutes)

Key characteristics

Use Case: SUBSCRIPTION
Lifecycle: PENDING → SUCCESSFUL/FAILED
Authorization: The payer bank confirms the payment in real time
Timeouts: A payment session remains valid only for a limited period of time (10 minutes). If the payer doesn't complete the payment flow and approves the payment consent, the payment expires.

Recommendations

When using Wero, it is recommended to perform the status check multiple times (or long polling), since — for technical reasons — it can occasionally take more than just a few seconds until a payment capture is successfully completed.
Merchants should not delete transactions that appear to be stuck in a pending capture status. Instead, if the merchant wishes to discontinue with the payment, such transactions should be cancelled properly.

Merchant benefits:

Predictability: steady recurring revenue streams, easier financial forecasting.

Retention: automated renewwals reduce sustomer churn, increasing Customer Lifetime Value.

Efficiency: automated billing cycles, minimized manual invoicing and administrative overhead.