Additional Info for Payment APIs

This section describes the additional information on v2/payment API such as character limit and data type of each parameter or fields of various JSON objects.

Request headers

Request body

order JSON object fields

billingDetails JSON object fields

callBackActions JSON object fields

paymentMethod JSON object Fields (only for Seamless Integration)

paymentCard JSON object fields (only for Seamless Card Payments)

Character Limits Summary

Production vs Test Environment Differences:

• firstName: 60 characters (Production), 20 characters (Test)
• All other parameters have the same limits across both environments

Key Parameter Limits:

• referenceId (txnid): 25 characters
• productInfo: 100 characters
• firstName: 60 characters (Production), 20 characters (Test)
• lastName: 20 characters
• email: 50 characters
• phone: 50 characters
• address1: 100 characters
• address2: 100 characters
• city: 50 characters
• state: 50 characters
• country: 50 characters
• zipCode: 20 characters
• successAction/failureAction/cancelAction URLs: 50 characters
• userDefinedFields (udf1-udf5): 255 characters each

Card-Specific Formats:

• cardNumber: 13-19 digits (15 for AMEX, 13-19 for Maestro)
• validThrough: MM/YY format (MM: 01-12, YY: two-digit year)
• cvv: 3-4 digits (3 for most cards, 4 for AMEX)

Key Differences between v1 and v2 _payment API

Parameter Changes:

1. key → accountId: Merchant key parameter renamed
2. txnid → referenceId: Transaction ID parameter renamed
3. amount → order.paymentChargeSpecification.price: Amount moved to nested object
4. productinfo → order.productInfo: Product info moved to order object
5. firstname, lastname, email, phone → billingDetails object: Customer details grouped into object
6. address1, address2, city, state, country, zipcode → billingDetails object: Address fields grouped
7. surl, furl, curl → callBackActions object: Callback URLs restructured
8. pg, bankcode → paymentMethod object: Payment method details grouped (seamless only)
9. ccnum, ccvv, ccexpmon, ccexpyr → paymentCard object: Card details grouped (seamless only)
10. hash → authorization header: Authentication moved to header
11. udf1-udf5 → order.userDefinedFields object: User defined fields grouped

New Parameters in v2:

• currency: Transaction currency (mandatory)
• paymentSource: Payment source identifier (optional)
• additionalInfo.txnFlow: Flow type for non-seamless integration
• callBackActions.cancelAction: Cancel callback support

Integration Flow Changes:

• Non-seamless: Must include additionalInfo.txnFlow = "nonseamless"
• Seamless: Requires paymentMethod and paymentCard objects
• Headers: Authentication moved to headers with date-based signature
• Structure: More modular with nested objects for better organization

API Endpoints

v2 Endpoints:

• Test Environment: https://apitest.payu.in/v2/payments
• Production Environment: https://api.payu.in/v2/payments
• HTTP Method: POST

Request Format:

{
  "accountId": "merchant_key",
  "referenceId": "unique_transaction_id",
  "currency": "INR",
  "order": {
    "productInfo": "Product description",
    "paymentChargeSpecification": {
      "price": "1000.00"
    }
  },
  "billingDetails": {
    "firstName": "John",
    "email": "[email protected]",
    "phone": "9876543210"
  },
  "callBackActions": {
    "successAction": {
      "redirectUrl": "https://example.com/success"
    },
    "failureAction": {
      "redirectUrl": "https://example.com/failure"
    }
  },
  "additionalInfo": {
    "txnFlow": "nonseamless"
  }
}