Overview
The DWS solution provides a reliable and efficient way to integrate an e-wallet into your application. This document walks you through the overall process and introduces the available integration choices.
Integration process
The following overall integration flow shows the steps to achieve end-to-end integration. The main steps include Preparation, Integration, Test in Sandbox, and Acceptance.
For more details, see Integration process.
Integration solutions
DWS provides a well-designed integration solution that consists of two parts: API integration and Mobile SDK integration.
API Integration
The server API integration enables your application to interact with DWS's wallet APIs through HTTP protocol or server-side SDK. These two integration options provide the same capability with different advantages. Before you start, compare the features, availability, and integration efforts as listed in the table below:
Solution | API Integration | |||
Impl. Options | HTTP | Server-side SDK | ||
Technology | HTTP | Java | Go | Node |
Introduction | Based on HTTP protocol, merchant interacts with APIs by manually constructing the HTTP requests. | Merchant interacts with APIs via the SDK, which encapsulates the process of encrypting, signing and sending the HTTP requests. | ||
UI Customization | Full | |||
Backend Requirement | Merchant's own backend is required. | |||
Integration point | Merchant Server | |||
Integration effort | Medium | Low | ||
Advantages |
|
| ||
Mobile SDK Integration
The Mobile Security SDK will be integrated into your Android/iOS application to mitigate the risk of unauthenticated transactions.
For more details, see Integration solutions.