Welcome to the Payment API Collection. This collection provides a streamlined interface for interacting with our payment processing API, with special focus on subscription management. A powerful pre-request script handles template management, request formatting, and signature generation automatically.
\nAutomatic Template Application: Pre-configured subscription templates for different scenarios
\nRequest Signing: Automatic SHA-256 signature generation
\nID Generation: Optional automatic generation of transaction and customer IDs
\nField Formatting: Automatic stringification of complex objects
\nEnvironment Integration: Seamless use of environment variables for credentials and URLs
\nBefore making any requests, create an environment with these variables:
\nFor advanced customization, you can set these collection variables:
\nFor subscription operations, you can customize these templates:
\nThe script automatically generates IDs when autoGenerateIds is set to true:
merchantTxnId will be generated as a UUID
merchantCustId will be generated in format CustId-XXXX-XXXX
For requests where you need to use your own merchantCustId values while still auto-generating merchantTxnId, you can:
Add a header: Include X-Skip-MerchantCustId-Generation header (with any value) in your request
Add a body flag: Include \"skipMerchantCustIdGeneration\": true in your request body (this flag will be automatically removed before sending)
This is useful for:
\nCustomer update operations where you need to use an existing customer ID
\nRequests where you want to manually specify the customer ID
\nTesting specific customer ID formats or values
\nTo skip request signing for a specific request:
\nAdd header X-Skip-Signing with any value, or
Add \"sign\": \"skip_sign\" to your request body
To stringify additional fields, set fieldsToStringify collection variable:
CopybillingInformation,customField1,customField2\n\n\"Invalid signature\" error:
\nVerify your SECRET environment variable is correct
Check that request signing is enabled
\nTemplate not applying:
\nVerify template variables are properly formatted JSON strings
\nEnable debugMode to see detailed logs
Missing required fields:
\ndebugMode is enabled, check console for validation warningsCustomer ID issues:
\nIf you need to use your own customer IDs, use the X-Skip-MerchantCustId-Generation header
Check if autoGenerateIds is enabled when you expect IDs to be generated
Set collection variable debugMode to true
Open Postman Console (View > Show Postman Console)
\nSend your request
\nReview the detailed logs showing template application and request processing
\na control flag that instructs the pre-request script to bypass automatic generation of the merchantCustId field while still allowing other automated processing (such as merchantTxnId generation and request signing) to proceed normally.
\n","type":"text"}],"body":{"mode":"raw","raw":"{\n \"appId\": \"{{APPID}}\",\n \"merchantNo\": \"{{MERCHANT-NO}}\",\n \"merchantCustId\": \"CustId-PC32-PHRO\",\n \"subProductType\": \"TOKEN\",\n \"sign\": null\n}","options":{"raw":{"language":"json"}}},"url":"{{baseUrl}}/v1/txn/queryTokenList","description":"Fetches stored tokenization records for a specific customer using their merchant-assigned customer ID. This endpoint returns all active payment tokens associated with the customer, including masked card details and token status information.
\n","auth":{"type":"apikey","apikey":{"key":"The settlement currency code for the requested file (e.g., USD).
\n","type":"text"},{"key":"date","value":"20250221","description":"Target settlement date in YYYYMMDD format.
\n","type":"text"},{"key":"merchantNo","value":"{{MERCHANT-NO}}","description":"Your merchant identifier for authentication and data filtering.
\n","type":"text"},{"key":"sign","value":"","type":"text"},{"key":"Content-Type","value":"application/octet-stream","description":"Defines response format as downloadable binary data.
\n","type":"text"}],"url":"{{baseUrl}}/v1/settlementFile/download","description":"StartFragmentThis API allows merchants to download settlement files containing transaction reconciliation data for a specified date and currency. Files are delivered in binary format for direct processing or import into accounting systems.EndFragment
\n","auth":{"type":"apikey","apikey":{"key":"