AU2021103671A4

AU2021103671A4 - An e-commerce system for multi-party e-commerce transaction payment processing

Info

Publication number: AU2021103671A4
Application number: AU2021103671A
Authority: AU
Inventors: Matt Holme
Original assignee: Youpay Pty Ltd
Current assignee: Youpay Pty Ltd
Priority date: 2020-06-29
Filing date: 2021-06-28
Publication date: 2021-08-19
Anticipated expiration: 2029-06-28

Abstract

An e-commerce system allows a second customer to pay for e-commerce items checked out by a first customer. Specifically, the present e-commerce system displays a first checkout interface allowing a first customer to checkout a plurality of e-commerce items. The first checkout interface may generate a payment link which is sent to the second customer. The second customer uses the payment link to access a second checkout interface and make payment for the checked-out e-commerce items using a selected payment option. 11 101 100 105-- Status 104 Address 10-/, Second 10 91 - Status 11 01 -- UI Shipping 111''Address First customer 11 Transactions 102 Processor 115,/ Transaction 103 118 116,/ Checkoutr1 117 Controllers I/O Gateweay 10 Memory/ DB eCommerce webserver eCommerce SDK /119 Frontend webserver . 120 121A First Checkout Interface Second Checkout Interface 123 122_ First client device Second client device 124 Figure 1

Description

101 100 105-- Status 104

Address

10-/, Second

10 91 - Status

11 01 -- UI

Shipping 111''Address

First customer

11 Transactions 102

Processor

115,/ Transaction 103 118 116,/ Checkoutr1 117 Controllers I/O Gateweay 10 Memory/ DB eCommerce webserver

eCommerce SDK /119 Frontend webserver . 120

121A First Checkout Interface Second Checkout Interface 123 122_ First client device Second client device 124

Figure 1

An e-commerce system for multi-party e-commerce transaction

payment processing

Field of the Invention

[0001] This invention relates generally to e-commerce systems. More particularly, this invention relates to an e-commerce system for multi-party e-commerce transaction payment processing.

Background of the Invention

[0002] E-commerce platforms handle e-commerce transactions and order fulfilment. E-commerce webservers comprise checkout controllers for adding selected e commerce items to a shopping cart and input of customer data and transaction controllers for processing payment accordingly.

[0003] The transaction controller takes a shipping address and a billing address. The shipping address and a billing address may be the same in certain instances.

[0004] However, problems exist where customers sometimes do not have sufficient credit and use someone else's credit card, such as that of a spouse, or where customers such as minors cannot legally possess credit cards yet obtain an input credit card details of a parent, with or without supervision.

[0005] Furthermore, Internet gifting may expose sensitive information of one party to another.

[0006] As such, the present invention seeks to provide improvements to e-commerce systems, which will overcome or substantially ameliorate at least some of the deficiencies of the prior art, or to at least provide an alternative.

[0007] It is to be understood that, if any prior art information is referred to herein, such reference does not constitute an admission that the information forms part of the common general knowledge in the art, in Australia or any other country.

Summary of the Disclosure

[0008] There is provided herein an e-commerce system which allows a second customer to pay for e-commerce items checked out by a first customer.

[0009] Specifically, the present e-commerce system displays a first checkout interface

allowing a first customer to checkout a plurality of e-commerce items. The first

checkout interface may generate a payment link which is sent to the second customer.

[0010] The second customer uses the payment link to access a second checkout

interface and make payment for the checked-out e-commerce items using a selected

payment option, such as credit card, PaypalTM, AfterPay TM or the like.

[0011] When generating e-commerce transactions, most e-commerce web servers

have a technical limitation of requiring both a shipping address (the address to which

the ordered items are sent in the post) and a billing address (associated with the

payment instrument of the customer) which, as alluded to above, may be the same.

[0012] As such, it is generally not possible technically to generating e-commerce

transactions without a shipping address and a billing address.

[0013]As such, the present system overcomes this technical limitation of these

existing e-commerce webservers by essentially generating two separate e-commerce

transactions wherein a first e-commerce transaction thereof comprises the shipping

address of the first customer and a second e-commerce transaction thereof comprises

the billing address of the second customer.

[0014] As such, conventional e-commerce platforms such as ShopifyTM, WooCommerceTMand the like may be used substantially in the conventional manner.

[0015] In embodiments, a frontend webserver comprising a payment SDK interfacing

the transaction and checkout controllers of the e-commerce may be used to generate

the unique identifier of the first e-commerce transaction, subsequently retrieve the e

commerce items of the first e-commerce transaction using the unique identifier and

update the first e-commerce transaction as being paid when payment against the

second e-commerce transaction has been successfully processed.

[0016] As such, the present e-commerce processing may be integrated with existing

e-commerce webservers to generate e-commerce transactions in substantially the

conventional manner allowing for a wide variety of existing e-commerce webservers

to be used in the conventional manner.

[0017] Embodiments allow for privacy control wherein the first checkout interface may

be used to control the display of the shipping address, first customer details and e

commerce item details on the second checkout interface.

[0018] Other aspects of the invention are also disclosed.

Brief Description of the Drawings

