How to handle recurring payments.


mPAY24 offers the possibility to save customer specific payment details for further use. The payment details are stored by mPAY24 as interactive or recurring profiles.

  • Interactive profiles are dedicated to improve the user buying experience as most payment details are stored and do not have to be entered again. If necessary, additional payment details such as CVC2 (CVV) for credit card transactions have to be entered to complete the transaction.

  • Recurring profiles should be used in scenarios where the merchant triggers the payment without user interaction (e.g. monthly payable subscriptions).


This function may not be enabled for your mPAY24 account. Contact the mPAY24 Support for further information.

Stored information

mPAY24 stores the payment details specified by the customer and the billing address, if provided. It is not possible to return the complete profile information to a merchant due to security reasons. If a transaction is initiated with a profile, all necessary details are provided to the financial institution.

Customer ID format

The merchant can choose the format for the customerID as long as it is compliant with the following requirements.

  • Adhere to the restraints of the mPAY24 interface (e.g. allowed characters, length, ...)
  • Contains no critical or sensitive information even in encrypted form (e.g. credit card number, ...)

Reuse of customer IDs

If a customerID should be reused, the merchant has to ensure that all old payment data linked to the profile has been deleted correctly by using the DeleteProfile call. The merchant takes the responsibility for possible misuse of payment data due to careless implementations.


mPAY24 recommends not to reuse already used customer IDs.

Invalid payment profiles

It is the merchants responsibility to delete invalid profiles and to notify the customer in an appropriate manner.

The merchant can use the ListProfiles call to retrieve expired (or soon expiring) profiles or is notified about the validation by the Confirmation Interface when a transaction has been initiated.