PSP

PSP API – Check Transaction Status and Initiate Onramp Requests

get-psp-status-by-cid

Checks the status of an onramp transaction using the transaction ID (cid).

SecurityAuthorization

Request

path Parameters

cid

required

string

The transaction ID used to track the PSP request.
This ID is usually provided in the widget URL as transactionID,
and refers to the internal transaction ID in Crymbo's system.

Example: 1234

Responses

200
Status successfully retrieved.

404
Transaction not found.

get/v3/psp/onramp/cid/{cid}

Response samples

200
404

application/json

{"status": "PENDING_PAYMENT" }

Get onramp transaction details by CID

Retrieves the details and status of an onramp transaction using the transaction ID (cid).

Access rules:

Merchant tokens can only access transactions that belong to their own merchant.

Admin tokens (customer-type users) can access any transaction by CID.

This endpoint requires a valid Bearer token.

Request

path Parameters

cid

required

string

The transaction ID used to track the PSP request.

This ID is usually provided by the widget as transactionID, and refers to the internal transaction ID in Crymbo's system.

Example: 1764072382462

Responses

200
Transaction successfully retrieved.

401
Unauthorized – missing or invalid Bearer token.

403
Forbidden – the token is authenticated but does not have permission to access this resource.

404
Transaction not found.

This can happen if:

The CID does not exist, or

For merchant tokens: the CID does not belong to the merchant.

get/psp/onramp/merchant/cid/{cid}

Response samples

200
401
403
404

application/json

{"cid": "1764072382462", "status": "PENDING_PAYMENT", "updated_at": "2025-11-25T12:11:28.000000Z", "spendAmount": "100", "spendCurrency": "EUR", "external_payment_id": "69259cef38374dca7863e983" }

➔ Next to Orders