Frequently Asked Questions (FAQs)
Under Bank EMI, the customer bears the interest of the loan, whereas, in the case of Brand EMI, the interest is borne by the manufacturer of the product (OEM). Brand EMI is also known as no-cost EMI.
Please pass 'ppc_PayModeOnLandingPage' with value 4 for EMI payment option.
Send the product name, SKU of the OEM and product code (Product ID stored at the merchant's end)to developer.support@pinelabs.com. When you receive a confirmation on the configuration of the product, you need to perform a transaction and post the product code in parameter 'ppc_Product_Code'.
Send a mail to developer.support@pinelabs.com, Once the team confirms on configuration, you can go ahead and verify the same by performing a transaction. Do remember that you have posted 'ppc_PayModeOnLandingPage' parameter with values 4.
You can check the EMI of a product using the EMI calculator. Please refer to the EMI calculator document for details.
UAT - https://uat.pinepg.in/PinePGRedirect/
Production - https://pinepg.in/PinePGRedirect/
UAT - https://uat.pinepg.in/api/PG
Production - https://pinepg.in/api/PG
UAT - https://uat.pinepg.in/api/BrandEmiCalculator
Production - https://pinepg.in/api/BrandEmiCalculator
A process wherein merchant can install their Native app on Pine Labs Smartpos to trigger the transaction request as per integration guide for card swiping and printing programmatically and close their bill after successful transaction.
Your App should support Android 5.1 & above for integration on PAX A920 device.
As of now only Native app is supported on Smartpos integration. If merchant have hybrid app then they can change payment page into native to start integration.
An Intent in the Android operating system is a software mechanism that allows users to coordinate the functions of different activities to achieve a task.
Bluetooth printer and Bar Code scanner.
You can connect Bluetooth printer with Smart Pos and send the request to Home application for printing.
Ensure home application should run in the background in PAX device.
Yes, Smartpos device will allow to install more than one APP.
You can upload the APP via the USB cable or Bluetooth on the test device directly. Once you test out the payment's integrations, the APP needs to be routed through the PAX store via Pine Labs self-serve link for live deployments. The APP will be checked for code compliance and security before the same moves to PAX store.
Merchant to provide the final APK to Pine Labs who will upload it on PAX Store.
No, Pine Labs PAX store is only accessible from Pine Labs Smartpos device.
Mock-up/debug device is a testing device from Pinelabs. Pine Labs business team will provide the MOCK-UP/Debug device for testing and development. So that, 3rd Party app can install and test. Please ask your sales SPOC to raise a request for the same.
The role of Home application is to receive the payment & printing request from 3rd party app.
Pine Labs team will provide the Application ID for UAT and Production.
Once final APK uploaded in Pine Labs PAX store, it will take next 7 days to update the new version of APK.
Following minimum requirements should be ensured for all existing or new Third party service providers:
- Due diligence should be performed on vendor financial stability before an agreement is entered with Third party service provider. Pine Labs and Third party may enter in escrow agreement in case of any issues
- Non-disclosure agreement (NDA) to be executed between Pine Labs and Third-party service provider
- Pine Labs defined NDA shall be executed with Third party service provider but not limited to liabilities, security and confidentiality requirements C. Application Security Assessment document:
- Application Secure Code Review Report: Application secure code review report shall be obtained from vendor which would have been tested against OWASP and SANS and the same shall be shared with Information Security group before testing
- Application Pentest Report: Application penetration testing report and assessment report should be obtained from Third party service provider which is tested against OWASP & SANS requirement. The same shall be shared with Information Security group before testing
- Following technical controls should be evaluated by Business such as:
- Application interface authentication
- Data masking techniques
- Rest full API's
- Security Assessment Ownership and Requisite Security assessment on Third party application will be under ownership of Pine Labs information Merchant will maintain their APP security report.
Your Billing APP should be compatible to Android version 5.1 & above which is supported on Pinelabs PAX terminal. In case the Android version is updated at our end for the terminals, you may require your APP to be updated to the same version in order to be compatible with such version. Such changes will be communicated to you well in advance by our team.
Any update to your Billing App has to be submitted to Pine Labs team as they will approve the sign the new release and push the update via App store.
Your Billing APP can run in background on Plutus Smart terminal to check the latest version available on your server. Whenever the Merchant turns on the device with Internet connectivity, the same gets updated.
You will be provided with the Test terminal as a part of the Integration starter kit along with the Integration guide having details of different API's. You may upload your Billing APP integrated with our Payment API's to start testing the End to End flows.
While you can pass any tender mode in the API request, you can test basic Debit/Credit card sale transactions on the test devices. Other Payment modes can be turned on basis the requirements raised.
No, the device is strictly for the testing purpose. But you can see the entire flow for the available payment modes.
Yes, the Plutus Smart device supports external hardware connectivity both through the wired attachment and via Bluetooth connectivity. You can connect an external scanner and via an additional attachment with device provided by Pine Labs basis the requirement. However, you would require to call our API to access the same. API for the same is provided in the Billing Integration guide shared by our team.
No. Billing APP cannot directly access the NFC hardware of the device. As per compliance, only the Plutus payments APP can access the NFC hardware. However, you can accept your closed loop card on the device if the same has been developed in the Payments APP by Pine Labs team. The development is taken up on case to case basis with a fixed TAT.
If your Billing APP works on an unsecured Intranet offline, the same can be connected directly using device WIFI. In case, there is an additional firewall which requires authentication on client's browser, the same will not work as the device does not allow any browser app.
API integrations happen at your end. Our tech team support is available for troubleshooting any issues which may come at the time of integration. You can reach out to your sales SPOC or write us at smartpos.integration@pinelabs.com
You can test this feature functionality on the test device itself. We can share a sample report format in an excel format for visualization purpose for how you may see the test results.
No, Google Play services won't work on the terminal. Hence, services like Google analytics, Firebase, app notifications won't work. Also, automatic update of billing app would only work via Pine Labs App Store after signing of the app by Pine Labs security team.
There is no browser client app available for the terminal, browser dependent features can be opened as in-app Web View content.
No. Remote management (like sure lock/TeamViewer) on the EDC terminal cannot be implemented.
Sample code is already available in the Integration guide.
No, all type of request of 3rd party app should process through Pine Labs HOME APP.
Validation is the process of do the end to end testing Merchant billing app where we execute test case according to merchant requirement.
Merchant APP version should be updated with every new release.
Pine Labs API response message should display on billing app.
After successful transaction host will send message of "Approved" along with Approval code.
Merchant will consider "Approved" message instead of Approval Code.
Amount should be in Paisa. Example 1Rs = 100 Paisa.
Pine Labs will provide the application ID. Merchant has to ensure to pass same application ID in the request string.
A process wherein merchant can install their billing app and ePOS app on on any Android mobile to trigger the supported payment transaction request
As of now only Native app is supported for ePOS integration. If merchant have hybrid app then they can change payment page into native app to start integration.
On ePOS app installation, new merchant need to onboard on ePOS app through their mobile number and verify the details during the sign up process. An onboarded merchant can add the multiple users/clients. Although this step is not requirted to start developing your app using ePOS simulator app. This app is hosted in Git Hub. Refer to ePos under API section for details
Application id is the unique identifier assigned to each app on app registration in developer portal and it shall be passed in requests to ePOS app.
Application id is the unique identifier assigned to each app on app registration in developer portal. Merchant has to ensure to pass same application ID in the request string.
This response may come while initiating the request from billing application.
- Make sure that billing application package name is correct i.e. installed billing application package name and package name shared with PineLabs.
- Logout and re-login required in the ePOS app before initiating the request from billing app to get sync the billing application with master server.
Make ensure that permission to ePOS app to run in background should be allowed in your android device. It can be found in app permissions in app setting.
Currently ePOS is compatible with any Android mobile running on version 5 and above.
Credit/Debit card sale, UPI, BQR and wallets and bank and brand EMI payments.
We can initiate multiple transactions and check the status of any transaction through get status API.
Pine Labs' Plural Checkout for Mobile SDK facilitates enhanced mobile payments experience for end user in mobile app eco-system. It helps to build best in market mobile-based payment systems. It enhances the payment experience and boosts the success rate with features like Auto-OTP processing, Showing correct keypad for required input, Auto-zoom and Auto-scroll, Remember Net banking User ID, Auto-manual reload when page load fails etc.
Pine Labs' Plural XT is a system that facilitates the integration with a number of online payment gateways. It provides an umbrella type relationship with payment gateways and promises its merchant the intelligent dynamic routing, deeper analytics, unified dashboard, simpler integration process.
Following are the payment gateways/aggregators are supported by Pine Labs' Plural XT.
| Aggregators | Bank PG | Wallets | Net Banking | UPI |
|---|---|---|---|---|
| BillDesk | ICICI | PayZapp | BillDesk | HDFC |
| Razorpay | HDFC | PayU | PayU | PayU |
| PayU | Axis | Razorpay | Razorpay | Razorpay |
| PhonePe | G-Pay |
No. You need to integrate with Pine Labs' Plural XT. It is a one-time activity. After that, you just need to use your credentials (MID, Secret Key etc.) which possess from the payment gateways. You can configure these payment gateways from the dashboard of Pine Labs' Plural XT and enter the credentials on the gateway configuration page. You can follow this process to add any payment gateway supported by Pine Labs' Plural XT.
Once you are onboarded on Pine Labs' Plural XT, you can access your access code and secrete key. These are provided on Credentials section of Settings on Pine Labs' Plural XT Dashboard.
No. you can save any number of cards against a customer id.
Yes. You can delete one or more cards saved against a customer. You can simply upload a csv file in the merchant dashboard.
Yes. You can explore the merchant dashboard of Pine Labs' Plural XT. You simply have to sign up by providing your email id and setting a password. After that, you can explore the dashboard.
Yes. You can the set priority of payment gateways through the merchant dashboard. These priorities are considered for the purpose of transaction routing.
Yes. You can design your own custom routing logic. This can be done through a small piece of JavaScript code. By this, merchants can define the channel-based routing (based on the source of the transaction - Desktop or Mobile), Issuer based routing, and volume-based routing.
Yes. Once you submit the JavaScript code of custom routing, it goes through an approval process by Pine Labs' Plural XT support team. The team takes care of the coding part of the custom routing. However, you must take due diligence of the logic part of it before submitting the code.