입금 및 잔액

CCPayment deposits and Solucaptcha account balance, in USD.

All your keys share the available balance: confirmed deposits minus recorded solver usage. balanceCents reports deposits; balanceMicrocents reports available API funds (divide by 100000 for USD). Current billing occurs at creation; failure refunds are not implemented yet. Withdrawals are not available.

How to deposit

1. Sign in with a verified email and open Credits.
2. Choose US$5 to US$1,000. Checkout expires after 1 hour.
3. Choose the correct cryptocurrency and network on CCPayment and follow checkout instructions.
4. Wait for confirmation. Returning to the site or refreshing the page does not prove payment.

Automatic credit equals the requested USD amount, with no extra credit for overpayments. CCPayment processing fees are paid by the site; wallet/network fees are paid separately by the customer. Do not send on the wrong network or reuse expired checkout.

States and confirmation

status	Meaning
creating	Creating checkout
pending	Waiting for payment
processing	Waiting for confirmation
partial	Received amount is still insufficient
expired	Checkout expired
review	Late payment, risk or mismatch: support required
credited	Credit confirmed exactly once

The server verifies the webhook signature and rechecks the order with CCPayment. Only confirmed, non-risk transactions with the correct currency/price, received before expiry and sufficient total credit automatically. Partial payments await completion; overpayments, late payments and mismatches require support review.

History is persisted and reconciliation continues without an open browser, up to 7 days after expiry. The interface polls every 30 seconds; manual refresh is limited to every 15 seconds per order.

Portal routes — account session

Base: https://solucaptcha.com. Requires a verified-email account session, not clientKey. Account POSTs require JSON and a valid origin. Webhook is a separate route exclusively for signed provider notifications.

Endpoint	Contract
GET /api/portal/payments	enabled, currency, balanceCents, minimumCents, maximumCents, orders (30)
POST /api/portal/payments/create	{"amount":"10.00","requestId":"UUID","locale":"pt-br"}
POST /api/portal/payments/orders/:id/refresh	{}
POST /api/portal/payments/webhook	CCPayment: signature required, no session

{
  "enabled": true,
  "currency": "USD",
  "balanceCents": 0,
  "balanceMicrocents": 0,
  "apiEnabled": true,
  "minimumCents": 500,
  "maximumCents": 100000,
  "orders": []
}

Illustrative example. balanceCents is an integer: 1000 means US$10.00 in deposits. balanceMicrocents reports available API funds: divide by 100000 for USD. Creation returns id, amountCents, status, checkoutUrl, canPay and millisecond timestamps. Reuse the same requestId UUID when retrying the same amount and logical attempt; never grant credit from the browser.

Errors and security

HTTP 400: INVALID_INPUT / PAYMENT_AMOUNT_INVALID; 401: UNAUTHENTICATED; 403: FORBIDDEN; 404: NOT_FOUND; 429: RATE_LIMITED; 503: PAYMENTS_UNAVAILABLE / PAYMENT_PROVIDER_UNAVAILABLE.

These routes use HTTP status and code, not the solver's errorId. Invalid webhook signatures return 401 INVALID_SIGNATURE. Processed notifications return text Success; signed ActivateWebhookURL activation returns JSON {"msg":"Success"}. Never expose CCPayment secrets in browsers, examples or support tickets.

Verification: unpaid checkout, official webhook test and automated tests passed. No real deposit has yet verified end-to-end financial settlement.

Reviewed on 2026-10-11 against docs/especificacao-api.md. Site availability and engine validation are separate statuses.