Cross-Reference to Related Applications

[0001] The present patent application claims the benefits of priority of US Provisional Patent Application No. 62/255,713, entitled "Method and System for Authenticating Electronic Certificates Using a Mobile Device" and filed at the United State Patent and Trademark Office on November 16, 2016.

Field of the Invention

[0002] The present invention generally relates to the field of computer implemented inventions. More specifically, the present invention generally relates to methods and systems for authenticating electronic certificates via a client device, and more particularly to methods for authenticating electronic certificates using a client device for the purpose of promotional and distribution campaigns and other similar purposes. The present invention also relates to methods for evaluating and supplying accounting and statistical information to issuers of electronic certificates.

Background of the Invention

[0003] Over recent years, several solutions have been considered in order to bypass the costs attached to paper-based coupons, vouchers or bonds, in terms of printing, handling, and environmental costs, and alternatives have been brought up using electronic coupons (e-coupons).

[0004] Solutions proposed have evolved over the recent years in accordance with the evolution of communication technologies. Still the proposed solutions are facing different issues and problems.

[0005] As an example, a coupon generating system may produce electronic barcodes to be displayed on a mobile device or using a computer application configured to be run on the said mobile device. As the barcode is electronically displayed on the screen of the mobile device, such barcode may be easily copied by someone or a device looking at the screen. Also, the use of barcodes implies that existing point-of-sale equipments are configured to work with a scanning apparatus.

[0006] A prior art solution disclosed in the U.S. patent application No. US 2009/0132380 Al (Tymms) teaches the use of the existing card payment equipment in place at many points of sale. Such solution addresses the problem of electronically redeeming cash value vouchers and avoiding directly interfacing the mobile device with the merchant's transaction system in order to redeem the voucher.

[0007] Other solutions propose a system configured for a mobile device to directly interact with the retailer's transaction system in order to redeem the coupon. Such systems typically require the retailer to own specific equipment and/or to develop new software or adapt existing software for the system compatible with such solutions As software development may be lengthy and costly, retailers are typically reluctant to do so.

[0008] In US 2006/0178932 Al (Lang), a method and system allowing the distribution of electronic coupons based on the geographic location of customers at a given moment relative to potential stores are disclosed. Such system may bring undesired results with regard to the selection of customers and/or stores, as well as to the respect of personal information of potential customers.

[0009] In US 2003/0074259 Al (Slyman), a method for redeeming electronic coupons is disclosed. Such method teaches an electronic device configured to receive a merchant authentication identifier into the mobile device as a function of the current status of the electronic coupon. The current status is set to a final status as a function of the current status and the validity of the merchant authentication identifier. However, such system requires the existence of a third server for establishing the communication between the point-of-sale and the mobile equipment.

[0010] Currently, 3-6 months are typically required to process paper coupons. Furthermore, the retailer typically receives the refund only after such processing is completed. Also, the performance of a promotional campaign may be hard or nearly impossible to evaluate given the absence of readily available data.

[0011] Therefore, despite ongoing developments in the field of methods for authenticating electronic certificates, there is a need for novel method and system for authenticating electronic certificates in a mobile device that can at least mitigate some of the shortcomings of the prior art.

Summary of the Invention

[0012] In a first aspect, a method for authenticating electronic certificates provided by an issuer for at least one customer using a client device is provided. In at least one embodiment, the method comprises creating a campaign for at least one point of sale (POS) on a certification server, the campaign comprising emission of at least one benefit; the at least one POS accepting the campaign; issuing a certified code associated with the at least one coupon to at least one client device; the client device requesting authentication of a unique identifier associated to the POS to the certification server using the certified code; and the certification server communicating confirmation of certification of the campaign to the client device.

[0013] In at least one embodiment, the method may further comprise issuing the unique identifier associated with the campaign to the at least one POS having accepted the campaign.

[0014] In at least one embodiment, the method may further comprise reading the identifier using the client device. In at least one embodiment, the scanning unit of the client device may be used to read the identifier.

[0015] In at least one embodiment, the method may further comprise, upon receiving request for authentication, the certification server verifying compliance of the identifier with parameters of the campaign.

[0016] In at least one embodiment, the method may further comprise the at least one POS accepting the campaign by using instructions received in a notice communicated by the certification server to the POS.

[0017] In at least one embodiment, the confirmation of certification of the campaign may be displayed on the client device using a certification display. The confirmation of certification may be displayed using a stack of layers comprising at least a visual sign confirming approval from the certification server. The stack may further comprise visual means for rendering the confirmation difficult to reproduce. The stack may further comprise a means ensuring real time confirmation.

