Skip to main content
POST
/
pg
/
payments
/
{uid}
/
upload-verification-details
Upload Payment Verification Details
curl --request POST \
  --url https://api-pacb-uat.eximpe.com/pg/payments/{uid}/upload-verification-details/ \
  --header 'Content-Type: application/json' \
  --header 'X-API-Version: <api-key>' \
  --header 'X-Client-ID: <api-key>' \
  --header 'X-Client-Secret: <api-key>' \
  --header 'X-Merchant-ID: <api-key>' \
  --data '
{
  "buyer_name": "John Doe",
  "type_of_goods": "GOODS",
  "product_description": "Electronics and accessories",
  "buyer_address": "123 Main Street, City, State",
  "invoice_number": "INV-2025-001",
  "buyer_postal_code": "12345",
  "hs_code": "8517.12.00"
}
'
{
  "success": true,
  "message": "Payment verification details uploaded successfully; order updated.",
  "data": {
    "uploaded_documents": [
      {
        "doc_name": "importer_name",
        "doc_type": "VALUE",
        "doc_status": "VERIFIED",
        "remarks": null,
        "added_on": null,
        "last_updated_on": null
      }
    ],
    "missing_documents": [],
    "errors": []
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.eximpe.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

The Upload Payment Verification Details endpoint allows you to upload payment verification details for a payment. This updates the associated order with the provided information and uploads the verification details to the payment gateway. Use this endpoint when you receive a PAYMENT_DETAILS_MISSING webhook and need to supply missing verification fields.

​
Test Data

When testing this API in the sandbox environment, you must use the following specific test values for the API to work correctly:
  • buyer_name: John
  • buyer_postal_code: 560034
  • product_description: This is a test product for test purpose.

📚 Test Data Reference

View all test data – Complete test data guide for sandbox testing.

Authorizations

​
X-Client-ID
string
header
required

Client Application ID - Your unique application identifier used to authenticate API requests. You can find your Client ID in the Developer Settings section of the merchant dashboard.

​
X-Client-Secret
string
header
required

Client Secret Key - Your secret key used alongside the Client ID for secure authentication. Keep this confidential and never expose it in client-side code. Available in the Developer Settings section of the merchant dashboard.

​
X-Merchant-ID
string
header
required

Merchant Identifier - The unique ID for the merchant account. This is required for PSP (Payment Service Provider) merchants who manage multiple merchant accounts. You can find merchant IDs in the Merchant Management section of the dashboard.

​
X-API-Version
string
header
required

API Version - Specifies which version of the API to use (e.g., '1.X.X', '2.X.X', or '3.X.X'). This header allows you to control which API version your integration uses. Default version information is available in the Developer Settings.

Path Parameters

​
uid
string
required

UID of the payment for which to upload verification details.

Body

application/json
​
buyer_name
string
required

Name of the buyer/importer.

Maximum string length: 255
​
type_of_goods
enum<string>
required

Type of goods.

Available options:
GOODS,
PHYSICAL_GOODS,
DIGITAL_GOODS,
SERVICE
​
product_description
string
required

Description of the product/goods.

​
buyer_address
string
required

Buyer's address.

​
invoice_number
string
required

Invoice number.

Maximum string length: 255
​
buyer_postal_code
string
required

Buyer's postal/ZIP code.

Maximum string length: 10
​
hs_code
string

HS code. Required when type_of_goods is GOODS, PHYSICAL_GOODS, or DIGITAL_GOODS; optional for SERVICE.

Maximum string length: 30

Response

Payment verification details uploaded successfully; order updated.

​
success
boolean
​
message
string
​
data
object