How do I process a refund in Worldline?

To find your API access code in Worldline, follow the steps given below:

• Open your Worldline account
• Go to the 'Configuration' section
• Navigate to 'Technical Information'
• Click on 'API settings'
• Here you will find your 'Direct API Key' which is basically your API access code
• If a key doesn't already exist, click 'Generate' to create a new key.

To assign user permissions in Worldline, you can use the User Manager in your Worldline account menu. To do so follow the steps given below:

• Open your Worldline account
• Navigate to the ‘User manager’ section
• Click on Configuration
• Choose Users
• Hit ‘New User’
• Input the required details
• Choose a profile
• Specify the access rights
• Hit ‘Create’

To create a Checkout link in Worldline, follow the steps given below:

• Open your Worldline Merchant Portal
• Go to the 'Payment Links' section
• Utilize the link builder to input the required payment details
• Create a unique payment link that you can send to your customers

To find a transaction report in Worldline, follow the steps given below:

• Open the Worldline Back Office
• Click on Operations
• Select ‘View transactions’ or ‘Financial history’
• Utilize the search bar to find your transaction
• Press on the ‘Advanced Selection Criteria’ option to add more search criteria

If your ERP handles UPI payments for capital market investments, tagging the right purpose code is super important — not just for compliance but also for making audits painless later. NPCI and your bank partners require that every UPI collection carry a purpose or merchant category tag (like INSURANCE_PREMIUM, CAPITAL_MARKET_INVESTMENT, etc.) so they can classify transactions properly during settlement and reporting.
Here’s a simple way to get this right:

• Add a purpose code field in your UPI transaction schema.

When the ERP creates a UPI collect request (/upi/collect or similar), include a key like purpose_code or txnPurpose in the payload. For capital market flows, this should map to NPCI’s defined code — usually something like CAPITAL_MARKET_INVESTMENT or CAPMKT_INV.
Example:
{
txn_id: INV12345,
amount: 250000,
payer_vpa: user@upi,
purpose_code: CAPMKT_INV,
remarks: Equity Purchase via Broker XYZ
}

• Use metadata rules to auto-tag transactions.

Don’t rely on manual tagging. Have your ERP detect when the ledger account, invoice type, or customer category = brokerage, mutual fund, or demat account funding, and then automatically assign the correct purpose code.
For example, any payment linked to GL accounts like Capital Market Receivables or Broker Margin Deposits should auto-inherit CAPMKT_INV.

• Validate purpose codes before posting.

Your ERP should block any UPI request that doesn’t have a valid code this ensures you never send untagged payments that cause reconciliation pain later.

• Store the code for audits.

When the UPI payment settles, store the purpose_code in your transaction and ledger tables so your auditors can filter by it during quarterly reviews. It’ll make your compliance reporting way cleaner.

• Sync with your payment gateway or PSP’s mapping.

Some gateways (like Razorpay or Cashfree) already have NPCI purpose code enums baked in. Make sure your ERP’s code names match theirs otherwise the tag may not pass through to the UPI network.

• Optional: include the code in the GST e-invoice or reconciliation exports.

Add a field like UPI Purpose in your audit or invoice exports. When auditors check high-value inflows, they can immediately see whether it was a capital market transaction no manual tracing needed.