Architecture diagram

During the integration of the Izipay SDK, the interactions between the application and the SDK have been optimized as much as possible in order to streamline the process and ensure a smooth user experience. Below is a diagram illustrating the steps involved in a payment transaction performed through the SDK:

1. Sending input data: In this step, you send the necessary data to initiate the payment process, such as amount, description, buyer's information, etc.

2. Token request: A request is made to the server to obtain a unique token representing the current transaction. This token will be used in subsequent steps to identify and manage the transaction.

3. Sending the token: The token obtained in the previous step is sent to the server to be linked to the corresponding transaction.

4. Merchant Configuration Query: A request is made to the server to obtain the specific merchant configuration, such as available payment methods, security options, etc.

5. Send trade configuration: The configuration obtained in the previous step is sent to the SDK so that it can adapt and display the appropriate options to the user during the payment process.

6. Display form and user interaction: The SDK displays the payment form to the user, where he/she can enter the payment details, such as card information, billing address, etc. The user interacts with the form to complete the transaction.

7. Sending transaction request: Once the user has provided the payment data, a request is sent to the server to process the transaction and perform the corresponding authorization or capture of funds.

8. Sending the payment result: The server responds with the result of the transaction, indicating whether the payment has been authorized or rejected. This result is sent to the SDK for processing.

9. Close form and send payment result: The SDK closes the payment form and sends the transaction result to the iOS project so that it can take appropriate actions, such as displaying a confirmation message to the user or updating the transaction status in the application.

10. End of payment notification: A notification is sent to the server or other interested parties to indicate that the payment process has been completed, which may trigger further actions such as sending an email receipt to the buyer or updating records in the system.

These steps represent a typical flow of integrating a payment form using your SDK into an iOS project. It should be noted that the exact details and method names may vary depending on the specific implementation of your SDK.