♻️ CCE.Cash - Instant & Automatic Exchange ♻️ Fees 0.4 - 0.8%!

[Murat]

Hi,

We're integrated with the CCE OpenAPI and everything works except the order-status query. Hoping you can confirm whether the endpoint is down or whether we're calling it wrong.

Working endpoints (same API key, same nonce/timestamp/HMAC signing):

POST /openapi/order/calculate → code: 0, success
POST /openapi/order/place → code: 0, returns the order (no, query_code, deposit address)

Failing endpoint:

POST /openapi/order/query → HTTP 500, code: 2 ("Server abnormality", per your docs)
Tried the identifier as { "no": "<8-char order no>" } and as { "query_code": "<12-char code>" } — both return the same 500 / code 2.
Example order: no = G3MPF0L7, query_code = EMGCEY312D43 (placed successfully via order/place).

Since calculate and place succeed on the identical credentials and signing, this doesn't look like an auth issue (no 400009 / 701100 / 400002 errors — just the generic 500 / code 2).

Questions:

Is POST /openapi/order/query the correct endpoint to fetch an order's status? If not, what is the correct path?
What is the exact request body it expects (which field — no, query_code, or something else)?
Is the endpoint currently experiencing issues on your side?

Account / API key (public): <your X-Api-Key>

Thanks!

[CCECash]

Hi,

We're integrated with the CCE OpenAPI and everything works except the order-status query. Hoping you can confirm whether the endpoint is down or whether we're calling it wrong.

Working endpoints (same API key, same nonce/timestamp/HMAC signing):

POST /openapi/order/calculate → code: 0, success
POST /openapi/order/place → code: 0, returns the order (no, query_code, deposit address)

Failing endpoint:

POST /openapi/order/query → HTTP 500, code: 2 ("Server abnormality", per your docs)
Tried the identifier as { "no": "<8-char order no>" } and as { "query_code": "<12-char code>" } — both return the same 500 / code 2.
Example order: no = G3MPF0L7, query_code = EMGCEY312D43 (placed successfully via order/place).

Since calculate and place succeed on the identical credentials and signing, this doesn't look like an auth issue (no 400009 / 701100 / 400002 errors — just the generic 500 / code 2).

Questions:

Is POST /openapi/order/query the correct endpoint to fetch an order's status? If not, what is the correct path?
What is the exact request body it expects (which field — no, query_code, or something else)?
Is the endpoint currently experiencing issues on your side?

Account / API key (public): <your X-Api-Key>

Thanks!

Please confirm that the returned message is "Server error" and not "Internal server error".

For specific information, please contact our business team at business@cce.cash for assistance.

[SamReomo]

I was talking about the person whose ID would be stolen and used for this. That person could end up facing serious problems. There is no point in talking about the hacker because they already know they are taking a huge risk, and they commit these crimes for money while causing harm to other people.

Yes, the person whose details hackers might use for KYC can face issues from authorities, although that person is fully innocent but we all know the system doesn't understand that and the authorities will investigate the person whose KYC details were used if the crime was of high intensity.

That's why most of the times when someone doesn't share their KYC data, they're on safe end, but we all know these days completing KYC at many sites is almost mandatory, and a user has no other option than completing the KYC verification. You're right the hackers don't care about anyone else, they only want to steal money, they don't really care about anyone.

[CCECash]

We're happy to share another mini-report!

TRONSCAN data shows that the total number of TRON accounts has reached  390,318,566, officially surpassing 390 million. It is reported that the total number of accounts is the total number of activated account addresses on the TRON network. https://t.co/zbWxiU23WX

With best wishes, ♻️ CCE.Cash

[LUZUMYY]

CCECash, Will you be implementing DAI (ERC-20) on the exchange? I want to exchange BTC for DAI.

[Forsyth Jones]

I don't know, but it wouldn't be difficult for a hacker to create fake KYC data or to ask someone in one of those countries to complete the KYC process for $1,000 or $10,000. I know it sounds crazy, but it's a small thing compared to what these people are capable of.

I agree, for hackers it's not hard to create fake KYC data mostly these days when all of those things can be done using AI platforms and some prompts.

It's not that hard to edit someone's KYC data these days, but as @ZAINmalik75 said, it might create even more problems for the hackers if they try to fake KYC verification because it's not that easy to trick authorities.

I even read in some forums where they were teaching others how to create fake KYC data but I'm pretty sure most people won't take such type of risk and they'll never use the breached KYC data because they'll face legal issues by doing such a thing.

Nowadays it's very easy to get stolen IDs from forums or dark web stores to use in KYC processes at exhcnages/banks. I wonder what mechanisms they use to determine if KYC documents are genuine or fake. Besides that, to get pass video/selfie verification processes, these criminals use ai tools to create deepfakes (this was already common even before 2022). Deepfakes are widely used to bypass age verification on social medias.

That's why KYC doesn't always solve the fraud problem, criminals are always studying ways to bypass the system rules.

CCECash, Will you be implementing DAI (ERC-20) on the exchange? I want to exchange BTC for DAI.

Taking advantage of the hook, it would be interesting if they added support for the Liquid BTC network, the Liquid network, for example, is supported in the green wallet (and LN-BTC as well, why not)