[0019] Notwithstanding any other forms which may fall within the scope of the present

invention, preferred embodiments of the disclosure will now be described, by way of

example only, with reference to the accompanying drawings in which:

[0020] Figure 1 shows an exemplary e-commerce system in accordance with an

embodiment;

[0021] Figure 2 shows exemplary processing by the e-commerce system of Figure 1;

[0022] Figures 3 and 4 show an exemplary first checkout interface displayed by the

system of Figure 1 in accordance with an embodiment; and

[0023] Figures 5 and 6 show an exemplary second checkout interface displayed by

the system of Figure 1 in accordance with an embodiment.

Description of Embodiments

[0024] An exemplary e-commerce system 100 comprises an e-commerce webserver

101. The e-commerce webserver 101 comprises a processor 102 for processing

digital data. A memory device 106 is in operable communication with the processor

102 via a system bus 104. The memory device 106 is configured for storing digital

data including computer program code instructions and associated data 114. The

computer program code instructions may be logically divided into a plurality of

controllers 117.

[0025] As illustrated, the controllers 117 may comprise a checkout controller 116 and

a transaction controller 115. The checkout controller 117 may comprise shopping cart

functionality allowing customers to add e-commerce items to a shopping cart and

checkout functionality allowing users to configure the selected e-commerce items and

input customer data.

[0026]The transaction controller 115 may generate and control e-commerce

transactions including with the aforedescribed shipping address, billing address and

payment details.

[0027]The data 114 may store a plurality of e-commerce transactions 113. The

transactions 113 may comprise a first e-commerce transaction 113 comprising first

customer data 112 including shipping address data 111. The first e-commerce

transaction may further be associated with the unique identifier 110 and have an e

commerce transaction status 109. The transactions 113 may comprise a second e

commerce transaction 113 comprising second customer data 108 including billing

address data 107 and an associated status 105.

[0028] The e-commerce webserver 101 may comprise an 1/O interface 103 for sending

and receiving data across a wide area network. The 1/O interface 103 may be in

operable communication with the payment gateway 118 for processing payments,

such as credit card transactions.

[0029] The e-commerce webserver 101 is in operable communication with a plurality

of client devices which are shown as comprising a first client device 122 and a second

client device 124. Each client device 122, 124 may display a checkout interface, given

as a first checkout interface 121 and second checkout interface 123 respectively.

[0030] The client devices 122, 124 may interface with the e-commerce webserver 101

directly. In alternative embodiments, the client devices 122, 124 may interface the e

commerce webserver 101 via an intermediary frontend webserver 120. The frontend

webserver 120 may comprise an e-commerce SDK configured to control the

transaction controller 115 and checkout controller 116 of the e-commerce webserver

101.

[0031] With reference to figure 2, exemplary processing by the system 100 may

comprise a first transaction phase 125 and a second transaction phase 126.

[0032] The first transaction phase 125 may comprise e-commerce item selection 127

by a first customer using the first client device 122 and the display of the first checkout

interface 121 is illustrated in Figure 3.

[0033] The first checkout interface 121 may display a list 138 of the selected e

commerce items and comprise input fields 139 for obtaining first customer data

including a shipping address input field 140 for obtaining a shipping address of the

first customer.

[0034] The input fields 139 may further comprise a privacy control 141.

[0035] The interface 121 may display a plurality of payment options 142, such as for

credit card payment, PaypalTM, AfterPayTMand the like. One of the payment options

142 may comprise an option for another person to make payment which, when

selected, causes the transaction controller 115 to generate the first e-commerce

transaction at step 129 in substantially the conventional manner and store the first e

commerce transaction 113 in the database 106 at step 130.

[0036] The transaction controller 115 or e-commerce SDK 119 may generate a unique

identifier for the first e-commerce transaction at step 131 which may be displayed in

an e-commerce transaction confirmation panel 143 of the interface 121.

[0037] The unique identifier may be displayed as a payment link 144 which may be

copied and pasted to an email client or the like. In embodiments, the interface 121

may take contact information, such as an email address, mobile phone number or the

like and send the unique identifier accordingly, including via push notification.

[0038] The second transaction phase 126 may comprise the transaction controller 115

or the e-commerce SDK 119 receiving the unique identifier of the first e-commerce

transaction at step 132.

[0039] For example, the first customer may have emailed the payment link 144 to a

second customer. Accessing on the payment link 144 on the second client device 124

may cause the second client device 124 to launch a web browser application or

alternatively launch and installed software application associated with the system

100.

[0040] The second client device 124 send the unique identifier to the e-commerce

webserver 101 or the frontend webserver 120 wherein the respective transaction

controller 115 or e-commerce SDK 119 thereof identifies the first e-commerce transaction within the database 106 and retrieves the associated e-commerce items thereof at step 133.

[0041]At step 134, the checkout controller 116 may display the second checkout

interface 123 as shown in Figure 5.

[0042] The second checkout interface 123 may display the e-commerce items 138

selected by the first customer. Furthermore, the second checkout interface 123 may

display customer data of the first customer, such as name and address data.

However, the first customer may use the aforedescribed privacy control 141 to control

