Skip to content

Commit ae2dd9f

Browse files
JamesMBlighJamesMBligh
authoredFeb 17, 2023
Merge pull request #9 from RedCrewOS/terminology-update
Update terminology to separate the concept of an Offer and a Session
·
v1.0.0
2 parents c35ddaf + bcc4482 commit ae2dd9f

File tree

7 files changed

+83
-71
lines changed

7 files changed

+83
-71
lines changed
 

‎open-qr-standard.md

+28-16
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
**An open standard for the publication of interoperable QR codes for payments and other use cases**
44

5-
**DRAFT**: v0.1.0
5+
**DRAFT**: v1.0.0
66

77
**Authors**: James Bligh, Kareem Al-Bassam, Jack Moggach
88

@@ -33,6 +33,8 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "S
3333
|Code Provider|The system that represents the initiating side of the user journey. This is the system that creates and publishes the QR Code. For a point-of-sale payment this would be the merchant checkout system.|
3434
|Code Consumer|The system that represents the acceptance, or client, side of the user journey. This is the system that scans and processes the QR Code. For a point-of-sale payment this would be the customer’s mobile wallet application.|
3535
|QR Profile|A profile for defining the format of the various actions and meta data that can be transferred using this standard for a specific type of use case or user journey.|
36+
|Offer|Details about an offer that may be claimed by a QR Consumer. Includes information about the profiles and capabilities associated with a specific QR Code.|
37+
|Session|An established connection (a claim on an Offer) between a QR Provider and a QR Consumer.|
3638

3739
## Generic Sequence Diagram
3840

