Consent Management APIs provide the capability to manage consents in a web application, on behalf of an end-user. A banking service consumer/ Account Servicing Payment Service Provider (ASPSP) may need to develop their own web application or use their own mechanism to deploy the consent management capabilities. At this point, a service provider needs a way to directly present consent resources to the end-user. In order to cater to this requirement, those consent capabilities (for example, consent creation/consent deletion) are presented as API resources in the Consent Management APIs.
The Payment Consent API provides payment consent capabilities as API resources.
You can find the REST API documentation for Payments Information Sharing Consent Management APIs below:
The following section contains sample requests and responses to the Payment Information Sharing Consent Management v1.3.0 resources.
Create payment consent resource
Creates a payment initiation resource addressable under {paymentId} with all data relevant for the corresponding payment product. This is the first step in the API to initiate the related payment.
POST /berlin130/payments/{payment-service}/{payment-product}
Retrieve payment consent resource
This resource retrieves the addressed consent resource.
GET /berlin130/payments/{payment-service}/{payment-product}/{paymentId}
Retrieve the status of a payment consent resource
Reads the transaction status of the addressed consent resource.
GET /berlin130/payments/{payment-service}/{payment-product}/{paymentId}/status
Remove payment consent resource
Deletes the consent resource with the given paymentId.