the display of the shipping address of the first customer, customer data of the first

customer and/or the e-commerce items in the second checkout interface 123.

[0043] The second checkout interface 123 similarly comprises input field 139 for

obtaining second customer data, including a billing address input field 145.

[0044] The interface 123 further comprises one or more payment options 142 such as

the aforedescribed credit card payment, PaypalTM, AfterPayTM and the like options.

[0045] Selecting one of the payment options 142, such as the credit card payment

option, may allow the input of credit card details and the transaction controller 115

processing payment accordingly by communicating with the payment gateway 118.

[0046] Upon receiving confirmation of successful payment processing from the

payment gateway 118, the transaction controller 115 may update the status 109 of

the first e-commerce transaction as being paid thereby triggering order fulfilment

processing by the e-commerce webserver 101 in the normal manner.

[0047] It should be noted that whereas the methodologies described herein may be

used for checkout of items on e-commerce platforms, the present methodologies may

be used for payment of other Internet transactions, such as, for example, ride sharing

platforms wherein a rider sends a payment link to another party for payment of a ride.

[0048] The foregoing description, for purposes of explanation, used specific

nomenclature to provide a thorough understanding of the invention. However, it will

be apparent to one skilled in the art that specific details are not required in order to

practise the invention. Thus, the foregoing descriptions of specific embodiments of

the invention are presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed as obviously many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, thereby enabling others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the following claims and their equivalents define the scope of the invention.

[0049] The term "approximately" or similar as used herein should be construed as

being within 10% of the value stated unless otherwise indicated.

Claims

Claims 1. An e-commerce system comprising:

an e-commerce webserver comprising:

a checkout controller, and

a transaction controller

wherein the system is configured for implementing:

a first transaction phase wherein:

the checkout controller:

receives a selection of one or more e-commerce items via

an interface, and

displays a first checkout interface, the first checkout

interface comprising input fields for first customer data including

a shipping address;

the transaction controller:

generates a first e-commerce transaction using the one or

more e-commerce items and the first customer data, the first

customer data including the shipping address, and

stores the first e-commerce transaction in a transaction

database;

the system generates a unique identifier for the first e-commerce

transaction

a second transaction phase wherein

the system:

receives, via a web service, the unique identifier,

retrieves the one or more e-commerce items of the first e

commerce transaction from the database using the unique identifier;

the checkout controller:

displays a second checkout interface, the second

checkout interface displaying at least one payment option including payment input fields for second customer data including a billing address, the transaction controller: generates a second e-commerce transaction using second customer data including the billing address; processes a payment via a payment gateway using the second customer data including the billing address; and responsive to successful payment confirmation from the payment gateway, updates the status of the first e-commerce transaction.

2. A system as claimed in claim 1, further comprising a frontend webserver

interfacing the e-commerce webserver wherein the frontend webserver comprises an

e-commerce SDK interfacing the transaction controller and the checkout controller of

the e-commerce webserver.

3. A system as claimed in claim 2, wherein the e-commerce SDK is used to

generate the unique identifier.

4. A system as claimed in claim 2, wherein the e-commerce SDK is used to

retrieve the one or more e-commerce items of the first e-commerce transaction from

the database using the unique identifier.

5. A system as claimed in claim 1, wherein the first checkout interface comprises

a shipping address privacy control input field controlling the display of the shipping

address of the second checkout interface.

6. A system as claimed in claim 1, wherein the first checkout interface comprises

a customer data privacy control input field controlling the display of the customer data

of the first customer of the second checkout interface.

7. A system as claimed in claim 1, wherein the first checkout interface comprises

an e-commerce item privacy control input field controlling the display of the one or

more e-commerce items of the first customer of the second checkout interface.

8. A system as claimed in claim 1, wherein the first checkout interface has

contact information input fields for the sending of the unique identifier accordingly.

9. A system as claimed in claim 1, wherein the unique identifier is displayed as a

payment link in the first checkout interface.

10. A system as claimed in claim 9, wherein access of the payment link causes the

system to display the second checkout interface.

101 100 105 Status 104 Billing 107 Address 2021103671

Second 108 customer Data

109 Status

110 UID

Shipping 111 Address First customer 112 Data

113 Transactions 102

114 Data Processor

115 Transaction 103 118 116 Checkout Payment 117 Controllers I/O Gateweay 106 Memory / DB eCommerce webserver

eCommerce SDK 119

Frontend webserver 120

121 First Checkout Interface Second Checkout Interface 123

122 First client device Second client device 124

Figure 1

125 126 28 Jun 2021

First transaction phase Second transaction phase

127 Item selection

Display first checkout 2021103671

128 interface

Generate first eCommerce 129 transaction

Store first eCommerce 130 transaction in database

Generate first eCommerce 131 transaction UID

Receive first eCommerce 132 transaction UID

Retrieve transaction data from database 133

Display scond checkout interface 134

Generate second 135 eCommerce transaction

Process payment 136

Update first eCommerce 137 transaction status

Figure 2

138 139 2021103671

140

141

142

Figure 3

121

138

143

144

Figure 4

138 139 2021103671

145

142

Figure 5

123

138

146

Figure 6