[0018] In at least one embodiment, the method may further comprise saving a list of certified codes on the client device and synchronizing the list of certified codes with the certification server. In at least one embodiment, the synchronizing of the list of certified codes may further comprise the certification server checking if certified codes of the list are valid. The synchronizing of the list of certified codes may further comprise issuing a bundle of the list of certified codes in relation to associated POS identifiers to the client device and storing the bundle as a last known bundle (LKB) on the client device. In at least one embodiment, the bundle may comprise a validity timestamp. In at least one embodiment, the list of certified codes and the LKB may be stored on the client device using a local certified client (LCC).

[0019] In at least one embodiment, any of the client device and the certification server being disconnected from a network, the method may further comprise finding a matching POS identifier in the LKB, the LKB being identified by a timestamp; and considering any one of the certified codes valid if the current timestamp is inferior to the sum of the timestamp of the LKB and the predetermined offline duration.

[0020] The method may further comprise updating the bundle by adding at least one of the current timestamp and the DRS/POS identifier. The coupon may be selected in the group of an electronic certificate, a bond or a voucher. In at least one embodiment, the at least one POS accepting the campaign may use a validation number.

[0021] In a second aspect, there is a system for authenticating electronic certificates provided by an issuer using a client device of a prospective customer at one or more point of sale (POS). In at least one embodiment, the system comprises a certification server executing a program configured to: create and store a campaign for at least one POS on the certification server, the campaign comprising emission of at least one coupon; notifying the at least one POS of the created campaign; receiving acceptation of the campaign by the POS; issuing a certified code associated with the at least one coupon to at least one client device; authenticating a unique identifier associated with the POS using a received certified code; communicating confirmation of certification of the campaign to the client device. The client device may comprise a display, a CPU, a storage unit and a memory unit. The system further comprises the client device being configured to store the certified code issued by the certification server in the storage unit; request authentication of the identifier to the certification server using the certified code; display a certification of compliance of the coupon if the authentication succeeds. The system may further comprise a communication network connected to the certification server.

[0022] In at least one embodiment, the certification server may be further configured to issue a unique identifier associated with the campaign to the at least one POS having accepted the campaign. The client device may further comprise a local certification client. The client device may be further configured to read the identifier. The client device may further comprise a scanning mean adapted to read the unique identifier. The scanning mean may be a camera integrated in the client device. The client device may further comprise a communication mean adapted to receive the unique identifier. The communication mean may be a wireless communication unit. The communication mean may be a near-field communication (NFC) or radio- frequency identification (RFID) reader.

[0023] The client device may comprise an application configured to communicate with the certification server. The client device may be a mobile device. The mobile device may be a smart phone. The client device may be further configured to display a confirmation of compliance using a certification display.

[0024] The client device may be further configured to display the certification display using a stack of layers comprising at least a visual sign confirming approval from the certification server. The stack may further comprise visual means for rendering the confirmation difficult to reproduce. The stack may further comprise a means ensuring real time confirmation. The client device may be further configured to retrieve parameters of the campaign.

[0025] In at least one embodiment, the client device may be further configured to store a list of certified codes; and synchronize the list of certified codes with the certification server. The synchronizing of the list of certified codes may further comprise the certification server checking if certified codes of the list are valid. The certification server may be further configured to issue a bundle of the list of certified codes in relation to associated POS identifiers to the client device and the client device being further configured to store the bundle as a last known bundle (LKB).

[0026] In at least one embodiment, any of the client device and the certification server being disconnected from the network, the client device may be configured to find a matching POS identifier in the LKB, the LKB being identified by a timestamp, and to consider any one of the certified codes valid if the current timestamp is inferior to the sum of the timestamp of the LKB and the predetermined offline duration.

[0027] In at least one embodiment, the unique identifier may be a hash tag. In at least one embodiment, the unique identifier may be a RFID tag.

[0028] The present invention generally relates to computer- implemented methods and systems for authenticating electronic certificates or coupons in a client device, for instance for the purpose of promotional and distribution campaigns and other similar purposes. The present invention also relates to methods for evaluating and supplying accounting and statistical information to issuers of electronic certificates.

