Integrating the OmiseGO eWallet requires a new setup to be deployed. Feel free to get in touch for that step as we offer hosted solutions. Before starting any integration, it is important to understand which responsibilities OmiseGO is taking care of and which ones you will need to implement.
These are examples of features provided by the OmiseGO eWallet. You may integrate with the APIs to utilize these features.
| Area of responsibilities | Tasks |
|---|---|
| Token management | - Create loyalty tokens (/token.create) - Put more loyalty tokens in circulation (/token.mint) - Update loyalty token information (/token.update) - Provide user interface for creating new loyalty tokens (Admin Panel) - Provide user interface for add/remove of loyalty tokens from circulation (Admin Panel) |
| Secondary user store | - Create users along with their wallets (/user.create) |
| Transactions | - List all transactions (/transaction.all) - Perform credit/debit of loyalty tokens to/from users (/transaction.create) |
| Entity management | - Create, update and list accounts (/account.create, /account.update, /account.all) - Create, update and list users with their wallets (/user.create, /user.update, /user.all) - Assign and unassign roles to users in an account (/account.assign_user, /account.unassign_user) |
| API management | - Generate and invalidate access and secret keys for server application (/access_key.create, /access_key.delete) - Generate and invalidate API keys for mobile application (/api_key.create, /api_key.delete) |
| Payment request | - Generate payment requests with QR code (Transaction Request Flow) |
| Notifications | - Notify merchant panel user of new successful payments (eWallet API Websockets) |
These are examples of features that are out of scope of the OmiseGO eWallet. You will need to consider implementing these features into your application.
See the attached links for examples on how to implement these features in your application.
| Side | Area of responsibilities | Tasks |
|---|---|---|
| Server | User management | - Create and safely store end-user data (e.g. User) - Send user creation requests to eWallet API (e.g. Signup) - Maintain the immutable user identifier (provider_user_id) to identify a user in eWallet API (e.g. Signup, Login, Purchaser) |
| Server | Mobile app authentication | - Authenticate mobile application user (e.g. Authenticator) - Request authentication tokens from eWallet API and send to the client application (e.g. TokenGenerator) |
| Server | Transactions (read/write) | - Perform credit and debit calls to eWallet API (e.g. Purchaser) - Perform all other data-changing operations with eWallet API |
| Mobile | User management | - Register new user with the server application (e.g. iOS, Android) - Send user data updates to the server application |
| Mobile | User authentication | - Authenticate user with the server application (e.g. iOS, Android) - Retrieve and store eWallet API’s authentication token from the server application (e.g. iOS, Android) |
| Mobile | Transactions (read-only) | - Retrieve user wallets from the eWallet API - Retrieve the list of settings including supported tokens (e.g. iOS, Android) - All data-changing operations cannot be performed by the mobile application |