-
Notifications
You must be signed in to change notification settings - Fork 0
/
camp2023-57130-eng-Online_selling_without_internet_connection_opus.vtt
209 lines (139 loc) · 5.41 KB
/
camp2023-57130-eng-Online_selling_without_internet_connection_opus.vtt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
WEBVTT
00:00:00.000 --> 00:00:10.000
[MUSIC]
00:00:10.000 --> 00:00:32.520
So now we have Sebastian, welcome.
00:00:32.520 --> 00:00:36.480
Sebastian is telling us about online selling without internet connection.
00:00:36.480 --> 00:00:38.680
>> Thank you.
00:00:38.680 --> 00:00:40.680
Hello, how many of you?
00:00:40.680 --> 00:00:43.000
>> [INAUDIBLE]
00:00:43.000 --> 00:00:44.280
>> Now, yes.
00:00:44.280 --> 00:00:48.200
How many of you use payment system, additional payment system?
00:00:48.200 --> 00:00:48.720
Raise your hand.
00:00:48.720 --> 00:00:52.800
How many of you like free software?
00:00:52.800 --> 00:00:57.360
How many of you know the software that the payment system is running?
00:00:57.360 --> 00:00:58.240
Okay, nobody.
00:00:58.240 --> 00:01:04.560
So how many of you know Nutaler already?
00:01:04.560 --> 00:01:06.360
Okay, couple of hands.
00:01:06.360 --> 00:01:13.240
So this is not about talking about Nutaler, you must already know it.
00:01:13.240 --> 00:01:16.360
But this is an update of what we are working on.
00:01:16.360 --> 00:01:20.280
So we are working on local currency lastly.
00:01:20.280 --> 00:01:23.600
This is how it works.
00:01:23.600 --> 00:01:30.200
So from the wallet, you first follow the one who doesn't have a use yet, Nutaler.
00:01:30.200 --> 00:01:34.720
You first withdraw the coins, you spend it, you get the ticket from the merchant,
00:01:34.720 --> 00:01:39.160
you spend it in the merchant with coins that are like the signature.
00:01:39.160 --> 00:01:44.840
So you cannot link the withdrawal from the payment, so no one can trace you.
00:01:44.840 --> 00:01:47.240
What are you buying?
00:01:47.240 --> 00:01:49.040
And then the merchant make the deposit and
00:01:49.040 --> 00:01:53.080
get the cash back from the merchant bank account, right?
00:01:53.080 --> 00:01:55.320
So this is, I already know.
00:01:55.320 --> 00:01:59.960
But we were thinking about if a merchant is going to be,
00:01:59.960 --> 00:02:04.000
like for example here, selling stuff and doesn't have internet connection.
00:02:04.000 --> 00:02:09.640
How do you trust that the wallet did the payment if you cannot check online?
00:02:09.640 --> 00:02:15.800
So we found a solution, basically without too much saying.
00:02:15.800 --> 00:02:19.280
We are using a TOTP,
00:02:19.280 --> 00:02:25.320
code generator that the merchant has with a shared key with a merchant device.
00:02:25.320 --> 00:02:29.800
So in the point of sales, you can check that the wallet's
00:02:29.800 --> 00:02:34.880
transaction has codes that are valid for the purchase.
00:02:34.880 --> 00:02:41.520
So when the wallet pays, you get information for the merchant back office, right?
00:02:41.520 --> 00:02:46.360
And it has some verification code that can be validated with the merchant point of
00:02:46.360 --> 00:02:47.800
sale.
00:02:47.800 --> 00:02:53.800
So as you can see here, the point of sales talks with the buyer,
00:02:53.800 --> 00:02:59.840
set the amounts, and it creates a contract that is going to be paid and
00:02:59.840 --> 00:03:05.880
generates the key that will generate the code that is going to be transferred to
00:03:05.880 --> 00:03:07.120
the point of sale.
00:03:07.120 --> 00:03:12.440
If the point of sales validate that the code is the correct one,
00:03:12.440 --> 00:03:15.280
it checks that the purchase is real.
00:03:15.280 --> 00:03:19.520
So you can do that without the point of sale being online with the merchant.
00:03:21.920 --> 00:03:28.320
So this is an example creating a QR code.
00:03:28.320 --> 00:03:33.080
The merchant can create a QR code that is going to be put in the point of sales.
00:03:33.080 --> 00:03:39.200
You set the description, the summary, and a fixed price.
00:03:39.200 --> 00:03:43.200
And then this is what can be printed in the point of sales.
00:03:43.200 --> 00:03:45.400
So you can scan it when you roll it and pay it.
00:03:45.400 --> 00:03:46.720
>> [LAUGH]
00:03:46.720 --> 00:03:48.360
>> When you pay it with the wallet,
00:03:48.360 --> 00:03:53.480
you're going to see the confirmation of the transaction with these codes.
00:03:53.480 --> 00:03:58.000
And these codes is what you can tell to the merchant to say, I made a purchase.
00:03:58.000 --> 00:04:02.400
This is my code, okay, and the merchant can verify that because there is
00:04:02.400 --> 00:04:05.520
an OTP validator in the merchant device.
00:04:05.520 --> 00:04:12.320
So there is no demo because there's too much thing happening right now.
00:04:12.320 --> 00:04:17.000
And we are going to be implementing this feature in the batch.
00:04:17.000 --> 00:04:20.880
And I think the SoCo village is running a merchant and
00:04:20.880 --> 00:04:25.280
title exchange and we are trying to implement that so it can be tested.
00:04:25.280 --> 00:04:29.800
We also will be in the house of tea.
00:04:29.800 --> 00:04:35.000
Every day at 3 PM we are going to be there just for talking about Tyler.
00:04:35.000 --> 00:04:39.240
And also maybe a workshop to set up local currencies.
00:04:39.240 --> 00:04:42.960
That's it.
00:04:42.960 --> 00:04:46.360
There is a lot of help wanted, testing, translations,
00:04:46.360 --> 00:04:47.640
also testing the deployments.
00:04:47.640 --> 00:04:51.520
That's it.
00:04:51.520 --> 00:04:52.020
Thank you.
00:04:52.020 --> 00:04:54.400
>> [APPLAUSE]
00:04:54.400 --> 00:04:59.480
[MUSIC]