[0029] In a first aspect of the invention, a method for authenticating electronic certificates provided by an issuer via client devices of recipient prospective customers (RPC) is provided. The method comprises the steps of conceiving or configuring parameters of a standalone campaign by the issuer for designated retailer stores or points of sale (DRS/POS) in connection with goods sold and/or services offered by the DRS or POS, the campaign comprising the emission of at least one electronic certificate, bond, voucher or similar coupon, sent to each RPC, allowing each RPC to participate to the campaign when purchasing said goods and services at the DRS/POS, storing the configured parameters of the campaign of step a) via an interface of a software platform provided by a Certification Authority Service Provider (CASP), entrusting the CASP to send a designation notice to the DRS/POS, the designation notice prompting the DRS/POS to accept the campaign by sending a confirmation back to the CASP, entrusting the CASP to send to the DRS/POS that have accepted the campaign an identifying tag, entrusting the CASP to inform each RPC about the campaign via a computer program present on memory of the client device of each customer and executed on the client device, such as a mobile application, installed on the client device of each customer, entrusting the CASP to provide each RPC via the computer program with a Mobile Certified Code (MCC), entrusting the CASP, upon request for authentication by a RPC having a stored valid MCC on its client device, to read an identifying tag of a DRS/POS that has accepted the campaign and to proceed to verification of compliance with the campaign parameters and entrusting the CASP, when authentication has been accepted, to send a validation number and to arrange for a certification display (MCD) to be displayed on the client device in order for the RPC to participate to the campaign.

[0030] It is disclosed a method for authenticating electronic certificates provided by an issuer via client devices of recipient prospective customers (RPC), the method comprising the steps of allowing an issuer to authenticate/log to a server/computer executing a program, the program being configured to display interface such as a web interface, allowing the issuer to configure and/or set parameter of a standalone campaign using the interface, the parameters of the standalone campaign being established by the issuer for designated retailer stores or points of sale (DRS/POS) in connection with goods sold and/or services offered by the DRS/POS, the campaign comprising the emission of at least one electronic certificate sent to each RPC, allowing each RPC to participate to the campaign when purchasing said goods and services at the DRS/POS.

[0031] The computer or the server may be configured to execute a computer implemented platform being configured to perform at least the following steps for the issuer sending a designation notice to the DRS/POS using a communication network, such as the Internet, upon reception of the designation notice, the DRS/POS being prompted to accept the campaign by sending a confirmation back to the server using the communication network, for the the DRS/POS logging acceptance of the campaign on the computer implemented platform, generating an identifying tag and sending the identifying tag to the DRS/POS, the client device of each customer commutating with RPC to receive the campaign details using providing each RPC with a Mobile Certified Code (MCC) using the client device, upon request for authentication by the client device of a RPC, reading an identifying tag installed at the DRS/POS and proceeding to verification of compliance against the campaign parameters, the DRS/POS having accepted the campaign and the client device having a stored valid MCC; and when authentication has been accepted, sending a validation number to the RPC and arranging for a certification display (MCD) to be displayed on the client device in order for the RPC to participate to the campaign.

[0032] A system for authenticating electronic certificates provided via client devices of recipient prospective customers (RPC), the system comprising a communication network, such as a WAN, LAN or the Internet, between an issuer, a central non- transitory computer readable medium of a Certification Authority Service Provider (CASP) and designated retailer stores or points of sale (DRS/POS), a client device of a RPC configured to execute a computer program, the computer program, such as a mobile application, being configured to communicate with the network, said computer program being further configured to having storing features and to read tag. The central computer of the CASP is configured in order to store a software platform having an interface for registering parameters of a standalone campaign conceived by the issuer for the DRS/POS, to generate a designation notice to be sent to each DRS/POS for prompting each DRS/POS to accept the campaign by sending a confirmation back to the central computer readable medium, to provide the DRS/POS that have accepted the campaign with an identifying tag; to proceed to the selection of the RPC, in accordance with the campaign parameters, and to inform each RPC about the campaign via the mobile application, to issue at least one mobile certificate code (MCC) to each RPC via the network, upon request for authentication by the client device of a RPC, to read an identifying tag installed at the DRS/POS and to proceed to verification of compliance against the campaign parameters, the DRS/POS having accepted the campaign and the client device having a stored valid MCC; and upon acceptation of authentication of the RPC, to send a validation number and to arrange for a certification display (MCD) to be displayed on the client device in order for the RPC to participate to the campaign.

Brief Description of the Drawings

[0033] The above and other objects, features and advantages of the invention will become more readily apparent from the following description, reference being made to the accompanying drawings in which:

[0034] Figure 1 illustrates a diagram of a prior art overall system, with conventional validation at point of sale through retailer's server.

[0035] Figure 2 is a diagram of the different actors of a method and system in accordance with the present invention.

[0036] Figure 3 is a workflow diagram presenting the steps of an embodiment of Phase I of the method, in accordance with the principles of the present invention.

[0037] Figure 4 is a workflow diagram presenting the steps of an embodiment of Phase II of the method, in accordance with the principles of the present invention.

[0038] Figure 5 is a workflow diagram presenting the steps of an embodiment of Phase III, in accordance with the principles of the present invention.

[0039] Figure 6 is an illustration of a sample of an identifier for Designated Retail Store in accordance with the present invention.

[0040] Figure 7 is a diagram showing the multiple layered display on the screen of a client device, in accordance with the principles of the present invention.

[0041] Figure 8 depicts an example of the screen displayed on the client device for authenticating an electronic certificate in accordance with the principles of the present invention. [0042] Figure 9 depicts an example of the screen displayed on the client device for authenticating an electronic certificate in accordance with the principles of the present invention.

[0043] Figure 10 depicts an example of the screen displayed on the client device for authenticating an electronic certificate in accordance with the principles of the present invention.

[0044] Figure 11 is a workflow diagram presenting the steps of an embodiment of the method for refreshing a list of certified codes of the method while being online in accordance with the principles of the present invention.

[0045] Figure 12 is a workflow diagram presenting the steps of an embodiment of a method to authenticate a certificate while a client device is offline in accordance with the principles of the present invention.

Detailed Description of the Preferred Embodiment

[0046] A novel method and a system for authenticating electronic certificates in a client device will be described hereinafter. Although the invention is described in terms of specific illustrative embodiment(s), it is to be understood that the embodiment(s) described herein are by way of example only and that the scope of the invention is not intended to be limited thereby.

[0047] The preferred embodiments of the present invention are described below with reference to the drawing figures where like numerals represent like elements throughout.

[0048] Now referring to Figure 1, a typical method of the prior art is shown. A coupon 5, such as a paper coupon or an electronic coupon on a client device, is presented at the point of sale (also referred as POS) or a retailer store 7 for validation. The point of sale typical comprises a cash registry equipped with a reading device or other similar equipment. Upon reading of the coupon 5, the point of sale communicates with a retailer server 9, which performs necessary verification and compilation. As it is known in the art, a POS may be implemented as a computerized device or an electronic device comprising a central processing unit, memory and a storage unit. The POS is configured to communicate on a network.

[0049] The client device 130 may be a computer or a network device. For example, the client device 130 may be a mobile device. For example, the client device 130 may be a smartphone, a smart tablet, or a smart watch configured to run a program, such as a web browser or an application configured to connect to the software platform. For example, the client device 130 may be a device having a non-transitory computer- readable medium with instructions stored thereon, that when executed by a processor, may perform steps as described herein.

[0050] Understandably, the client device may be any type of computerized device such as a mobile device, a smart phone, a tablet, a smart watch or any device allowing to communicate with another device or to retrieve information from a passive tag.

[0051] Now referring to Figure 2, an embodiment of a system for authenticating electronic certificates in a client device 130 is illustrated. In such an embodiment, a producer, merchant, or other corporate or physical person 10 (also named "Issuer") may create a promotional or distribution campaign (also named "Campaign") for some goods and/or services. The Campaign is configured to present or offer some benefit (also named "Campaign's Object") to potential customers. The Campaign's Objects are typically free samples, coupon, vouchers, rebates, or tickets. Understandably, any other benefit could be offered without departing from the principles of the present invention.

[0052] A potential customer or selected recipient prospective customers 20 (also named "RPC") uses a client device 130. The client device 130 typically comprises a processing unit, such as a CPU, a storage unit, a memory unit and is configured to communicate with a network 25. The network 25 may be any communication network, such as, for example, local area network (LAN), wide area network (WAN), including the Internet, wireless LAN (WLAN), which may provide communication among devices as described herein.

[0053] The system may be configured to communicate or activate the Campaign's Object to the client device 130 at specific location, such as at some Designated Retail Stores 30 ("DRS") or at some specific points of sale (also named "POS"). Such locations are, generally, where such goods and/or services are to be made available. A Certification Authority Service Provider 40 ("CASP"), typically embodied as a server computer ("CAS"), is configured to run a software platform. The software platform allows the Issuer to log and to enter the Campaign parameters. [0054] Now referring to Figures 3 to 5, a method for authenticating electronic certificates in the client device 130 in accordance with a preferred embodiment is shown. The method 500 may comprise a step 510 to create a Campaign using a software platform 100 ("Platform") running on the CASP 40.

[0055] In a preferred embodiment, the Platform comprises instructions configured to run on a computer or server, such as the CASP. The Platform is configured to display a user interface on a computerized device, such as a computer, a smart phone, a tablet or any other device comprising a CPU, a non-transitory computer-readable medium and a display device (also referred as the "Issuer device"). In a preferred embodiment, the Platform is hosted on a web server and is configured to display a web page on a browser software or on a application running on the computerized device.

[0056] In a typical embodiment, the Issuer device 130 communicates with the CASP 40 using the network 25 to send information and parameters of the Campaign. The CASP 40 may be configured to receive the parameters of the Campaign and to store the Campaign in a data source.

