SEPA API-only
Introduction
SmartPay supports SEPA Direct Debit integrations without the use of the Web SDK. This approach is intended for merchants who prefer to handle mandate presentation and signing directly within their own user interface, and it is designed for merchants who want full control over the customer experience. In the API-only flow, mandate handling is entirely managed by the merchants. Merchants are responsible for collecting and storing the mandate acceptance from the customer and must ensure compliance with SEPA requirements, including auditability and legal validity of the mandate.
The API-only option is available for both B2C (Core) and B2B mandates, and examples below outline both cases.
SEPA Mandate Management
SEPA mandate management allows merchants to programmatically create, retrieve and manage SEPA mandates for recurring payment scenarios, such as subscriptions or installment-based transactions. A SEPA mandate is a legal authorization signed by the consumer, permitting the merchant to collect payments via SEPA Direct Debit. These mandates are a prerequisite for initiating SEPA-based transactions and must be securely stored and referenced for all related payment flows.
Mandate details can be retrieved and managed through dedicated endpoints, enabling streamlined integration into merchant onboarding workflows or recurring billing systems.
This API-only offering is designed specifically for SEPA Direct Debit use cases and supports both private consumers (B2C) and business customers (B2B), following the two SEPA schemes which will be outlined in the examples below. Mandates created via API are compliant with SEPA regulations, including mandatory fields such as mandate reference, Creditor Identifier, and signature timestamps.
For SEPA Core (B2C) payments, J.P. Morgan Mobility Payments Solutions S.A. always acts as the creditor, with mandates created, signed and stored on behalf of JPM MPS. For SEPA B2B payments, the creditor can be either JPM MPS or the merchant, depending on the configuration. Merchants acting as creditors for B2B payments are responsible for managing the full mandate process independently. Mandate management is required to use a merchant-specific Creditor Identifier and to support both SEPA Core and B2B transaction. For more information, please refer to our SEPA integration options table.
SEPA mandate consists of:
-
Creditor segment - data and identification of the payee:
- Name and address of the creditor
- Creditor Identifier Number = financial authority issued identification of Creditor in SEPA schema
-
Mandate information:
- Mandate Reference = unique reference of this SEPA mandate. It needs to be unique in the scope of a creditor reference
- Mandate type = recurring or one-off
- Mandate legal information
-
Debtor segment - data and identification of the customer:
- Name and address of the debtor
- Bank Account Number used for the direct debit
- SWIFT/BIC - Bank Identification
This SEPA mandate management solution is intended to be used to support the processing of SEPA direct debit payments, but not for management of the actual mandate documents.
It is the client's obligation to:
- Collect all data relevant for the mandate
- Create a mandate document and ensure that it is signed by the debtor / customer
- In case of B2B mandates to ensure that customer has submitted to the customer's bank prior first payment authorization
- Submit all required fields as on the original mandate document
- Archive the "paper" mandate
A creditor identification number is assigned to a debtor by the respective member state's financial authority. The mandate management solution can be used with an own Creditor Identifier or using J.P. Morgan Mobility Payments S.A.'s general Creditor Identifier. Your Product Solution Specialist can support you with the right setup for your use case.
SEPA mandate management is an alternative service to the widget-based SEPA Core processing, designed for merchants who create and manage SEPA mandates in their own workflows. Parallel use of mandates in mandate management solution and processing of SEPA Core mandates created via SmartPay / Subscription web forms is not supported. Please contact your Product Solution Specialist or Key Account Manager for further information.
Base URLs & additional details
| SANDBOX | PRODUCTION | |
|---|---|---|
| API Base URL | https://mandatemgmt.cons.shared.upcf.jpmmps.com/api/v1/mandates | https://mandatemgmt.shared.upcf.jpmmps.com/api/v1/mandates |
| Merchant Key | Provided by Product Solution Specialist | Provided by Key Account Manager |
| API Authentication Key | Provided by Product Solution Specialist | Provided by Key Account Manager |
Further details of data model used in mandate management, please visit the Data Model.
Creditor Identification Data
Each mandate requires data of the creditor for the mandate. Your Product Solution Specialist can help you to assess the correct setup for the creditor data. Mandate management solution supports both — the use of merchant specific creditor identification, passed via create mandate API or use of pre-configured creditor identification data, which would be returned in create mandate response.
Supported Mandate Schemes
The current release of mandate management solution supports SEPA mandates: mandateScheme = "SEPA_B2B" or "SEPA_CORE"
Please refer to the data model for more details on mandate objects.
Mandate Management APIs
For a complete overview of available mandate operations, please refer to our API-Reference: