PineLabs

Follow the steps below to onboard PineLabs as a payment provider.

Watch Out!

While Optimizer can route payments based on your business logic, the method enablement of each gateway needs to be handled between you and the gateway, or it may lead to failed payments.

Prerequisites

Write to your PineLabs Plural Account Manager
with the following requests:
- Enable all the required payment methods and refunds. Mention that you are using Razorpay as the technology company to handle sensitive card data.
- Enable the Aggregator model. Otherwise, RRN and other attributes are not returned in the callback response of card payment initialisation. Razorpay supports only the aggregator model for Pine Labs Plural card integration.
- Enable the INQUIRY API for your Pine Labs Plural account to check the payment status.
- Allow dynamic URL in redirection URL.
Copy Razorpay in the email and we will provide the supporting document from our end.
Pine Labs Plural supports only the static callback URL (merchant_return_url). You need to share Razorpay's dynamic callback URL to whitelist. Share the following URL:
- Production redirect URL format - https://api.razorpay.com/v1/payments/<pay_payment_id>/callback/<hash>/<rzp_live_merchant_keys>
Handy Tips
After the Razorpay production URL is shared, the Pine Labs DBA team must configure the production database to support the Razorpay dynamic URL.
To pass your unique Order ID or Receipt for every order, write to your Relationship Manager to show the udf_data.udf_field_1 parameter in PineLabs Dashboard and customise report. Know more about
how to send your order id to PineLabs
.

Handy Tips
Only MasterCard and Visa networks will be supported by default for an AXIS terminal configuration done by PineLabs.

Integration Requirements

Before you go live with PineLabs on Optimizer, whitelist the dynamic URL.

The dynamic URL pattern needs to be whitelisted for PineLabs, or the payments will fail. To whitelist the dynamic URL pattern for PineLabs, you should communicate the requirements to the PineLabs account manager via email in a specific manner. Know more about

how to communicate via email

Add PineLabs as a Payment Provider

To add PineLabs as a payment provider:

Log in to your
Razorpay Dashboard
.
Go to the PAYMENT PRODUCTS section and click Optimizer.
In the top-right section, click Add Provider.
Select PineLabs in the list of gateways available and click Next.
Enter the provider name and description and click Next.
Enter your Access code, Merchant ID and Secure secret.
Select the payment methods you want to enable for PineLabs and click Submit.

You have successfully added PineLabs as a payment provider on Optimizer.

Supported Payment Methods

Email Format

Follow the email format given below to communicate the
prerequisites
or any other requirements to the PineLabs account manager:

Dear Account Manager,

We are using “Optimizer” as a technology service provider to manage our integration with PineLabs for account <Merchant/Account ID>.

In order to use this TSP, we require the following configuration changes:

Enable the Aggregator model for card transactions.
Allow Dynamic URL in redirection/return URL (Configure the production database to support dynamic URL).
Configure the below dynamic URL for return URL:
Enable the INQUIRY API to check the payment status.
Please enable the account for card, and UPI transactions.

Please share a list of the enabled banks for netbanking and networks for cards payments methods so that this can be configured at our end.

Regards,

Send Receipt/Order ID to External Gateway

You might be generating a unique Order ID or Receipt for every order which can be passed to PineLabs via

Orders API

To make your order id to be visible on the PineLabs dashboard:

In Razorpay's Orders API, use the receipt parameter to send your unique Order ID or Receipt.
Razorpay passes this value to PineLabs in the udf_data.udf_field_1 parameter.
Write to your PineLabs Relationship Manager to show the parameter udf_data.udf_field_1 in the dashboard and reports as per your use case.

Best Practices

Before routing all traffic or some traffic to a new gateway via Optimizer, the following best practices are recommended:

Live and Test Mode Rules

All rules configured on live or test mode on the Razorpay Dashboard will reflect on live mode. However, credentials added on test mode will not be automatically replicated in live mode.

Sanity Test at Razorpay

You can reach out to Razorpay for basic sanity testing of the integration. Razorpay will try a test payment of small value and ensure that the credentials are correct.

Perform Self Sanity Test

We recommend configuring a rule on live mode to route payments lesser than a set value (for example, ₹2) to the PineLabs gateway. This helps to test on production whether small value payments are being routed to PineLabs and working successfully, thus avoiding any direct impact on production traffic.

To configure a rule in live mode:

Log in to your
Razorpay Dashboard
.
In the left navigation, click Optimizer.
Click +Add Rule and enter the Rule name and Description.
Click Next and enter the following rule:
- In Parameter field, select Amount (In Rupees).
- In Select Connection field, select Less Than.
- In Enter Amount field, enter the value 2 and click Next.
Enter the value 100 in the Route field, select PineLabs in the Payment Via field, and click Next.
Click Publish Rule.

Go Live

After the integration is tested and successful, you can go live on PineLabs.