API Reference
Client Login
  1. LEDGER API
  2. Customers

Update customer (REST)

patch
https://api.uat.paymentology.com/pty/customer/v1/customers/
  • REST-style endpoint for the same operation as Update customer (PWS). Same request fields and response envelope.
  • The customer is identified by customer_id in the path instead of cu_id in the body.
Path Params
int64
required
Body Params
string
required
length between 1 and 40

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

int32
required
≥ 1

Unique identifier for the client which Paymentology will provide at outset

string
length between 0 and 50

User Id of the Customer who triggered the API request.

string
length between 0 and 200

Remarks for API request

string

Customer title

string
^(?!\d+$).+

Customer First Name

string
^(?!\d+$).+

Customer Last Name

string

Customer Company

int32

Customer Type

string
length between 0 and 50

Customer Ref

string
length between 0 and 10

Customer building number

string
length between 0 and 100

Customer address1

string
length between 0 and 100

Customer address2

string

Customer Address3

string

Customer Postal Code

string

Customer City Name

string

Customer Country Name

string

Customer Email

string
^\\+[0-9]{1,15}$

Customer Mobile Number must be formatted as + followed by up to 15 digits, without spaces, dashes, or other characters.

string

Customer Pass Code

string

Customer Native Language

string

Customer Nationality

int32
enum

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

Allowed:
string

Customer Alternate Email

string

Customer State

string

Customer Date of Birth

int32

Default rule alert sms severity

int32

Default rule alert email severity

string

Bank Customer Number

string
^\\+[0-9]{1,15}$

Customer Alternate Mobile must be formatted as + followed by up to 15 digits, without spaces, dashes, or other characters.

string
^\\+[0-9]{1,15}$

Customer Phone Home must be formatted as + followed by up to 15 digits, without spaces, dashes, or other characters.

string

Customer Id Type

string
length between 0 and 100

Customer id number can be driving licence,citizenship number

double

Credit rating

int32

Credit rating source

string

Display Name

string
enum

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

Allowed:
string
length between 0 and 1000

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

string

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

string
enum

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

Allowed:
int32

Counter which is decremented with each KYC attempt

string

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

boolean

Indicates whether the customer is the main cardholder

Responses

401

Missing or invalid access token. Empty body.

403

Access token rejected by the API gateway (for example, expired).

Updated 1 day ago

Did this page help you?
Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 1 day ago

Did this page help you?