PApaymentology
Ledger API - Customers

Create customer (REST)

<ul> <li class="docBullet">REST-style endpoint for the same operation as <a href="https://developer.paymentology.com/bankinglive/reference/v3_pws_create_customer">Create customer (PWS)</a>. Same request body and response envelope.</li> </ul>
post/pty/customer/v1/customers

Request

  • Base URL
    https://api.uat.paymentology.com
  • URL
    https://api.uat.paymentology.com/pty/customer/v1/customers
  • Auth
    HTTP bearer

Request body

api_call_unique_identifierstring required

Unique number that must be passed at each API request. Identifier to make each API request unique

client_idinteger required

Unique identifier for the client which Paymentology will provide at outset

cu_fnamestring required

Customer First Name

cu_mobilestring required

Customer Mobile Number. Format i.e 00 (country code) phone number or + (country code) phone number.

cu_snamestring required

Customer Last Name

user_idstring

User Id of the Customer who triggered the API request.

remarksstring

Remarks for API request

cu_titlestring

Customer title

companystring

Customer Company

cu_refstring

Customer Ref

cu_bldg_nostring

Customer building number

cu_add1string

Customer address1

cu_add2string

Customer address2

cu_add3string

Customer address3

cu_pcodestring

Customer PCode

cu_citystring

Customer City Name

cu_countrystring

Customer Country Name

cu_emailstring

Customer Email

cu_pass_codestring

Customer Pass Code

cu_langstring

Customer Native Language

cu_nationalitystring

Customer Nationality

cu_gender1 | 2 | 3

Customer Gender. Possible values are: 1=Male 2=Female 3=Other

cu_alternate_emailstring

Customer Alternate Email

cu_statestring

Customer State

cu_dobstring

Customer Date of Birth

default_rule_alert_sms_severityinteger

Default rule alert sms severity

default_rule_alert_email_severityinteger

Default rule alert email severity

bank_customer_nostring

Bank Customer Number

cu_alternate_mobilestring

Customer Alternate Mobile

cu_phone_homestring

Customer Phone Home

cu_id_typestring

Customer Id Type

cu_id_numberstring

Customer id number can be driving licence,citizenship number

credit_ratingnumber double

Credit rating

credit_rating_sourceinteger

Credit rating source

display_namestring

Display Name

kyc_status'1' | '2' | '3' | '4' | '5' | '6' | '7'

KYC status possible options are: 1=Awaiting first verification attempt 2=KYC data submitted, Awaiting Response 3=KYC successful 4=KYC unsuccessful 5=KYC verification attempts expired 6=KYC not possible (permeant) 7=Awaiting KYC re-verification

kyc_status_detailsstring

KYC status details. User defined text to describe the reason of status

kyc_ext_referencestring

External reference id provided by KYC provider to refer last KYC attempt

key_provider_name'1' | '2' | '3'

Key provider name. Possible options are: 1=Jumio (supported for now) 2=IDNow 3=Sumsub

kyc_attempt_countinteger

Counter which is decremented with each KYC attempt

kyc_attempt_datestring

Date with timestamp. It will contain the value when last KYC attempt was made

is_main_cardholderboolean

Indicates if the customer to be created is main cardholder or not. The possible values are true or false.

Response

Request processed. Check header.error_id: 0 means success. Any other value is a business error, reported with HTTP 200 and an empty body. Common codes: 992 (invalid account id), 993 (invalid card token), 995 (validation failed), 1043 (account does not belong to the client), 1055 (invalid program_code), 1531 (invalid customer id).

Example response

{
  "header": {
    "error_desc": "success"
  },
  "body": {
    "customer_id": 607748
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.