Pay10 Hosted Integration Guide

The PAY10 Payment Gateway is a secure website, where you redirect customers from your Website/Ecommerce/Mobile platform to make a payment using Credit Card/Debit Card/Pay10 Wallet other payment options. The gateway collects customer payment details in a secure manner using standard HTML forms and processes the payment transaction. After the payment is complete, the customer is returned to your website and you receive a real-time notification of the payment, which includes details of the transaction.

Pre-requisites

It is expected that the users may go through the entire guide to understand the Integration Requirements though it is easy for people with technical understanding. It is assumed that the Merchant doesn't have any specific business need for capturing the Customer's Card Information on their website as additional regulatory requirements of having PCI DSS certification is mandatory for capturing Customer's Credit/Debit/Pay10 Wallet information on Merchant websites. All Card/Pay10 Wallet information is captured seamlessly on PAY10 Payment Gateway Page in a secured manner and transaction response is returned to the Merchant real-time post processing of the transaction.

Integration Overview

Merchants can enjoy the benefit of enabling a vast collection of payment partners with one simple integration. PAY10 has done the heavy lifting of supporting payments, payouts, and settlements in fiat or crypto currencies so merchants can focus on building wonderful user experiences for their customers.

Key Functionalities

Accepting Payments
Merchants have the flexibility to choose to accept payments from a wide range of fiat and crypto currencies. Simply make a payment request to PAY10 and a payment HTML file will be returned. Display the rendered HTML file to the customer and merchants can start accepting payments.

1. When the user wishes to purchase good/services from your company, the merchant would need to send a payment request to PAY10’s server.
2. PAY10 will process the payment request and immediately return a response containing a payment page’s HTML.
3. Merchant presents the payment page to the user.
4. The user will enter and submit the payment details within this website.
5. Once the transaction has been completed, the transaction details, including the status, will be sent to the return_url that was provided initially in the payment request.

Payment Request

This endpoint initiates the payment request from the merchant.

Request Parameters

📘

*Abbreviations: NU - Numeric, CH – Character, AN – Alphanumeric

Amount Forma

Rules for handling the decimal point for the amount value is expressed below:

Generating the Hash Value

SHA-256

PAY10 requires a SHA-256 HMAC digital signature be included in each payment request to ensure the data integrity and authenticity of the request. The instructions below demonstrate how PAY10 expects the data to be encrypted:

1. Rank order of the payload’s key-value pairs in ascending alphabetical order of the keys.
2. Concatenate the key-value pairs into a single-line string and, instead of using an ampersand (&), delimit the key-value pairs with a tilde (~).
3. Append the secret key at the end of the string.
4. Wrap the entire string with a pair of curly brackets .
5. Generate a hash value of the string using the PAY10 secret and SHA-256 algorithm.
6. Convert all characters of the hash value into uppercase.

This is an example string of a payment request before it is hashed:

📘

AMOUNT=100~CURRENCY_CODE=784~CUST_CITY=NewDelhi~CUST_COUNTRY=UAE~CUST_EMAIL=[[email protected]](mailto:[email protected])~CUST_NAME=JohnPaul~CUST_PHONE=09999999999~CUST_SHIP_CITY=NewDelhi~CUST_SHIP_COUNTRY=UAE~CUST_SHIP_EMAIL=[[email protected]](mailto:[email protected])~CUST_SHIP_NAME=JohnPaul~CUST_SHIP_PHONE=0123456789~CUST_SHIP_STATE=Delhi~CUST_SHIP_STREET_ADDRESS1=House01~CUST_SHIP_STREET_ADDRESS2=Newlane~CUST_SHIP_ZIP=110075~CUST_STATE=Delhi~CUST_STREET_ADDRESS1=Newlane~CUST_STREET_ADDRESS2=Sector44~CUST_ZIP=110075~ORDER_ID=PAYORD220920151610~PAY_ID=160234578452178~PRODUCT_DESC=Mobile~RETURN_URL=<https://www.example.com/return_url~TXNTYPE=SALEb6200e78557e4e55>

This is the expected result of the hash value:

📘

Hash value = 6797F1842DEB4F3EBAEAD53E1BAFD5A535D322B9FA3893F201FDB03933EEAE09

The purpose of the SHA256 signature field is to ensure the integrity of the data posted back to your server. You should always compare the SHA256 signature field's value posted by PAY10 with the one you calculated.

AES-256

PAY10 requires AES-256 CBC to decrypt the received response. Pass ENCDATA to AES-256 for decryption.

This is an example string of a payment response before it is decrypted:

📘