@@ -79,7 +81,7 @@ An example sequence of activity supported by this standard is as follows ([PNG v
7981
| | | | |
8082
| |<------------------------------ | |
8183
| | | |
82-
| Request details of session | | |
84+
| Request details of Offer | | |
8385
|<----------------------------------------------| | |
8486
| | | |
8587
| Consumer capabilities from discovery | | |
@@ -96,15 +98,15 @@ An example sequence of activity supported by this standard is as follows ([PNG v
9698
| (optional: Use of Central Authority) Validate the Consumer certification | |
9799
|---------------------------------------------------------------------------------------------------------->|
98100
| | | |
99-
| Provide details of session | | |
101+
| Provide details of Offer | | |
100102
|---------------------------------------------->| | |
101103
| | | |
102-
| | Validate session type is supported | |
103-
| |----------------------------------- | |
104-
| | | | |
105-
| |<---------------------------------- | |
104+
| | Validate Offer type is supported | |
105+
| |--------------------------------- | |
106+
| | | | |
107+
| |<-------------------------------- | |
106108
| | | |
107-
| "Claim" session and provide details | | |
109+
| "Claim" Session and provide details | | |
108110
|<----------------------------------------------| | |
109111
| | | |
110112
| Callback to indicate journey completion | | |
@@ -118,23 +120,33 @@ The Code Provider will publish a QR Code that MUST conform with the requirements
118120

119121
This QR Code MUST contain a URL in the following format:
120122

121-
`https://<provider base>/<QR ID>`
123+
`https://<provider base>/<Offer ID>`
122124

123125
The Code Provider MUST provide a valid web page at the location specified by `<provider base>` with instructions for a user how the QR Code can be successfully used.
124126

125-
The `<QR ID>` is used to obtain access to a data entity held by the Code Provider referred to in this standard as a session. QR IDs MAY be single or multiple use depending on the use case being supported.
126-
127-
Sessions MUST be single use.
127+
The `<Offer ID>` is used to obtain access to a data entity held by the Code Provider referred to in this standard as an `Offer`. Offer IDs MAY be single or multiple use depending on the use case being supported.
128128

129129
The Code Provider SHOULD superimpose a logo on the QR code to help Customers recognise trusted brands. This logo SHOULD be tested to ensure the logo does not introduce too much error to the QR Code and the QR Code remains readable. In situations where the effect of scanning a QR code is unclear the Code Provider SHOULD provide guidance as to how the QR Code can be successfully used.
130130

131-
## Session Actions
131+
## Offers
132+
133+
An Offer is the information associated with a specific QR Code that represnts the profiles that the QR Code allows access to. A Code Consumer obtains the Offer information for a QR Code and then determines how to proceed based on the information the Offer contains and what there service supports.
134+
135+
Offers MAY be single use or MAY be multi-use.
136+
137+
## Sessions
138+
139+
After obtaining the Offer information a Code Consumer may claim that Offer. This will result in a Session being established between the Code Provider and the Code Consumer with the Code Provider being the owner of the Session.
140+
141+
Sessions MUST be single use.
142+
143+
## Offer and Session Endpoints
132144

133-
The Code Provider MUST support a Session Info endpoint that the Code Consumer can call to obtain information about the session using the QR ID obtained from the QR Code. This endpoint SHOULD be idempotent and should not have side effects on the underlying Session.
145+
The Code Provider MUST support an Offer Info endpoint that the Code Consumer can call to obtain information about the Offer using the Offer ID obtained from the QR Code. This endpoint SHOULD be idempotent and should not have side effects on the underlying Offer.
134146

135-
The Code Provider MUST support a Session Claim endpoint that the Code Consumer can use to claim a session for use using a QR ID. This endpoint MUST provide a unique Session ID that can be used for subsequent interactions.
147+
The Code Provider MUST support an Offer Claim endpoint that the Code Consumer can use to claim a Offer for use using a Offer ID and thus establishing a Session. This endpoint MUST provide a unique Session ID that can be used for subsequent interactions.
136148

137-
The Code Provider MUST support a Session Status endpoint to identify the status of a session using a Session ID.
149+
The Code Provider MUST support a Session Status endpoint to identify the status of a Session using a Session ID.
138150

139151
The Code Provider MUST support the ability to perform a callback to the Code Consumer when the status of the Session changes.
140152

‎profiles/core-profile.md

+25-25
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ Note that this profile should read as an addendum to the [Open QR Standard](../o
77

88
This profile MUST be supported by both Code Providers and Code Consumers.
99

10-
**DRAFT**: v1.0.0
10+
**DRAFT**: v1.1.0
1111

1212
**Authors**: James Bligh, Kareem Al-Bassam, Jack Moggach
1313

@@ -23,8 +23,8 @@ The supported discovery properties are:
2323

2424
| Property | Optionality | Description |
2525
|----------|-------------|-------------|
26-
|sessionInfoUri|REQUIRED|URL of the Session Info endpoint hosted by the Code Provider.|
27-
|sessionClaimUri|REQUIRED|URL of the Session Claim endpoint hosted by the Code Provider.|
26+
|offerInfoUri|REQUIRED|URL of the Offer Info endpoint hosted by the Code Provider.|
27+
|offerClaimUri|REQUIRED|URL of the Offer Claim endpoint hosted by the Code Provider.|
2828
|sessionStatusUri|REQUIRED|URL of the Session Status endpoint hosted by the Code Provider.|
2929
|jwksUri|REQUIRED|URL of the JWKS endpoint for the Code Provider. MUST include appropriate keys to support the algorithms supported.|
3030
|signingAlgorithms|REQUIRED|JSON array containing a list of supported JWS [RFC7515] signing algorithms. Values to be taken from the JWA standard [RFC7518]. Only asymmetric algorithms may be supported.|
@@ -35,9 +35,9 @@ The supported discovery properties are:
3535

3636
## Code Provider Endpoints
3737

38-
### Session Info Endpoint
38+
### Offer Info Endpoint
3939

40-
An API used to obtain information about the session associated with a nominated QR ID.
40+
An API used to obtain information about the Offer associated with a nominated Offer ID.
4141

4242
#### HTTP Method
4343

@@ -47,13 +47,13 @@ GET
4747

4848
| Parameter | Optionality | Description |
4949
|-----------|-------------|-------------|
50-
|qr-id|REQUIRED|The QR ID that information is requested for.|
50+
|offer-id|REQUIRED|The Offer ID that information is requested for.|
5151

5252
#### Error Responses
5353

5454
HTTP Status: 401, Validation of the provided authorisation JWT failed
5555

56-
HTTP Status: 422, The provided QR ID is not known
56+
HTTP Status: 422, The provided Offer ID is not known
5757

5858
#### Successful Response
5959

@@ -66,7 +66,7 @@ Successful response schema [JSONSchema]:
6666
```json
6767
{
6868
"$schema": "http://json-schema.org/draft-07/schema",
69-
"$id": "https://cds-au/qr/core-provider/1/response/session/info",
69+
"$id": "https://cds-au/qr/core-provider/1/response/offer/info",
7070
"type": "object",
7171
"additionalProperties": false,
7272
"required": [
@@ -85,7 +85,7 @@ Successful response schema [JSONSchema]:
8585
"properties": {
8686
"qrId": {
8787
"type": "string",
88-
"description": "The qr-id that the information was requested for"
88+
"description": "The offer-id that the information was requested for"
8989
},
9090
"provider": {
9191
"type": "string",
@@ -107,11 +107,11 @@ Successful response schema [JSONSchema]:
107107
"expiryTime": {
108108
"type": "string",
109109
"format": "date-time",
110-
"description": "The expiry time of the QR code. After this time the qr-id cannot be used to claim a session "
110+
"description": "The expiry time of the QR code. After this time the offer-id cannot be used to claim a session "
111111
},
112112
"profiles": {
113113
"type": "object",
114-
"description": "An object with details for each of the qr profiles supported by this qr-id. Each property of this object uses the urn of the profile and contains properties defined by the qr profile that the urn denotes",
114+
"description": "An object with details for each of the qr profiles supported by this offer-id. Each property of this object uses the urn of the profile and contains properties defined by the qr profile that the urn denotes",
115115
"additionalProperties": false,
116116
"patternProperties": {
117117
"^urn:.*$": {
@@ -131,9 +131,9 @@ Successful response schema [JSONSchema]:
131131
}
132132
```
133133

134-
### Session Claim Endpoint
134+
### Offer Claim Endpoint
135135

136-
An API used to claim a session under a specific QR Profile using a nominated QR ID.
136+
An API used to claim an offer and establish a session under a specific QR Profile using a nominated Offer ID.
137137

138138
#### HTTP Method
139139

@@ -143,7 +143,7 @@ POST
143143

144144
| Parameter | Optionality | Description |
145145
|-----------|-------------|-------------|
146-
|qr-id|REQUIRED|The QR ID that a session is to be claimed for.|
146+
|offer-id|REQUIRED|The Offer ID that an offer is to be claimed for.|
147147

148148
#### Request
149149

@@ -152,7 +152,7 @@ Request schema [JSONSchema]:
152152
```json
153153
{
154154
"$schema": "http://json-schema.org/draft-07/schema",
155-
"$id": "https://cds-au/qr/core-provider/1/request/session/claim",
155+
"$id": "https://cds-au/qr/core-provider/1/request/offer/claim",
156156
"type": "object",
157157
"additionalProperties": false,
158158
"required": [
@@ -182,7 +182,7 @@ Request schema [JSONSchema]:
182182
},
183183
"profiles": {
184184
"type": "object",
185-
"description": "An object with details for each of the qr profiles supported by this qr-id. Each property of this object uses the urn of the profile and contains properties defined by the qr profile that the urn denotes",
185+
"description": "An object with details for each of the qr profiles supported by this offer-id. Each property of this object uses the urn of the profile and contains properties defined by the qr profile that the urn denotes",
186186
"additionalProperties": false,
187187
"patternProperties": {
188188
"^urn:.*$": {
@@ -204,11 +204,11 @@ Request schema [JSONSchema]:
204204

205205
#### Error Responses
206206

207-
HTTP Status: 400, The specified QR Profile is not supported for this QR ID or the data provided was not valid
207+
HTTP Status: 400, The specified QR Profile is not supported for this Offer ID or the data provided was not valid
208208

209209
HTTP Status: 401, Validation of the provided authorisation JWT failed
210210

211-
HTTP Status: 422, The provided QR ID is not known
211+
HTTP Status: 422, The provided Offer ID is not known
212212

213213
#### Successful Response
214214

@@ -221,7 +221,7 @@ Successful response schema [JSONSchema]:
221221
```json
222222
{
223223
"$schema": "http://json-schema.org/draft-07/schema",
224-
"$id": "https://cds-au/qr/core-provider/1/response/session/claim",
224+
"$id": "https://cds-au/qr/core-provider/1/response/offer/claim",
225225
"type": "object",
226226
"additionalProperties": false,
227227
"required": [
@@ -240,15 +240,15 @@ Successful response schema [JSONSchema]:
240240
"properties": {
241241
"sessionId": {
242242
"type": "string",
243-
"description": "The session-id created by claiming the session. This ID represents this claim event and must be unique. Can be used for subsequent calls for status"
243+
"description": "The session-id representing the session created by claiming the offer. This ID represents this claim event and must be unique. Can be used for subsequent calls for status"
244244
},
245245
"provider": {
246246
"type": "string",
247247
"description": "The unique identifier of the code provider. This is defined as the base location where the discovery document can be found, i.e. ‘https://<provider base>’"
248248
},
249249
"profiles": {
250250
"type": "object",
251-
"description": "An object with details for each of the qr profiles supported by this qr-id. Each property of this object uses the urn of the profile and contains properties defined by the qr profile that the urn denotes",
251+
"description": "An object with details for each of the qr profiles supported by this offer-id. Each property of this object uses the urn of the profile and contains properties defined by the qr profile that the urn denotes",
252252
"additionalProperties": false,
253253
"patternProperties": {
254254
"^urn:.*$": {
@@ -270,7 +270,7 @@ Successful response schema [JSONSchema]:
270270

271271
### Session Status Endpoint
272272

273-
An API used to obtain information about a specific session that was previously claimed.
273+
An API used to obtain information about a specific session that was previously established by claiming an Offer.
274274

275275
#### HTTP Method
276276

@@ -280,13 +280,13 @@ GET
280280

281281
| Parameter | Optionality | Description |
282282
|-----------|-------------|-------------|
283-
|session-id|REQUIRED|The Session ID that information is requested for that was previously obtained from a call to the Session Claim endpoint.|
283+
|session-id|REQUIRED|The Session ID that information is requested for that was previously obtained from a call to the Offer Claim endpoint.|
284284

285285
#### Error Responses
286286

287287
HTTP Status: 401, Validation of the provided authorisation JWT failed
288288

289-
HTTP Status: 422, The provided QR ID is not known
289+
HTTP Status: 422, The provided Offer ID is not known
290290

291291
#### Successful Response
292292

@@ -326,7 +326,7 @@ Successful response schema [JSONSchema]:
326326
},
327327
"profiles": {
328328
"type": "object",
329-
"description": "An object with details for each of the qr profiles supported by this qr-id. Each property of this object uses the urn of the profile and contains properties defined by the qr profile that the urn denotes",
329+
"description": "An object with details for each of the qr profiles supported by this offer-id. Each property of this object uses the urn of the profile and contains properties defined by the qr profile that the urn denotes",
330330
"additionalProperties": false,
331331
"patternProperties": {
332332
"^urn:.*$": {

‎profiles/payment-instruments/eftpos.md

+9-9
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ This payment instrument definition relies upon the [Point-of-sale Payment Profil
77

88
Support for this payment instrument is optional.
99

10-
**DRAFT**: v0.0.4
10+
**DRAFT**: v0.0.5
1111

1212
**Authors**: Jack Moggach
1313

@@ -39,9 +39,9 @@ The supported properties are:
3939
| cardSupported | REQUIRED | Boolean flag indicating if the Code Provider supports payment via card details. |
4040
| tokenSupported | REQUIRED | Boolean flag indicating if the Code Provider supports payment via an Eftpos card formtoken. |
4141

42-
#### Session Info Endpoint
42+
#### Offer Info Endpoint
4343

44-
The following schema defines the content to be returned by the Code Provider in a request to the session info endpoint. This information will be included in the **urn:cds-au:qr:pos-merchant:1** 'profile' property within the 'instrumentTypes' section.
44+
The following schema defines the content to be returned by the Code Provider in a request to the offer info endpoint. This information will be included in the **urn:cds-au:qr:pos-merchant:1** 'profile' property within the 'instrumentTypes' section.
4545

4646
This schema will be returned with an object with the field name of:
4747

@@ -52,7 +52,7 @@ Response Schema [json-schema]:
5252
```json
5353
{
5454
"$schema": "http://json-schema.org/draft-07/schema",
55-
"$id": "https://cds-au/qr/pos-instrument/eftpos/1/response/session/info",
55+
"$id": "https://cds-au/qr/pos-instrument/eftpos/1/response/offer/info",
5656
"type": "object",
5757
"additionalProperties": false,
5858
"required": [
@@ -61,15 +61,15 @@ Response Schema [json-schema]:
6161
"properties": {
6262
"3dsEnabled": {
6363
"type": "boolean",
64-
"description": "Is 3DS enabled for the given session? This value does not indicate whether or not a 3DS challenge will be triggered - only that it may be triggered."
64+
"description": "Is 3DS enabled for the given offer? This value does not indicate whether or not a 3DS challenge will be triggered - only that it may be triggered."
6565
}
6666
}
6767
}
6868
```
6969

70-
#### Session Claim Endpoint
70+
#### Offer Claim Endpoint
7171

72-
The following schema defines the content to be returned by the Code Provider in a request to the session claim endpoint. This information will be included in the **urn:cds-au:qr:pos-merchant:1** ‘profile’ property within the ‘instrumentTypes’ section.
72+
The following schema defines the content to be returned by the Code Provider in a request to the offer claim endpoint. This information will be included in the **urn:cds-au:qr:pos-merchant:1** ‘profile’ property within the ‘instrumentTypes’ section.
7373

7474
This schema will be returned with an object with the field name of:
7575

@@ -86,7 +86,7 @@ Request Schema [json-schema]:
8686
```json
8787
{
8888
"$schema": "http://json-schema.org/draft-07/schema",
89-
"$id": "https://cds-au/qr/pos-instrument/eftpos/1/request/session/claim",
89+
"$id": "https://cds-au/qr/pos-instrument/eftpos/1/request/offer/claim",
9090
"type": "object",
9191
"additionalProperties": false,
9292
"required": [],
@@ -100,7 +100,7 @@ Response Schema [json-schema]:
100100
```json
101101
{
102102
"$schema": "http://json-schema.org/draft-07/schema",
103-
"$id": "https://cds-au/qr/pos-instrument/eftpos/1/response/session/claim",
103+
"$id": "https://cds-au/qr/pos-instrument/eftpos/1/response/offer/claim",
104104
"type": "object",
105105
"additionalProperties": false,
106106
"required": [

‎profiles/payment-profile.md

+13-13
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ This profile relies upon, and extends the [Core QR Profile definition](./core-pr
99

1010
This profile is optional.
1111

12-
**DRAFT**: v1.0.0
12+
**DRAFT**: v1.1.0
1313

1414
**Authors**: James Bligh, Kareem Al-Bassam, Jack Moggach
1515

@@ -39,16 +39,16 @@ The supported discovery properties are:
3939

4040
## Code Provider Endpoints
4141

42-
### Session Info Endpoint
42+
### Offer Info Endpoint
4343

44-
The following schema defines the content to be returned by the Code Provider in a request to the session info endpoint under the ‘profiles’ property. This schema will be returned with an object with the field name of the *Code Provider Profile URN*.
44+
The following schema defines the content to be returned by the Code Provider in a request to the offer info endpoint under the ‘profiles’ property. This schema will be returned with an object with the field name of the *Code Provider Profile URN*.
4545

4646
Profile specific response schema [JSONSchema]:
4747

4848
```json
4949
{
5050
"$schema": "http://json-schema.org/draft-07/schema",
51-
"$id": "https://cds-au/qr/pos-merchant/1/response/session/info",
51+
"$id": "https://cds-au/qr/pos-merchant/1/response/offer/info",
5252
"type": "object",
5353
"additionalProperties": true,
5454
"required": [
@@ -78,11 +78,11 @@ Profile specific response schema [JSONSchema]:
7878
},
7979
"merchantReference": {
8080
"type": "string",
81-
"description": "Optional reference identifier which represents the QR session in a merchant's internal systems."
81+
"description": "Optional reference identifier which represents the offer in a merchant's internal systems."
8282
},
8383
"synchronous": {
8484
"type": "boolean",
85-
"description": "Flag indicating that a payment with this QR code will be synchronous and a final status will be provided when the session is claimed. Assumed to be false if absent"
85+
"description": "Flag indicating that a payment with this QR code will be synchronous and a final status will be provided when the offer is claimed. Assumed to be false if absent"
8686
},
8787
"instrumentTypes": {
8888
"type": "object",
@@ -93,9 +93,9 @@ Profile specific response schema [JSONSchema]:
9393
}
9494
```
9595

96-
### Session Claim Endpoint
96+
### Offer Claim Endpoint
9797

98-
The following schemas define the content to be included in the request and response payloads for the session claim endpoint under the ‘profiles’ property.
98+
The following schemas define the content to be included in the request and response payloads for the offer claim endpoint under the ‘profiles’ property.
9999

100100
The following schema will be included in the request object with an object with the field name of the *Code Consumer Profile URN*.
101101

@@ -104,7 +104,7 @@ Profile specific request schema [JSONSchema]:
104104
```json
105105
{
106106
"$schema": "http://json-schema.org/draft-07/schema",
107-
"$id": "https://cds-au/qr/pos-wallet/1/request/session/claim",
107+
"$id": "https://cds-au/qr/pos-wallet/1/request/offer/claim",
108108
"type": "object",
109109
"additionalProperties": false,
110110
"required": [
@@ -126,7 +126,7 @@ Profile specific request schema [JSONSchema]:
126126
"properties": {
127127
"type": {
128128
"type": "string",
129-
"description": "The type of the instrument to be used for the payment. Additional fields such as tokens or identifiers will be included as defined for the specific instrument type. The instrument type must be one of the types indicated as being supported in the provider discovery document and in the response to a call to session info"
129+
"description": "The type of the instrument to be used for the payment. Additional fields such as tokens or identifiers will be included as defined for the specific instrument type. The instrument type must be one of the types indicated as being supported in the provider discovery document and in the response to a call to offer info"
130130
}
131131
}
132132
}
@@ -141,7 +141,7 @@ Profile specific response schema [JSONSchema]:
141141
```json
142142
{
143143
"$schema": "http://json-schema.org/draft-07/schema",
144-
"$id": "https://cds-au/qr/pos-merchant/1/response/session/claim",
144+
"$id": "https://cds-au/qr/pos-merchant/1/response/offer/claim",
145145
"type": "object",
146146
"additionalProperties": true,
147147
"required": [
@@ -322,7 +322,7 @@ Profile specific response schema [JSONSchema]:
322322

323323
## Code Provider Callback
324324

325-
Code Providers which support the Point of Sale Payment MUST be able to callback to a nominated Code Consumer endpoint when information about a claimed Session changes.
325+
Code Providers which support the Point of Sale Payment MUST be able to callback to a nominated Code Consumer endpoint when information about a Session changes.
326326

327327
Code Consumers can optionally include a ‘callbackUri’ within their discovery document. If this value is set the Code Provider MUST send callback requests. The ‘callbackUri’ can be found in the Code Consumer profile with the *Code Provider Profile URN*.
328328

@@ -346,7 +346,7 @@ The supported discovery properties are:
346346
|----------|-------------|-------------|
347347
|loyaltyPrograms|OPTIONAL|Array of strings indicating the loyalty programs supported for payments. The values in the array are string indicators nominated by the loyalty program organisation.|
348348
|instrumentTypes|OPTIONAL|Map indicating the types of payment instruments supported by the code provider. The keys in the map are string indicators nominated by the organisation that manages the instrument type. Keys follow a URN format and support versions. Metadata about the instrument type may be included in the mapped value object.|
349-
|callbackUri|OPTIONAL|A URL where the wallet can receive status callbacks. If supplied the merchant should send a POST request to this URL using the ‘Session Status’ schema whenever information about a session is changed.|
349+
|callbackUri|OPTIONAL|A URL where the wallet can receive status callbacks. If supplied the merchant should send a POST request to this URL using the ‘Session Status’ schema whenever information about a Session is changed.|
350350

351351
## Code Consumer Endpoints
352352

‎resources/ascii-sequence.txt

+4-4
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Provider->Consumer:Capabilities provided
1414
Consumer->Consumer:Ensure capabilities match
1515
Consumer->Consumer:Extract security configuration
1616

17-
Consumer->Provider:Request details of session
17+
Consumer->Provider:Request details of Offer
1818

1919
Provider->Consumer:Consumer capabilities from discovery
2020

@@ -24,10 +24,10 @@ Provider->Provider:Validate credentials based
2424

2525
Provider->Authority: (optional: Use of Central Authority) Validate the Consumer certification
2626

27-
Provider->Consumer:Provide details of session
27+
Provider->Consumer:Provide details of Offer
2828

29-
Consumer->Consumer:Validate session type is supported
29+
Consumer->Consumer:Validate Offer type is supported
3030

31-
Consumer->Provider:"Claim" session and provide details
31+
Consumer->Provider:"Claim" Session and provide details
3232

3333
Provider->Consumer:Callback to indicate journey completion

‎resources/png-sequence.txt

+4-4
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Code Consumer->Code Provider:Provider capabilities requested from discovery endp
1616
Code Provider-->Code Consumer:Capabilities provided
1717
Code Consumer->Code Consumer:Ensure capabilities match\nand extract security configuration
1818

19-
Code Consumer->Code Provider:Request details of session
19+
Code Consumer->Code Provider:Request details of Offer
2020

2121
Code Provider->Code Consumer:Consumer capabilities requested from discovery endpoint
2222

@@ -29,11 +29,11 @@ opt Use of Central Authority
2929
Code Provider->Central Authority:Validate the Consumer certification
3030
end
3131

32-
Code Provider-->Code Consumer:Provide details of session
32+
Code Provider-->Code Consumer:Provide details of Offer
3333

34-
Code Consumer->Code Consumer:Validate that the session type is supported
34+
Code Consumer->Code Consumer:Validate that the Offer type is supported
3535

36-
Code Consumer->Code Provider:"Claim" session and provide additional details\n(e.g payment instrument, callback)
36+
Code Consumer->Code Provider:"Claim" Session and provide additional details\n(e.g payment instrument, callback)
3737

3838
note over Code Provider, Code Consumer:Consumer optionally completes activity\n(e.g. scanning items at checkout)
3939

‎resources/sequence.png

5.72 KB
Loading

0 commit comments

Comments
 (0)
Please sign in to comment.