Update Merchant
Live Partners API
https://partners-api.service.cedar.money/bpapi
Live Partners API
https://partners-api.service.cedar.money/bpapi
PUT
https://partners-api.service.cedar.money/bpapi
Description
Sandbox-Only Behavior: Simulate kycStatus
Updates
kycStatus
field by using a special pattern in the localRegNumber
field.How it Works
localRegNumber
value ends with a pipe character (|
) followed by a valid KYC status, the merchant's kycStatus
will be set to that value regardless of other verification steps. A webhook event will also be triggered to reflect the update.Example
kycStatus
to VALID
:{
"localRegNumber": "123456789|VALID"
}
kycStatus
to VALID
and send the appropriate webhook notification.Supported kycStatus
Values
Code | Display Name | Notes |
---|---|---|
NEW | New | Recently created and not yet processed – can submit onboarding |
PENDING | Pending | Awaiting verification or further action – can submit onboarding |
PENDING_REVIEW | Pending Review | Waiting for manual review |
UNDER_REVIEW | Under Review | Currently being examined for verification |
ACTION_NEEDED | Action Needed | Requires user or system intervention – can submit onboarding |
VALID | Valid | Successfully verified and approved – can initiate transactions |
FLAGGED | Flagged | Marked for potential issues or concerns |
ABANDONED | Abandoned | Left incomplete or not pursued further |
ℹ️ This behavior is available only in sandbox environments for testing and development purposes. In production, the kycStatus
is managed through the proper verification pipeline.
Request
Path Params
id
integer
required
Example:
1
Header Params
x-api-key
string
required
Example:
CEDAR_DEV_api_key_b0ab5b29-caa7-4fa6-9f94-51dbc145e9ed
x-api-secret
string
required
Example:
CEDAR_DEV_api_secret_YtGc1iMIdVaSlE3yeBxS3Y6RY3j933s3YdTloLZjY9ar7T5vuVTGPovoRplo7PSZbYg2RLV9yJ3ZT7BctcxxPSR5pQpEMndj3EJB
Body Params application/json
Request samples
Responses
Modified at 2025-06-01 08:26:41