---
title: "Get Customer Details"
method: POST
path: "/pws/pws_get_customer_details"
tags: ["Customer"]
---

# Get Customer Details

`POST /pws/pws_get_customer_details`

This web service gets the customers details for the given search criteria

## Request body

- PwsGetCustomerDetails
  - `api_call_unique_identifier` string, required — Unique number that must be passed at each API request. Identifier to make each API request unique
  - `client_id` integer, required — Unique identifier for the client which Paymentology will provide at outset
  - `user_id` string — User Id of the Customer who triggered the API request.
  - `remarks` string — Remarks for API request
  - `cu_fname` string — Customer First Name
  - `cu_sname` string — Customer Last Name
  - `cu_email` string — Customer Email Id
  - `cu_ref` string — Customer Reference
  - `cu_id` integer — Customer Id

## Response `200`

Successful Response

- GetCustomerDetailsResponse
  - `header` CustomerDetailsHeader
    - `error_id` integer — error id
    - `error_desc` string — error message
  - `body` CustomerDetailsBody[]
    - `company` string — Customer company
    - `cre_dt` string — Created date
    - `cu_id` integer — Customer ID
    - `cu_fname` string — Customer first name
    - `cu_sname` string — Customer last name
    - `cu_type` integer — Customer type
    - `cu_ref` string — Customer ref
    - `cu_bldg_no` string — Customer building number
    - `cu_add1` string — Customer address1
    - `cu_add2` string — Customer address2
    - `cu_pcode` string — Customer postal code
    - `cu_city` string — Customer city name
    - `cu_country` string — Customer country name
    - `cu_email` string, email — Customer email
    - `cu_mobile` string — Customer mobile number
    - `cu_pass_code` string — Customer pass code
    - `cu_lang` string — Customer native language
    - `cu_nationality` string — Customer nationality
    - `cu_gender` integer — Gender
    - `cu_alternate_email` string — Customer alternate email
    - `cu_state` string — Customer state
    - `cu_dob` string — Customer date of birth
    - `default_rule_alert_sms_severity` integer — Default rule alert sms severity
    - `default_rule_alert_email_severity` integer — Default rule alert email severity
    - `bank_customer_no` string — Bank customer number
    - `is_main_cardholder` boolean — Indicates whether the customer is the main cardholder
    - `cu_alternate_mobile` string — Customer alternate mobile
    - `cu_phone_home` string — Customer phone home
    - `cu_id_type` string — Customer id type
    - `cu_id_number` string — Customer id number
    - `credit_rating` number, double — Credit rating
    - `credit_rating_source` integer — Credit rating source
    - `display_name` string — Display name
    - `kyc_status` string — <p>KYC status</br>possible options are:</p><ul><li>1 =Awaiting first verification attempt</li> <li>2 = KYC data submitted, awaiting response</li> <li>3 = KYC successful</li> <li>4 = KYC unsuccessful</li> <li>5 = KYC verification attempts expired</li> <li>6 = KYC not possible (permeant)</li> <li>7=Awaiting KYC re-verification</li></ul>
    - `kyc_status_details` string — <p>KYC status details.</br>user defined text to describe the reason of status</p>
    - `kyc_ext_reference` string — External reference id provided by KYC provider to refer last KYC attempt
    - `key_provider_name` string — <p>Key provider name.</br>possible options are:</p><ul><li>1 = Jumio (supported for now)</li> <li>2 = IDNow</li> <li>3 = Sumsub</li></ul>
    - `kyc_attempt_count` integer — Counter which is decremented with each KYC attempt
    - `kyc_attempt_date` string — Date with timestamp . It will contain the value when last KYC attempt was made

## Other responses

- `404` — Webservices does not exist
- `500` — Internal Server error

---

[API](https://skmtc.net/paymentology/apis/payapi-docs.md) · [All operations](https://skmtc.net/paymentology/apis/payapi-docs/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/paymentology/payapi-docs/revisions/a675891b0365/schema)