Skip to main content
POST
/
payment-instrument
Create Payment Instrument
curl --request POST \
  --url https://uat-api.clinkbill.com/api/payment-instrument \
  --header 'Content-Type: application/json' \
  --header 'X-API-KEY: <api-key>' \
  --header 'X-Timestamp: <api-key>' \
  --data '
{
  "customerId": "cus_xxxxx",
  "paymentInstrumentType": "CASHAPP",
  "customerName": "Alice Example",
  "metadata": {
    "source": "checkout"
  }
}
'
{
  "code": 200,
  "msg": "success",
  "data": {
    "id": "<string>",
    "customerId": "<string>",
    "card": {
      "last4": "<string>",
      "name": "<string>",
      "expiryYear": "<string>",
      "expiryMonth": "<string>",
      "scheme": "<string>",
      "funding": "<string>",
      "issuerRegion": "<string>",
      "issuerBank": "<string>",
      "billingAddress": {
        "city": "<string>",
        "country": "<string>",
        "line1": "<string>",
        "line2": "<string>",
        "postalCode": "<string>",
        "state": "<string>"
      }
    },
    "wallet": {
      "accountTag": "<string>"
    },
    "created": 123
  }
}

Documentation Index

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

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

Authorizations

X-API-KEY
string
header
required

Your secret API key obtained from the Clink dashboard (Developers section)

X-Timestamp
string
header
required

Current timestamp in milliseconds since Unix epoch (required for request signing)

Body

application/json

Parameters required to create a payment instrument by API. Provide at least one of customerId, customerEmail, or referenceCustomerId.

paymentInstrumentType
enum<string>
required

Payment instrument type. Supported values are uppercase. Card and browser-wallet payment instruments are not supported by this API.

Available options:
ALIPAY,
CASHAPP,
GCASH,
KAKAO,
PROMPTPAY,
QRIS,
TNG,
WECHAT
customerId
string

Existing customer ID. At least one customer identifier is required.

customerEmail
string

Customer email. Used to resolve or create a customer when customerId is not provided.

referenceCustomerId
string

Merchant-side customer ID used to resolve, create, or bind a customer.

customerName
string

Display name of the customer.

subPaymentMethodType
string

Optional sub payment method type.

metadata
object

Merchant metadata. Values must be strings.

Response

Payment instrument created successfully

code
integer<int32>

Response status code, 200 when success

Example:

200

msg
string

Brief description of what happened, 'success' when happy case

Example:

"success"

data
object

Payment instrument information returned by the API.