Introduction

A payment consent is an authorization from a customer that allows you to initiate payments on their behalf without requiring further customer involvement. This is commonly used for recurring payments such as bills, subscriptions, and memberships.

How Payment Consents Work

Before a payment consent can be used to initiate payments, the customer must sign it. This signing step is handled through a Payment Consent Signing flow. When creating the signing request, make sure to select the correct provider and method based on how the consent will be used.

Creating a New Payment Consent

To create a new consent and start the signing flow, use the Initiate Payment Consent Signing endpoint. If you want to receive webhooks whenever the consent status changes, include a status_callback_url in your request.

📘
Important! Store the ID of the created consent. You will need this ID later when initiating payments using the consent.

You can retrieve the details and current status of a consent at any time using the Get Payment Consent endpoint.

Available payment consent providers and methods

Provider	Method	Flow	Description
`autogiro`	`bankgirot`	`redirect`	Initiates an Autogiro mandate (autogiro medgivande). The customer verifies their consent through a redirect-based signing flow.
`swish`	`recurring`	`e_commerce` / `m_commerce`	Creates a Swish Recurring payment consent, allowing the customer to approve future recurring Swish charges. The customer confirms the consent via either the e-commerce or m-commerce flow.

Simulate consent status updates in sandbox

To simulate consent status updates in the sandbox environment, use the Mimic API and the Update Consent endpoint. When you trigger a simulated status change, callbacks will be sent to the status_callback_url (if one was provided when the consent was created).