FEED Integration

Use Cases

For Independent Sales Organizations (ISOs)

• If you have your own Customer Relationship Management (CRM) system, you can develop custom dashboards and reports for real-time monitoring and analysis of transactions.
• FEED gives you more flexibility to manage transactions and settlements for your merchants.

For Independent Software Vendors (ISVs)

• Integrate FEED into your software solutions to provide your clients with advanced features for tracking and reporting payments.
• Offer real-time data validation and reporting, making your software more valuable.
• Tailor FEED integration to each client’s specific needs, creating unique solutions that improve their experience.

For Merchants (Multi-Store)

• If you have your own CRM, you can integrate FEED to view and manage all transactions from all your stores in your own CRM.
• Manage your transactions and settlements with more flexibility to fit your business needs

Authentication Process

We have provided three types of authentication in FEED services:

• Default - Deprecated
• Basic Authentication
• HMAC

Default: Deprecated

If the integrator is enabled by default, we will send the payload without any authentication. We will only require the event trigger URL as mandatory.

Basic Authentication

If the integrator is enabled with Basic Authentication, they need to provide the username (APIKey) and password (SecretKey) in the portal along with the Event Trigger URL. We will send the payload and authorization in base64 format.

HMAC

If the integrator is enabled with HMAC then we will provide the two options whether he can provide his own HMAC key and share with iPOSPays team or we will provide the Key generate button it will be used to generate the HMAC key that needs to be copied by the integrator.

Logic used for the HMAC Generation:

String param_data = param_value1|param_value2|param_value3|………|;

String final_data = secret_key|param_data;

String secureHash = generate_secure_hash_using_SHA512_and_secret_key;