This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
integration:transactions-new [2018/05/18 11:04] 10.144.24.34 created |
integration:transactions-new [2019/08/01 08:38] tjotov removed |
||
---|---|---|---|
Line 3: | Line 3: | ||
Transactions are user confirmed decisions like payments. They are secure, authenticated and validated using personal factor. | Transactions are user confirmed decisions like payments. They are secure, authenticated and validated using personal factor. | ||
Tiny coding effort is required like providing confirmation text and evaluating the operation. | Tiny coding effort is required like providing confirmation text and evaluating the operation. | ||
- | When user confirmation is required (i.e. user clicks on “pay” button) following workflow is processed. Service provider actions are in bold. Two main methods are supported: | + | When user confirmation is required (i.e. user clicks on “pay” button) following workflow is processed. Service provider actions are in bold. |
- | ===== Push notification ===== | ||
- | This scenario is available for smart phones only. User must be logged in AAA Reverse Proxy. | ||
- | - Call AAA Reverse Proxy push transaction method (standard http request) providing confirmation text and verification level (personal factor, bio factor, no second factor) | ||
- | * Then AAA Reverse Proxy creates a request and sends it via push notification to user’s smart phone | ||
- | * Request is processed via PEIG. | ||
- | * User confirms it and provides personal factor | ||
- | * AAA Reverse Proxy evaluates request and sends a response back to service provider applications | ||
- | - Read response (JSON) and parse it | ||
- | - Evaluate success / failure: OK, User rejected, Wrong personal factor, etc. | ||
- | |||
- | User experience: | ||
- | - User clicks on payment button. | ||
- | - A confirmation message is displayed on his smart phone (PEIG application) | ||
- | - If user agrees, personal factor is required (or bio factor) | ||
- | - Done | ||
- | |||
- | ===== Generic transaction ===== | ||
This scenario has no limitations and can be used even for non-authenticated users (every ADUCID operation is also authentication). | This scenario has no limitations and can be used even for non-authenticated users (every ADUCID operation is also authentication). | ||
- Prepare confirmation text (e.g. “Pay $99 from account 123456789 to account 987654321”). | - Prepare confirmation text (e.g. “Pay $99 from account 123456789 to account 987654321”). |