integration:transactions
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
integration:transactions [2018/05/18 11:06] 10.144.24.34 |
integration:transactions [2018/10/24 12:03] tjotov |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== No-code transcations ====== | ====== No-code transcations ====== | ||
| What if solution requires more than pure authentication? | What if solution requires more than pure authentication? | ||
| - | 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 [[documentation: | ||
| 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. | When user confirmation is required (i.e. user clicks on “pay” button) following workflow is processed. Service provider actions are in bold. | ||
| + | |||
| 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”). | ||
Page Tools