[0057] In some embodiments, the CASP 40 may be configured to require the Issuer device 130 to authenticate with the CASP 40 prior to create the Campaign.

[0058] The Campaign parameters may comprise a list of DRS 30, the objects of the Campaign, i.e. the goods and/or services covered, the rebates granted, if any, the costs and payments required, if any, and the parameters, if any, or any criteria, including specific identification, of RPC 20 targeted for the Campaign. RPCs' selection options may comprise specific identifications provided by Issuer, together with means allowing CAS to contact them, or identification of parameters, leaving CAS to perform the selection, on criteria such as, without restriction, interests expressed on social networks, such as Facebook™, or other identifiers such as age, gender, language, territory, profession, etc.

[0059] In a preferred embodiment, the CAS may be a computerized device having a non-transitory computer-readable medium with instructions stored thereon, that when executed by a processor, may perform steps as described herein.

[0060] Still referring to Figure 3, the method may further comprise sending a designation notice (the "Notice") to each of the DRS 30 and/or POS at step 520. Each DRS/POS 30 is configured to receive the Notice and, if the Notice is compliant, to accept the said Notice by sending a confirmation of acceptance. The sending of the Notice to each DRS/POS 30 may be done by physical mail, by electronic communication or any other mean allowing a sufficient level of security.

[0061] The method further comprises accepting the Notice at step 530. The DRS/POS 30 may be configured to communicate or store the acceptance in a data source using the software platform.

[0062] The method may further comprise communicating an identification tag 110 (also referred as "Identifier") to the DRS/POS 30. For example, the Identifier 110 may be embodied as a sticker to be affixed in the proximity of each point of sale, the sticker comprising a unique code such as a QR Code or equivalent.

[0063] In other embodiments, the Identifier 110 may also be issued in an electronic format in a format adapted to be sent electronically to a computer device of the DRS/POS 30. In such embodiments, the Identifier 110 is adapted to be displayed by a device comprising a display unit, such as a tablet, a POS device or any similar device. In another example, the Identifier 110 may be displayed on the computer device of the DRS 30, so that, for example, the customer, who may want to participate in the campaign, may scan the Identifier 110 with the client device 130, when at the DRS/POS 30. Understandably, any other means for providing a unique Identifier could be used without departing from the present invention. An example of an Identifier 110 is shown in Figure 6. For example, the Identifier 110 may be activated upon receipt by the DRS 30.

[0064] In some embodiments, the DRS 30 may be part of a group of establishments, such as a franchise network. In such embodiments, a prior general campaign approval may have been obtained. As such, the Identifier 110 may be sent in combination with the designation Notice (see for instance step 520).

[0065] It should be noted that same Identifier 110 may be used by the same DRS/POS 30 for several campaigns (consequent and/or non-consequent). For example, the DRS/POS 30 may accept a new campaign and continue using the Identifier 110 that was issued for a previous campaign.

[0066] The system is configured to adapt to any type of POS system. Typically, the choice of a type of POS depends on the type of Campaign's Objects and could be as diverse as cash registers, restaurant tables, check-in desks at airports, railway or bus stations, as well as stations for other means of transportation, as well as event venues, such as for sport and cultural events, e.g. museums, stadiums, theaters and movie theaters.

[0067] In some embodiments, authentication of the client device 130 may also be performed by sending a notification to the DRS 30. The notification shall comprise a unique network link adapted to verify authentication of the client device. In a preferred embodiment, the notification is sent by email and the unique network link is a Uniform Resource Locator (also known as "URL") used to verify the applicant's e- mail address. In some embodiments, if the said authentication is successful, the DRS 30 may be configured to receive an electronic encoded Identifying Tag by the system. The Identifying Tag may then be printed or used in its electronic version.

[0068] The CASP 40 may be configured to communicate at least one message to at least one RPC 20 of the Campaign (see for instance 550). The sending of the message is typically triggered by the creation of the Campaign 510. In a preferred embodiment, the at least one message may be sent using any electronic communication mean to the client device 130 of the RPC. The electronic communication mean typically use a communication network 25 such as, but not limited to, social network applications, e- mails, newsletters and/or otherwise. Such messages may comprise instructions for the RPC 20 to install an application 120, such as a mobile application (also known as "Mobile App") on the RPC client device 130.

[0069] In a typical embodiment, the Mobile App is made available for download to the client device 130 from on-line app stores such as Apple AppStore™ or Google Play Store™. Understandably, any other installation procedure may be used without departing from the principles of the present invention.

