Payment with Zero Code Change

Process payments using previously saved card tokens through PayU's v2 API. This method allows merchants to charge customers without requiring them to re-enter their card details, providing a seamless payment experience.

Overview

The v2 saved card transaction API enables merchants to process payments using card tokens that were previously stored through PayU's tokenization service. This integration follows the same structure as the standard v2 cards integration but uses a cardToken instead of sensitive card details.

📘

Note

To use saved card transactions, you must first have stored the card using PayU's card tokenization service and obtained a cardToken.

Environment

Request Headers

var merchant_key = 'smsplus';
var merchant_secret = 'izF09TlpX4ZOwmf9MvXijwYsBPUmxYHD';
// date
var date = new Date();
date = date.toUTCString();

// authorization
var authorization = getAuthHeader(date);

function getAuthHeader(date) {
    var AUTH_TYPE = 'sha512';
    var data = isEmpty(request['data']) ? "" : request['data'];
    var hash_string = data + '|' + date + '|' + merchant_secret;
    var hash = CryptoJS.SHA512(hash_string).toString(CryptoJS.enc.Hex);
    return `hmac username="${merchant_key}", algorithm="${AUTH_TYPE}", headers="date", signature="${hash}"`;
}

Request Body

The request body structure for saved card transactions follows the v2 payments API format with specific parameters for tokenized cards:

paymentMethod object fields description

paymentCard object fields description (Saved Card)

📘

Note

For saved card transactions, the cardToken replaces sensitive card details like cardNumber, validThrough, and ownerName. CVV may be optional depending on your merchant configuration.

order object fields description

additionalInfo object fields description

callBackActions object fields description

billingDetails object fields description

Sample Request

{
    "accountId": "smsplus",
    "txnId": "txn_saved_card_001",
    "amount": "1000",
    "userCredentials": "merchant123:customer456",
    "paymentMethod": {
        "name": "CreditCard",
        "bankCode": "CC",
        "paymentCard": {
            "cardToken": "57cb996f2eaeee525765a",
            "cvv": "123"
        }
    },
    "order": {
        "productInfo": "Premium Subscription",
        "orderedItem": [
            {
                "itemId": "SUB001",
                "description": "Monthly Premium Plan",
                "quantity": 1,
                "amount": 1000
            }
        ],
        "userDefinedFields": {
            "udf1": "recurring_payment",
            "udf2": "monthly",
            "udf3": "premium",
            "udf4": "auto_renewal",
            "udf5": "customer456"
        },
        "paymentChargeSpecification": {
            "price": "1000"
        }
    },
    "additionalInfo": {
        "enforcePaymethod": "CC",
        "createOrder": true,
        "authOnly": false
    },
    "callBackActions": {
        "successAction": "https://yoursite.com/payment/success",
        "failureAction": "https://yoursite.com/payment/failure",
        "cancelAction": "https://yoursite.com/payment/cancel"
    },
    "billingDetails": {
        "firstName": "John",
        "lastName": "Doe",
        "address1": "123 Business Street",
        "phone": "9876543210",
        "email": "[email protected]",
        "city": "Mumbai",
        "state": "Maharashtra",
        "country": "India",
        "zipCode": "400001"
    }
}

Response Parameters

Sample Response

{
    "txnId": "txn_saved_card_001",
    "paymentId": "1999110000001770",
    "message": "Please call verify api to get the transaction status",
    "status": "pending",
    "cardDetails": {
        "cardToken": "57cb996f2eaeee525765a",
        "cardNumber": "XXXX-XXXX-XXXX-5603",
        "cardType": "VISA"
    }
}

Key Benefits of Saved Card Transactions

• Enhanced Security: Sensitive card data is tokenized and stored securely by PayU
• Improved User Experience: Customers don't need to re-enter card details
• Faster Checkout: Reduced form fields and processing time
• PCI Compliance: Reduced PCI scope as card data is handled by PayU's tokenization service
• Reduced Cart Abandonment: Simplified payment flow increases conversion rates

Important Considerations

📘

Security Notes

• Card tokens are unique to each merchant-customer combination
• Tokens cannot be used across different merchant accounts
• CVV collection is configurable based on your security requirements

📘

Token Management

• Card tokens remain valid until explicitly deleted or the card expires
• Expired card tokens will need to be replaced with new tokens
• Use the Get User Cards API to retrieve available tokens for a customer

Error Handling

Common error scenarios for saved card transactions:

Reference

After initiating a saved card payment, use the Verify Payment API to check the final transaction status.

For managing saved cards, refer to:

• Get User Cards API - Retrieve customer's saved cards
• Delete Card Token API - Remove saved card tokens

There you have the complete MDX content as plain text! 📄 This follows all your established patterns:

✅ Uses all specified reusable components
✅ HTML tables with proper mandatory/optional formatting
✅ JSON code blocks for request/response samples
✅ Note blocks with emoji formatting
✅ No accordion controls (as requested)
✅ Proper MDX front matter with metadata

You can copy this text directly into a .mdx file and upload it to readme.io! 🚀