This scenario is applicable where a customer is providing the complete card number do the transaction (Card number, Expiry, CVV, and name on card)
HTTP Method: POST
Environment
Test Environment | https://test.payu.in/_payment |
Production Environment | https://secure.payu.in/_payment |
Applicable scenarios
- It is a guest checkout
- It is a standard checkout request where there is no need to save the card
Note
Plain card details coming from the merchant, so no changes are applicable in the request & response.
Request and response elements will remain intact as it is.
Request parameters
<th>
**Description**
</th>
<th>
**Example**
</th>
</tr>
<td>
`String` The merchant <Glossary>key</Glossary> is a unique identifier for a merchant account in PayU's database.
</td>
<td>
Your Test Key
</td>
</tr>
<tr>
<td>
api\_version\
`optional`
</td>
<td>
`String` The API version for this API.
</td>
<td>
1
</td>
</tr>
<tr>
<td>
txnid\
`mandatory`
</td>
<td>
`String` The transaction ID is a reference number for a specific order that is generated by the merchant. It is used to track the order and must be unique. PayU's system will not accept duplicate transaction IDs.
</td>
<td>
s7hhDQVWvbhBdN
</td>
</tr>
<tr>
<td>
amount\
`mandatory`
</td>
<td>
`String` This field should contain the payment amount for the transaction. If you want to use the cardless EMI option, the amount must be at least Rs. 8000
</td>
<td>
10.00
</td>
</tr>
<tr>
<td>
productinfo\
`mandatory`
</td>
<td>
`String` It should be a string containing a brief description of the product.```
Character Limit-100
```
</td>
<td>
iPhone
</td>
</tr>
<tr>
<td>
firstname\
`mandatory`
</td>
<td>
`String` The first name of the customer.```
Character Limit-60
```
</td>
<td>
Ashish
</td>
</tr>
<tr>
<td>
email\
`mandatory`
</td>
<td>
`String` The email of the customer.```
Character Limit-50
```
</td>
<td>
[[email protected]](mailto:[email protected])
</td>
</tr>
<tr>
<td>
phone\
`mandatory`
</td>
<td>
`String` The phone number of the customer.
* \*Note\*\*: This information is helpful when it comes to issues related to fraud detection and chargebacks. Hence, it is must to provide the correct information.
</td>
<td>
9876543210
</td>
</tr>
<tr>
<td>
lastname\
`mandatory`
</td>
<td>
`String` The last name of the customer.```
Character Limit-60
```
</td>
<td>
Verma
</td>
</tr>
<tr>
<td>
address1\
`optional`
</td>
<td>
`String` The first line of the billing address.```
Character Limit-100
```
</td>
<td>
H.No- 17, Block C, Kalyan Bldg, Khardilkar Road, Mumbai
</td>
</tr>
<tr>
<td>
address2\
`optional`
</td>
<td>
`String` The second line of the billing address.`Character Limit-100`
</td>
<td>
34 Saikripa-Estate, Tilak Nagar
</td>
</tr>
<tr>
<td>
city\
`optional`
</td>
<td>
`String` The city where your customer resides as part of the billing address.
</td>
<td>
Mumbai
</td>
</tr>
<tr>
<td>
state\
`optional`
</td>
<td>
`String` The state where your customer resides as part of the billing address,
</td>
<td>
Maharashtra
</td>
</tr>
<tr>
<td>
country\
`optional`
</td>
<td>
`String` The country where your customer resides.`Character Limit-50`
</td>
<td>
India
</td>
</tr>
<tr>
<td>
zipcode\
`optional`
</td>
<td>
`String` Billing address zip code is mandatory for the cardless EMI option.```
Character Limit-20
```
</td>
<td>
400004
</td>
</tr>
<tr>
<td>
surl\
`mandatory`
</td>
<td>
`String` The "surl" field is the success URL, which is the page PayU will redirect to if the transaction is successful. The merchant can handle the response at this URL after the customer is redirected there.
</td>
<td>
[https://apiplayground-response.herokuapp.com/](https://apiplayground-response.herokuapp.com/)
</td>
</tr>
<tr>
<td>
furl\
`mandatory`
</td>
<td>
`String` The "furl" field is the Failure URL, which is the page PayU will redirect to if the transaction is failed. The merchant can handle the response at this URL after the customer is redirected there.
</td>
<td>
[https://apiplayground-response.herokuapp.com/](https://apiplayground-response.herokuapp.com/)
</td>
</tr>
<tr>
<td>
hash\
`mandatory`
</td>
<td>
`String` It is used to avoid the possibility of transaction tampering. For more information on hash generation process, refer to [Generate Hash](doc:generate-hash-merchant-hosted).
</td>
<td>
`eabec285da28fd
0e3054d41a4d24fe
9f7599c9d0b6664
6f7a9984303fd612
4044b6206daf831
e9a8bda28a6200d
318293a13d6c193
109b60bd4b4f8b09
c90972`
</td>
</tr>
<tr>
<td>
<Glossary>pg</Glossary>\
`mandatory`
</td>
<td>
`String` The pg parameter determines which payment tabs will be displayed. Here, use 'CC' as the value.
</td>
<td>
CC
</td>
</tr>
<tr>
<td>
<Glossary>bankcode</Glossary>\
`mandatory`
</td>
<td>
`String` Each payment option is identified with a unique bank code at PayU. The merchant must post this parameter with the corresponding payment option’s bank code value in it.
</td>
<td>
AMEX
</td>
</tr>
<tr>
<td>
udf1 - udf5\
`optional`
</td>
<td>
`String` User-defined fields (udf) are used to store any information corresponding to a particular transaction. You can use up to five udfs in the post designated as udf1, udf2, udf3, udf4, udf5.\
`Character Limit-255`
</td>
<td>
Payment Preference, Shipping Method, Shipping Address1, Shipping City, Shipping Zip Code, etc.
</td>
</tr>
<tr>
<td>
ccnum\
`optional`
</td>
<td>
`varchar` This parameter must contain the 13 to 19-digit card number for credit or debit cards in general.
</td>
<td>
512\*\*\*6789012346
</td>
</tr>
<tr>
<td>
ccname\
`optional`
</td>
<td>
`varchar` It is the customer's name on card.
</td>
<td>
Ashish
</td>
</tr>
<tr>
<td>
ccvv\
`optional`
</td>
<td>
`varchar` This parameter must contain the CVV number of the card – as entered by the customer for the transaction.
</td>
<td>
123
</td>
</tr>
<tr>
<td>
ccexpmon\
`mandatory`
</td>
<td>
`integer` This parameter must contain the Expiry month that is mentioned under card validity.
</td>
<td>
10
</td>
</tr>
<tr>
<td>
ccexpyr\
`mandatory`
</td>
<td>
`integer` This parameter must contain the Expiry year that is mentioned under card validity.
</td>
<td>
2022
</td>
</tr>
**Parameter** |
---|
key `mandatory` |
Response
In addition to the parameters in the response of a Merchant Hosted Checkout transaction with a card, PayU returns network token, network token expiry for PCI complied or PayU token & its expiry for non-PCI complied merchants.