[0070] As shown in Figure 3, at step 550, CASP 40 may also issue or generate at least one computer-generated Mobile Certificate Code 140 ("MCC"). In a preferred embodiment, the MCC may be specifically generated for each client device 130 and/or the MCC may be personalized for each RPC 20. For example, the Mobile App may be configured to receive the MCC and store the MCC on the client device 130.

[0071] In some embodiments, the Mobile App 120 may be a mirror application of the Platform. For example, the Mobile App may comprise, among others, sticker identifying features, and portfolio features to receive and save MCC. In a preferred embodiment, the Mobile App may be configured to store and/or save the MCC on the Mobile App for later use.

[0072] The method may further comprise the CASP 40 sending the MCC to one or more client device 130. The client device 130 may be configured to receive and store on the said client device 130 or in any other data source the MCC 560. For example, the Mobile App may be configured to store the said MCC on the client device 130 or in any other data source.

[0073] Now referring to Figure 4, a workflow diagram presenting the steps of an embodiment of Phase II of the method in accordance with the principles of the present invention is shown. Phase II generally provides for a certification of the RPC 20 at the DRS/POS 30.

[0074] In at least one embodiment, the customer may identify himself/herself to the DRS or POS 30. Alternatively, the Mobile App may be configured to identify the DRS or POS 30 in the vicinity of the location of RPC 20. For example, the Mobile App may display a notice on the client device 130 when the DRS or POS 30 is within a predetermined range. The RPC 20 intending to participate in the Campaign ("Customer") may then scan the Identifier of the DRS or POS 30 using the client device 20 (steps 570 and 575 at Figure 4). In such an embodiment, the client device 130 must comprise a mean for scanning or recognizing the Identifier, such as but not limited to an integrated camera or scanner. The Mobile App may be configured to capture and identify the image of the Identifier of the DRS or POS 30.

[0075] The method may further comprise determining whether the MCC may be used for a particular POS/DRS 30 (see 580). For example, after having scanned POS's Identifier using the Mobile App, the Customer may perform an on-site verification as to whether the required circumstances for certification and eventual redemption are available.

[0076] If the DRS/POS 30 verifies or accepts the MCC, the client device 30 may be configured to send a request to the CAS for authentication/certification of MCC 590.

[0077] In at least one embodiment, the CASP 40 may further be configured to verify whether the MCC may require a payment by Customer 600. For example, if no payment may be required, CASP 40 may proceed directly to step 610. Alternatively, if payment may be required, CASP may send a request to a Payment Processor for payment processing. In some embodiments, the Payment Processor may be implemented by a financial partner. In such an embodiment, the payment processing may be done using electronic payment using credit card and/or through mobile applications such as, for example, ApplePay™, Google Wallet™ or PayPal™. Still, in such an embodiment, the CASP 40 shall be configured to wait for affirmative confirmation from Payment Processor prior to proceeding to the next step. Understandably, any other known means for accepting or processing a payment may be used without departing from the principles of the present invention. At step 610 of the method, the CASP 40 may be configured to verify whether the authentication/certification is available. As such, CAS is configured to return a failure message refusing authentication of electronic certificate or a success message accepting the authentication.

[0078] In at least one embodiment, CAS may also be configured to use geolocalization data of the client device 130 or of the POS/DRS 30. In some embodiments, the geolocalization data may supplement confirmation of primary identification made by the Identifier. For example, geotagging may be performed using Global Positioning System (GPS) features or, in a more complex environment, such as shopping centers, through the use of relay such as, for example, Bluetooth™ tags of the IBeacon™ types.

[0079] In at least one embodiment, the CAS may be configured to identify that any failure event, such as but not limited to the MCC having already been authenticated, that the goods and/or services being the object of the Campaign are not available or that the Campaign has lapsed. If the CAS identifies such a failure event/situation, the CAS may communicate a failure message to the client device 130 refusing authentication of the electronic certificate.

[0080] If conditions for certification are met, the CAS is configured to communicate a success message and/or a confirmation message to the customer device 130. The confirmation message typically comprises a unique identifier such as a Validation Number 150. The Mobile App may be configured to display the confirmation on the client device 130 or to display a Certification Display (MCD) 160. The Certification Display (MCD) is typically embodied as to display a unique and unfalsifiable visual confirmation. An example of the MCD is shown at Figure 8. [0081] In at least one embodiment, the MCD may be made visually available to the Customer on the client device 130. For example, the MCD may also be made available on the POS's representative's computer device. For example, the MCD may confirm that the conditions for granting of the Campaign's Object to the RPC are met.

[0082] In at least one embodiment, the CASP 40 may be configured to collect and/or store data. In such embodiment, the collected data may comprise location of use of MCC, time of use of MCC and/or other information related to use of MCC by the customer's device 130. For example, the data collected by the CASP 40 may be compiled to analyze the Campaign's results.