{"PAY_ID":"1009120125180122","ENCDATA":"N2N0ktvZ07xVU1YgMdIRpiGChgc3u9sZhCra9twHXiLZveG2y9pAub/ijAnELRc4mJjFqcJtmCWaV3wDTTwAqEVE54mSUHoMGySSd/CaDudHu4ciBlhlRigGyr7Vqev692bN412msQMatZBmfE2F28onz9h2L2gsnF1+rNBcsct+sxK9IhoOmq/TltadYUrYRnu3sxkzzjy/ByeHDivy7IbzL26p3q8oW6YVRhtmmDUsfLcLYyr5t9KLGSMb34958r8jinqQqIpxQqqw5wc6iCNJ0geIOgFFp6miYzCTC9WyafAxSyEZA3VREaWYi83/1ZfF+NolG5JZg3d9Fpu9DwsXlNvAWp296Avp65Ero+Rn0XhDZG8Uey6NXIgo+fWqLegxaxjKs7dkM1eEnppNeep1KupPlxYX9EaKQoqwPMq0kcZMW/2c06/goFx6rmDGguLoxDvs7QljouYhPK+7+EdLts9GbzAYzzI8p1kTP0L8RhDjC+be3jjHG1oEF1j0jUmbpE67dGdGFG68W2c71iaFAjVyy8pOs6bgoiKi9dg1i6PmukaYZE0fahSWhiqjHPx4uh6XMR7d1+Mkkc84QW6fT1RSFrzpAixoV4Nj9XOPBarrz6jLIgnswE21/amufH3bd/4+TxS1ykI0XqpqVJEO+L7aR2gcWc1GekrbhtiH06x56b7rueunIg2iJ0R6NIVoRVoauLZaOpsJTL9tpuHkUlAuucIHeHwmh4FzOAfUghohnDpkgFxfKg7LeyyG2q+gcOKKOAfjQMctbjExmb6idxCW9Nqdv65NnPf+9cQYYZTvk5Fbyg5DvZtoaIxlQagIkq4mcMyzfQdSJrIBN958vTE419ZZ3kxJPhUELAwb4dl89u8mG PmGgXgrtyvL}

After Decryption you will get the similar string:

📘

{RESPONSE_DATE_TIME=2024-02-25 18:08:51~RESPONSE_CODE=000~TXN_ID=1669120314180851~CUST_PHONE=9999999999~TXNTYPE=SALE~CURRENCY_CODE=784~SURCHARGE_FLAG=N~HASH=611C4492531EFDF77BF8DC90E6A810CC9F5D4D9934602F15632BE306F421978F~RETURN_URL=http\://localhost/uat/response.php~STATUS=Captured~PAY_ID=1049120302195014~PG_REF_NUM=1669120314180851~ORDER_ID=PAY10_681895713~AMOUNT=100~RESPONSE_MESSAGE=SuccessfulPayment~CUST_EMAIL=[[email protected]](mailto:[email protected])~CUST_NAME=Test }

Sending Request and Getting Response

Request

This is an example string of a payment request before it is hashed:

📘

AMOUNT=100~CURRENCY_CODE=784~CUST_CITY=Demo City~CUST_COUNTRY=DemoCountry~CUST_EMAIL=[[email protected]](mailto:[email protected])~CUST_NAME=Demo Merchant~CUST_PHONE=1234567890~CUST_SHIP_CITY=Demo Ship City~CUST_SHIP_COUNTRY=Demo Ship Country~CUST_SHIP_EMAIL=[[email protected]](mailto:[email protected])~CUST_SHIP_NAME=Demo Ship Customer~CUST_SHIP_PHONE=0123456789~CUST_SHIP_STATE=Demo Ship State~CUST_SHIP_STREET_ADDRESS1=Demo Ship Address1~CUST_SHIP_STREET_ADDRESS2=Demo Ship Address2~CUST_SHIP_ZIP=Demo Ship Zip Code~CUST_STATE=Demo State~CUST_STREET_ADDRESS1=Demo Address1~CUST_STREET_ADDRESS2=Demo Address2~CUST_ZIP=DemoZipCode~ORDER_ID=PAYORD220920151610~PAY_ID=160234578452178~PRODUCT_DESC=DemoProduct~RETURN_URL=http\://localhost:8080/MerchantSimulator/response.jsp~TXNTYPE=SALEb6200e78557e4e55

Now use SHA256 Encryption to encrypt the above string. This is the expected result of the hash value:

📘

Hash value= 6797f1842deb4f3ebaead53e1bafd5a535d322b9fa3893f201fdb03933eeae09

Now change the above string to Uppercase.

📘

Hash value= 6797F1842DEB4F3EBAEAD53E1BAFD5A535D322B9FA3893F201FDB03933EEAE09

Final Request String:

<form action="https://uatpg.pay10.ae/pgui/jsp/paymentrequest” method="post" >
<input type="text" name="PAY_ID" value="1507231702331001"/>
<input type="text" name="MERCHANTNAME" value="Demo Merchant"/>
<input type="text" name="ORDER_ID" value="ORDID2234"/>
<input type="text" name="AMOUNT" value="100"/>
<input type="text" name="TXNTYPE" value="SALE"/>
<input type="text" name="CUST_NAME" value="Demo"/>
<input type="text" name="CUST_STREET_ADDRESS1" value="Gurgaon"/>
<input type="text" name="CUST_ZIP" value="123456"/>
<input type="text" name="CUST_PHONE" value="9999999999"/>
<input type="text" name="CUST_EMAIL" value="[email protected]"/>
<input type="text" name="PRODUCT_DESC" value="CD Player"/>
<input type="text" name="CURRENCY_CODE" value="784"/>
<input type="text" name="RETURN_URL" value="http://www.yourwebsite.com/response.php"/>
<input type="text" name="HASH" value="6797F1842DEB4F3EBAEAD53E1BAFD5A535D322B9FA3893F201FDB03933EEAE09"/>
<input type="text" name="PAY_ID" value="1507231702331001"/>
<input type="submit" value="Click to Pay" name="submit"/>
</form>

Response Parameters

After completion of the transaction, the customer is redirected back to the merchant at the return URL provided. In case the merchant does not receive the transaction response, a status enquiry request can be initiated.

Response Received:

📘

{"PAY_ID":"1009120125180122","ENCDATA":"N2N0ktvZ07xVU1YgMdIRpiGChgc3u9sZhCra9twHXiLZveG2y9pAub/ijAnELRc4mJjFqcJtmCWaV3wDTTwAqEVE54mSUHoMGySSd/CaDudHu4ciBlhlRigGyr7Vqev692bN412msQMatZBmfE2F28onz9h2L2gsnF1+rNBcsct+sxK9IhoOmq/TltadYUrYRnu3sxkzzjy/ByeHDivy7IbzL26p3q8oW6YVRhtmmDUsfLcLYyr5t9KLGSMb34958r8jinqQqIpxQqqw5wc6iCNJ0geIOgFFp6miYzCTC9WyafAxSyEZA3VREaWYi83/1ZfF+NolG5JZg3d9Fpu9DwsXlNvAWp296Avp65Ero+Rn0XhDZG8Uey6NXIgo+fWqLe gxaxjKs7dkM1eEnppNeep1KupPlxYX9EaKQoqwPMq0kcZMW/2c06/goFx6rmDGguLoxDvs7QljouYhPK+7+EdLts9GbzAYzzI8p1kTP0L8RhDjC+be3jjHG1oEF1j0jUmbpE67dGdGFG68W2c71iaFAjVyy8pOs6bgoiKi9dg1i6PmukaYZE0fahSWhiqjHPx4uh6XMR7d1+Mkkc84QW6fT1RSFrzpAixoV4Nj9XOPBarrz6jLIgnswE21/amufH3bd/4+TxS1ykI0XqpqVJEO+L7aR2gcWc1GekrbhtiH0 6x56b7rueunIg2iJ0R6NIVoRVoauLZaOpsJTL9tpuHkUlAuucIHeHwmh4FzOAfUghohnDpkgFxfKg7LeyyG2q+gcOKKOAfjQMctbjExmb6idxCW9Nqdv65NnPf+9cQYYZTvk5Fbyg5DvZtoaIxlQagIkq4mcMyzfQdSJrIBN958vTE419ZZ3kxJPhUELAwb4dl89u8mG PmGgXgrtyvL}

Now Again AES256 will be used to decrypt the response -

This is an example string of a payment response after it is decrypted:

📘

{ RESPONSE_DATE_TIME=2024-02-25 18:08:51~RESPONSE_CODE=000~TXN_ID=1669120314180851~CUST_PHONE=9999999999~TXNTYPE=SALE~CURRENCY_CODE=784~SURCHARGE_FLAG=N~HASH=611C4492531EFDF77BF8DC90E6A810CC9F5D4D9934602F15632BE306F421978F~RETURN_URL=http\://localhost/uat/response.php~STATUS=Captured~PAY_ID=1049120302195014~PG_REF_NUM=1669120314180851~ORDER_ID=PAY10_681895713~AMOUNT=100~RESPONSE_MESSAGE=SuccessfulPayment~CUST_EMAIL=[[email protected]](mailto:[email protected])~CUST_NAME=Test }

The below Table shows the response parameters sent to merchant:

📘

For status enquiry, you can refer to the status enquiry doc - Status Enquiry

And for refund, please refer to the refund doc from the API doc hub - Refund Transaction

Response Codes

Please refer to the below table which contains the details of the response code and the associated message: