Wiki source code of account-onboarding
Last modified by ang on 2024/04/22 15:46
| 1 | (% class="jumbotron" %) |
| 2 | ((( |
| 3 | (% class="container" %) |
| 4 | ((( |
| 5 | Integrate to **PayEx Account onboarding API ** |
| 6 | ))) |
| 7 | ))) |
| 8 | |
| 9 | = Changelog = |
| 10 | |
| 11 | |
| 12 | (% id="HRoutesegments" %) |
| 13 | = Introduction = |
| 14 | |
| 15 | (% class="lead" %) |
| 16 | The account-onboarding API handle the onboarding process of accounts. Create account, upgrade of creditlimit. The onboard process may include payment flows for split-payments and credit accounts for retail finance scenarios. The api contains redirect scenarios for account onboarding, upgrades and authentication. |
| 17 | |
| 18 | == [[image:AccountOnboarding.png||height="660" width="474"]] == |
| 19 | |
| 20 | |
| 21 | (% id="HRoutedescription" %) |
| 22 | === Route description === |
| 23 | |
| 24 | Each resource in the API corresponds to its own route. All routes are structured according to a specific standard, explained below |
| 25 | |
| 26 | The below route is an example of a route towards resource3Id, to operate on this resource you must also include the ids of its parentresources in the route. |
| 27 | //api.payex.com/ledger/**{Subdomain}**/v1/**{LedgerNumber}**/resource1/**{resource1Id}**/resource2/**{resource2Id}**/resource3/**{resource3Id}**// |
| 28 | |
| 29 | (% border="1" %) |
| 30 | |=Route segment|=Description |
| 31 | |Subdomain|In this part of the API it will be credit-account |
| 32 | |LedgerNumber|The ledger identifier/number at PayEx |
| 33 | |resource1Id|Identifier of resource1 |
| 34 | |resource2Id|identifier of resource2, subresource to resource1 |
| 35 | |resource3Id|identifier of resource3, subresource to resource2 |
| 36 | |
| 37 | {{display reference="developer:Main.credit-account.api.account-onboarding.account-onboarding-from-swagger.WebHome"/}} |
| 38 | |
| 39 |