Search

EP-4736101-A1 - CARD ON FILE ENROLMENT METHOD AND SYSTEM

EP4736101A1EP 4736101 A1EP4736101 A1EP 4736101A1EP-4736101-A1

Abstract

A method of enrolling a payment card as a card on file by a payment processing platform. The method comprising the steps of: receiving, from a card issuer platform associated with the payment card, a registration request comprising data associated with the payment card; storing, on a secure storage means, the data associated with the payment card; sending, to the card issuer platform, a registration receipt; receiving, from a merchant platform, the registration receipt; generating a merchant token; and sending, to the merchant platform, the merchant token useable as a card on file.

Inventors

  • BUSSOLOTTI, LUCA

Assignees

  • Mastercard International Incorporated

Dates

Publication Date
20260506
Application Date
20240617

Claims (15)

  1. 1. A method of enrolling a payment card as a card on file by a payment processing platform, the method comprising the steps of: receiving, from a card issuer platform associated with the payment card, a registration request comprising data associated with the payment card; storing, on a secure storage means, the data associated with the payment card; sending, to the card issuer platform, a registration receipt; receiving, from a merchant platform, the registration receipt; generating a merchant token; and sending, to the merchant platform, the merchant token useable as a card on file.
  2. 2. The method of claim 1, wherein the registration request comprises data associated with the payment card.
  3. 3. The method of any preceding claim, wherein the registration request is received from the card issuer platform via a push provisioning API.
  4. 4. The method of any preceding claim, wherein the registration receipt comprises a unique identifier associated with the payment card.
  5. 5. The method of any preceding claim, wherein the registration receipt is received from the merchant platform via an enrolment API.
  6. 6. The method of any preceding claim, further comprising storing a copy of the merchant token in the secure storage means.
  7. 7. The method of claim 6, further comprising storing an indicator in the secure storage means, the indicator arranged to associate the merchant token with the data associated with the payment card.
  8. 8. The method of any preceding claim, further comprising: determining that a cardholder associated with the payment card is not already registered for the digital payment solution.
  9. 9. The method of claim 8, wherein determining that the payment card is not already registered for the digital payment solution comprises: receiving one or more cardholder details associated with the cardholder; and determining that the one or more cardholder details are not associated with digital payment solution account stored on the account database.
  10. 10. The method of any preceding claim, wherein the data associated with the payment card comprises data corresponding to at least one of: card primary account number, FPAN, email address, telephone number, address.
  11. 11. The method of any preceding claims, further comprising: receiving, from the merchant platform, a transaction request comprising the merchant token and transaction details; and initializing an authorization process.
  12. 12. The method of claim 11, wherein the transaction details comprise at least one of: a transaction amount; a transaction currency; and a transaction id.
  13. 13. The method of claim 11 or claim 12, wherein initializing the authorization process comprises: verifying that the merchant token is valid; and sending an authorization request to the card issuer platform including the transaction details.
  14. 14. The method of claim 13, wherein verifying that the merchant token is valid comprises comparing the merchant token to the merchant token stored on the secure storage means.
  15. 15. A payment processing platform comprising: a secure storage means; and one or more processors adapted to perform the steps of any of claims 1 to

Description

CARD ON FILE ENROLMENT METHOD AND SYSTEM CROSS-REFERENCE TO RELATED APPLICATION This application claims the benefit of, and priority to, Italian Patent Application No. 102023000013695, filed June 30, 2023. The entire disclosure of the above application is incorporated herein by reference. FIELD OF THE DISCLOSURE The present disclosure relates to a card on file enrolment method and system. BACKGROUND Many remote e-commerce payment platforms exist currently which allow a customer to pay for their products on an e-commerce site with very little friction. However, the enrolment of users into those e-commerce platforms is complex and requires multiple user interactions with online forms. These requirements, in particular the multiple user interactions, induce friction in the customer enrolment procedure which can cause potential customers to abandon the enrolment journey prior to completing it. This reduces customer uptake of e-commerce payment platforms that provide a higher quality of user interaction over the classic approach of entering payment card details into an online form, leading to increased complexity of user interaction in the long run and more complex and computationally intensive requirements for processing of payments compared to specialist e-commerce payment platforms. Currently, a cardholder wishing to onboard or enrol with a merchant that requires card details to be stored, for example to maintain a subscription for a service, has to manually enter card details associated with a payment card. The payment card may be either a soft, virtual card or a physical card having an associated personal account number (PAN). Such manual entry may require multiple user interactions with online forms, for example when entering a card number associated with the payment card, which may in turn induce friction in the customer enrolment procedure, which can cause potential customers to abandon the enrolment process prior to completion. Accordingly, customer uptake of merchant goods or services may be reduced due to the friction introduced by this manual card detail entry process. Additionally, once card details have been entered, the cardholder may also have to authenticate themselves, for example via a mobile banking app which uses two factor authentication for security to ensure that it is the cardholder who is utilising the payment card. This further increases the number of user interactions required to register a payment card. The present disclosure has been devised to mitigate or overcome at least some of the above-mentioned problems. SUMMARY OF THE DISCLOSURE In accordance with a first aspect of the present disclosure, there is provided a method of enrolling a payment card as a card on file using a payment processing platform, the method comprising the steps of: receiving, from a card issuer platform associated with the payment card, a registration request comprising data associated with the payment card; storing, on a secure storage means, the data associated with the payment card; sending, to the card issuer platform, a registration receipt; receiving, from a merchant platform, the registration receipt; generating a merchant token; and sending, to the merchant platform, the merchant token useable as a card on file. The proposed method may advantageously provide a means for enrolling a card on file without requiring an input from a user adding their payment card details to a merchant service. In particular, the enrolment of the card on file may occur at backend systems, with communication between the card issuer platform, the merchant platform, and the payment processing platform. Additionally advantageously, the proposed method may reduce an amount of data sent by a user computing device. In particular, the user computing device may not have to transmit data representing their payment card details to the merchant platform. Instead, transmission of payment card data may occur between the payment processing platform and the card issuer platform. These platforms may be optimized for such data transfer, for example using encrypted and secure communication channels, and as such, data transfer may also be optimized. Further advantageously, due to the use of a merchant token, the merchant platform may never receive or store user information such as funding primary account number (FPAN), address, or any other relevant information. In particular, the merchant platform may initiate a transaction by sending the merchant token to the payment processing platform along with transaction details. Instead, this information may be stored on the card issuer platform and/or the payment processing platform. Thus, sensitive information associated with the user or cardholder may be secured in few places, and may also be less vulnerable. Strong customer authentication (SCA) may be standardized and performed by an issuer mobile banking application stored on the user computing device. Thus, a user or cardholder taking part