[0083] Now referring to Figure 7, the MCD 160 of a preferred embodiment is shown. The MCD 160 may be a stack of layers. Such stack of layers may allow gathering on one single display information regarding the specific transaction. For example, the information may comprise a validation code, a visual sign confirming approval from CASP, visual means rendering the display difficult to reproduce, and/or a means ensuring that the visual is in real time. Having such information in one single display aims at substantially reducing the possibility of counterfeiting or using false coupons. The MCD 160 may comprise any number of layers. Still referring to Figure 7, an exemplary stack 160 of four layers 170, 180, 190, and 200 is shown.

[0084] In such an embodiment, one layer (for example, a first layer 170 at Figure 7) may be provided to display the information to be authenticated. For example, the first layer 170 may have information on validity of the coupon or ticket, its face value, its expiration date and/or legal terms when necessary, etc.

[0085] Another layer (for example, a second layer 180 at Figure 7) may be provided to comprise a stamp, repeated throughout the display. For example, the stamp may move. The stamp may comprise information such as the Validation Number 150, the store number and/or the POS number of the retailer, and/or the name of the retailer, etc.

[0086] Another layer (for example, a third layer 190 at Figure 7) may be provided to comprise Guilloche designs, colorful and/or animated (for example, rotation, translation), and/or any other graphic patterns, which, for example, may be difficult to reproduce. US Patent no 8681387 B2, issued to Maltz and al., discloses examples of methods for creating Guilloche designs. [0087] One of the layers of the stack of layers 160 may comprise at least one image, such as a trademark and/or logo of the Issuer 10 to facilitate the identification of the MCD.

[0088] Another layer (for example, a fourth layer 200 at Figure 7) may be provided to allow the viewer to see a real-time image on the display of the client device 130, in real time. Such image may be captured, for example by a front and/or back camera of the client device 130.

[0089] It should be understood that the layers of the stack of the layers may be displayed in any sequence.

[0090] Figures 8, 9 and 10 show several examples of MCD. Figure 8 shows an example of MCD when applied for authentication of a coupon in a coupon Campaign. Figure 9 shows an example of MCD of a boarding pass for transportation. Figure 10 shows an example of MCD of admission tickets to an entertainment event.

[0091] Referring now back to Figure 5, a workflow diagram of steps of an exemplary embodiment of Phase III of the method is shown. In at least one embodiment, CASP

40 is configured to receive and store information regarding the Campaign's Object granted by the POS/DRS 630 in order to process the received information received.

For example, CASP 40 may be configured to send instructions to the Payment processor 640 for payment to the DRS/POS 30 of outstanding monetary rebates. For example, the CASP 40 may be configured to request the Payment Processor to process payment at predetermined time intervals, such as at the end of the day or when a specific amount is reached.

[0092] The method may further comprise the CASP 40 generating at least one accounting report for the Campaign activities for at least one (or each) DRS/POS 30. For example, the CASP 40 may be configured to generate accounting reports at regular time intervals, such as, for example, at the end of the day.

[0093] In a preferred embodiment, the CASP 40 is configured to aggregate the Campaign results and/or analytics (step 660). For example, CASP 40 may transmit such information to the Issuer 10.

[0094] In at least one embodiment, the system and the method may operate without communication between the client device 130 and the CASP 40 when identifying the DRS/POS 30 and/or when ensuring that the MCC is usable. For this purpose, the client device 130 shall be configured to run a Local Certification Client (LCC). In such an embodiment, the LCC is configured to maintain an up-to-date list of the MCC saved at the client device 130.

[0095] Still in such an embodiment, the LCC is configured to request the CASP 40 an updated list of MCC. Upon receiving the said request from the LCC, the CASP 40 checks whether the list comprises at least one valid MCC and generate a list of valid MCC. The CASP 40 is configured to communicate the generated list to the LCC. In a typical embodiment, the list comprises valid MCC and valid DRS/POS Identifiers for each MCC, store as a bundle. In a preferred embodiment, the bundle may be timestamped. Once the timestamped bundle is received by the LCC, the timestamp bundle is stored as a Last Known Bundle (LKB).

[0096] Upon identification, when the RPC 30 uses the client device to certificate the coupon (also referred "Certification time"), the LCC may read the LKB to find a matching DRS/POS identifier in the MCC list. If the sum of the LKB timestamp and the predetermined offline duration (AOD) is higher than the timestamp of the Certification time and of a predetermined offline duration (AOD), the MCC is considered valid and may the coupon may be used at the DRS/POS 30 at that particular time. For example, a constant of the allowed offline duration may be defined by the DRS/POS system or within the client device.

[0097] The LCC may be configured to update the entry for the MCC in the LKB by adding the use time, the DRS/POS identifier and/or other relevant information.

[0098] In at least one embodiment, the LCC may be configured to add the updated bundle to any further requests to the CASP 40 in order to get a new and updated LKB. Such updated LKB would increase the duration of use of the coupon in an offline mode. To ensure both parties get the latest versions of the bundle, the CASP 40 may not deliver any new LKB if the updated bundle was not transmitted to CASP 40 with a later (further) request sent to the CASP 40. CASP 40 may then store updates for MCC entries found in the bundle.

[0099] Referring now to Figure 11, an exemplary embodiment of a method to update or refresh a list of MCC while being connected to the CASP or being in an online mode 700 is shown. The client device 130 and CASP 40 may synchronize one ore more MCC list while the communication between the client device 130 and the CASP 40 is available (e.g. when both client device 130 and the CASP 40 are online).

[00100] At step 710, the list of MCC 140 may to be synchronized or refresh is saved on the client device 130. At step 720, a request may be sent to the CASP 40. The request typically comprises instructions to verify whether the list of MCC is up- to-date or to verify time at which the list of MCC was updated.

[00101] The method further comprises verifying if the bundle was emitted for that the client device 130 (see 730) and if a matching existing bundle (EB) was sent by the LCC for that bundle (see 740). Upon completing 730 and 740, the method further comprises the CASP 40 verifying whether each item of the list of MCC is up- to-date 750 or at which time each item was updated. For example, the CASP 40 may verify whether the MCC may be used (e.g. verify the campaign dates) and/or verify whether the quantities of goods/services available.

[00102] While verifying each item of the list of MCC, the method further comprises the CASP 40 marking each verified MCC as valid 770.

[00103] At step 760, the CASP 40 may verify if the last item of the list of MCC has been processed. Having verified all items of the list of MCC, the CASP 40 may generate, at step 780, a bundle comprising the list of the MCC verified as valid along with an associated list of DRS/POS Identifiers where the MCC are valid. At step 790, the bundle may be sent back to the client device 130 along with the bundle (validity) timestamp. At step 795, the LCC on the client device 130 may save the bundle as LKB within a storage means.

[00104] Referring now to Figure 12, shown an embodiment of a method to authentication an electronic certificate in the client device 130 while being disconnected from the network 800 (Phase B). At the Phase B of the method, the RPC may use the coupon at DRS/POS location while the client device 130 of the RPC 20 or the DRS/POS 30, or both are offline. For example, this exemplary portion 800 of the method for authenticating electronic certificates in the client device 130 may be performed when the client device 130, CASP 40, or both is/are offline. In some embodiment, if the client device 130 or the DRS/POS 30, or both do not have access to the communication network 25 (e.g. there is no WAN, LAN or Internet access available), such method is usable as the communication may not be possible between the client device 130 and the CASP 40 to identify the DRS/POS 30 or to ensure that the MCC is usable.

[00105] At step 820, the customer identifies a DRS and/or POS. At step 830, the customer may scan or read the Identifier. The Identifier is then use by the client device. In a preferred embodiment, the client device comprise a scanning mean, such as a camera, to read the Identifier. At step 840, the LCC may find a matching coupon for this DRS/POS identifier in LKB. If the LCC finds the matching coupon for this DRS/POS Identifier in LKB, the method then compares, at step 850, a timestamp of the current time (also known as "Certification time") with the sum of the timestamp of the LKB and a constant of the allowed offline duration (AOD). If the Certification time timestamp is less than a sum of the timestamp of the LKB and of a constant of the allowed offline duration, the MCC may be considered valid at step 860.

[00106] At step 870, LCC may update the bundle with the relevant information, such as, for example, DRS/POS Identifier or MCC as having been used at such time and/or date.

[00107] It should be noted that DRS/POS as used herein may mean DRS, POS, or both.

[00108] Broadly, it should be understood that the method and system described herein are adapted to allow communication between the client device 130 and the CASP 40 without requiring any communication with a device of the POS/DRS. Indeed, only the authentication of the MCC and the participation of the customer in the Campaign allow the verification of the coupon, rebate, or other ticket. In particular, no communication between DRS/POS 30 and CASP 40 may be necessary for authenticating electronic certificates provided by the issuer 10.

[00109] It should be noted that in some embodiments, the Issuer device may also act as the client device 130 to take advantage of the campaign.

[00110] While illustrative and presently preferred embodiment(s) of the invention have been described in detail hereinabove, it is to be understood that the scope of the claims should not be limited by the preferred embodiments set forth in the examples, but should be given the broadest interpretation consistent with the description as a whole.