> ## Documentation Index > Fetch the complete documentation index at: https://docs.didit.me/llms.txt > Use this file to discover all available pages before exploring further. # API de recarga de créditos > Crie um checkout Stripe e recarregue o saldo Didit: de $50 a $10,000 pelo valor nominal, nos planos Free, Growth e Scale. Recargas valem 12 meses. Prompt para recarregar créditos Copiar o prompt para a área de transferência \

\``Goal: Start a manual credit top-up by creating a hosted Stripe Checkout session. Once Stripe processes the payment, Didit's invoice.paid webhook handler credits the organization's balance.

Endpoint: POST https://verification.didit.me/v3/billing/top-up/
Auth header: x-api-key: 
Content-Type: application/json

Request body:
\- amount_in_dollars (number, REQUIRED) — USD amount to charge, from $50 MINIMUM to $10,000 MAXIMUM. The balance receives the same amount: no discount or bonus. Tax is added automatically at checkout based on billing address.
\- success_url (URI, optional) — Stripe redirects here after successful payment. Currently defaults to `https://console.didit.me`. Pass a working URL explicitly; the default host is unavailable. Append literal placeholder {CHECKOUT_SESSION_ID} if you want Stripe to substitute the session id.
\- cancel_url (URI, optional) — Stripe redirects here when the customer aborts. Currently defaults to `https://console.didit.me`. Pass a working URL explicitly; the default host is unavailable.

curl:
curl -X POST 'https://verification.didit.me/v3/billing/top-up/' \
-H 'x-api-key: YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"amount_in_dollars": 500,
"success_url": "https://yourapp.com/billing/success",
"cancel_url": "https://yourapp.com/billing/cancel"
}'

Response 200:
\{
"checkout_session_id": "cs_test_a1B2c3D4e5F6g7H8i9J0",
"checkout_session_url": "https://checkout.stripe.com/c/pay/cs_test_..."
}
Redirect the customer's browser to checkout_session_url (or hand it off to your billing admin out-of-band) to complete payment.

Full flow:
1\. POST /v3/billing/top-up/ with amount_in_dollars and explicit success_url and cancel_url values.
2\. Redirect to checkout_session_url.
3\. Customer pays on Stripe-hosted page.
4\. Stripe redirects to success_url (or cancel_url on abort).
5\. Didit receives invoice.paid webhook, increases organization balance.
6\. Poll GET /v3/billing/balance/ to confirm balance reflects the top-up.

Failure modes:
\- 400 — the body is a JSON array with one message:
\["amount_in_dollars is required."]
\["amount_in_dollars must be a number."]
\["Amount must be at least $50."]
\["Amount must be at most $10,000."]
\["You have an annual plan. Contact your account manager to top up."]  // Enterprise annual-contract orgs cannot top up: usage beyond the contract credit is invoiced as overage.
\- 401 — missing/malformed x-api-key.
\- 403 — key valid but cannot create top-up sessions for this organization.
\- 429 — rate-limited.

Notes:
\- Top-ups are available on the Free, Growth and Scale plans, from $50 to $10,000 each. They are added at face value (pay $10,000, receive $10,000; no discount or bonus), pay for every product, and last 12 months. Each check uses the month's plan credit first, then the oldest top-up.
\- Auto top-up amounts, set in Console → Billing, follow the same $50 to $10,000 range.
\- The Stripe Checkout session is single-use, but calling this endpoint repeatedly creates NEW sessions — track completion on your side via success_url/cancel_url to avoid duplicate charges.
\- When the cardholder pays with card / SEPA / US ACH, Stripe attaches the payment method with setup_future_usage=off_session so Didit can later auto-charge it for auto-refill.
\- The organization must already have a Stripe customer set up (created automatically the first time the org configures billing).

For end-to-end Didit integration, paste in the full prompt at /integration/integration-prompt.``

\
Colar em ## OpenAPI ````yaml pt-br/openapi-25.json POST /v3/billing/top-up/ openapi: 3.0.0 info: version: 3.0.0 title: Didit Verification API description: API de verificação de identidade. Autentique-se com o cabeçalho x-api-key. servers: - url: https://verification.didit.me security: [] tags: [] paths: /v3/billing/top-up/: post: tags: - Billing summary: Recarregar créditos description: >- Adiciona créditos por meio de uma sessão hospedada do Stripe Checkout (**\$50 a \$10,000** por recarga). As recargas estão disponíveis nos planos Free, Growth e Scale, são adicionadas pelo valor nominal, sem desconto nem bônus, e valem por 12 meses; contratos anuais Enterprise não podem recarregar. Redirecione o cliente para a `checkout_session_url` retornada. operationId: billing_top_up requestBody: required: true content: application/json: schema: type: object required: - amount_in_dollars properties: amount_in_dollars: type: number minimum: 50 maximum: 10000 description: >- Valor a cobrar, em USD. **Deve ser de 50 a 10,000.** O saldo recebe o mesmo valor, sem desconto nem bônus. O imposto é adicionado automaticamente no checkout com base no endereço de faturamento do cliente. success_url: type: string format: uri description: >- URL para a qual o checkout hospedado redireciona o cliente após um pagamento bem-sucedido. Atualmente, o padrão é `https://console.didit.me`. Informe explicitamente uma URL funcional; o host padrão está indisponível. Acrescente o placeholder literal `{CHECKOUT_SESSION_ID}` se quiser que o checkout hospedado o substitua pelo ID da sessão. cancel_url: type: string format: uri description: >- URL para a qual o checkout hospedado redireciona o cliente quando ele cancela ou fecha a janela do Checkout. Atualmente, o padrão é `https://console.didit.me`. Informe explicitamente uma URL funcional; o host padrão está indisponível. examples: Minimum top-up: value: amount_in_dollars: 50 Custom amount with redirects: value: amount_in_dollars: 500 success_url: https://yourapp.com/billing/top-up/success cancel_url: https://yourapp.com/billing/top-up/cancel responses: '200': description: >- Sessão de checkout hospedada criada. Redirecione o usuário para `checkout_session_url` para concluir o pagamento. content: application/json: schema: type: object required: - checkout_session_id - checkout_session_url properties: checkout_session_id: type: string description: >- Identificador da sessão de checkout hospedada (por exemplo, `cs_test_a1B2c3...`). Útil para a conciliação no lado do servidor. checkout_session_url: type: string format: uri description: >- URL da página de pagamento hospedada, de uso único. Redirecione o cliente para ela para concluir o pagamento. examples: Created: value: checkout_session_id: cs_test_a1B2c3D4e5F6g7H8i9J0 checkout_session_url: >- https://checkout.example.com/c/pay/cs_test_a1B2c3D4e5F6g7H8i9J0 '400': description: >- Payload inválido: o valor está ausente, não é um número, está abaixo do mínimo de \$50 ou acima do máximo de \$10,000, ou a organização tem um contrato anual Enterprise. O corpo do erro é um array JSON. content: application/json: examples: Missing amount: value: - amount_in_dollars is required. Not a number: value: - amount_in_dollars must be a number. Below minimum: value: - Amount must be at least $50. Above maximum: value: - Amount must be at most $10,000. Annual plan: value: - >- You have an annual plan. Contact your account manager to top up. '403': description: >- Chave de API ausente, inválida ou revogada, ou a chave não pode criar sessões de recarga para esta organização. Uma chave ausente retorna `403`; uma chave incorreta, revogada ou expirada retorna `401`. content: application/json: examples: Forbidden: value: detail: You do not have permission to perform this action. '429': description: >- Limite de requisições excedido; aguarde e tente novamente após o intervalo indicado em `Retry-After`. content: application/json: examples: Throttled: value: detail: Request was throttled. Expected available in 30 seconds. security: - ApiKeyAuth: [] x-codeSamples: - lang: curl label: curl source: |- curl -X POST 'https://verification.didit.me/v3/billing/top-up/' \ -H 'x-api-key: YOUR_API_KEY' \ -H 'Content-Type: application/json' \ -d '{ "amount_in_dollars": 500, "success_url": "https://yourapp.com/billing/success", "cancel_url": "https://yourapp.com/billing/cancel" }' - lang: python label: Python source: |- from didit import Didit # Reads DIDIT_API_KEY. client = Didit() result = client.billing.top_up( amount_in_dollars=50.0, ) print(result) - lang: javascript label: Node.js source: |- import Didit from "@didit-protocol/sdk-node"; // Reads DIDIT_API_KEY. const didit = new Didit(); const result = await didit.billing.topUp({ amount_in_dollars: 50.0, }); console.log(result); - lang: go label: Go source: "ctx := context.Background()\n// Reads DIDIT_API_KEY.\nclient := didit.NewClient()\n\nresult, err := client.Billing.TopUp(ctx, didit.BillingTopUpParams{\n\tAmountInDollars: 50.0,\n})\nif err != nil {\n\tlog.Fatal(err)\n}\nfmt.Printf(\"%+v\\n\", result)" - lang: java label: Java source: |- import me.didit.Didit; import me.didit.types.BillingTopUpParams; // Reads DIDIT_API_KEY. Didit client = new Didit(); var result = client.billing().topUp(BillingTopUpParams.builder() .amountInDollars(50.0) .build()); System.out.println(result); - lang: php label: PHP source: |- billing->topUp([ 'amount_in_dollars' => 50.0, ]); print_r($result->toArray()); - lang: ruby label: Ruby source: |- require "didit" # Reads DIDIT_API_KEY. didit = Didit::Client.new result = didit.billing.top_up(amount_in_dollars: 50.0) puts result.to_h - lang: csharp label: .NET source: |- using System; using System.Text.Json; using Didit; // Reads DIDIT_API_KEY. using var client = new DiditClient(); var result = await client.Billing.TopUpAsync(new BillingTopUpParams { AmountInDollars = 50.0, }); Console.WriteLine(JsonSerializer.Serialize(result)); components: securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: >- Chave de API da sua aplicação, em Developers -> API keys no Business Console. A chave principal tem acesso total. Uma chave nomeada pode ter escopo restrito: nenhum acesso, leitura ou escrita por recurso, limitada a alguns fluxos ou a sessões aprovadas, a uma lista de endereços IP e a uma data de validade. 401 significa que a chave está errada, revogada ou expirada; 403 significa que nenhuma chave foi enviada, que a chave não tem acesso a este recurso ou ação, ou que a requisição veio de um endereço fora da sua lista de IPs; 404 em uma rota de sessão significa que a sessão está fora dos fluxos ou status da chave. Uma chave sem acesso a mídia recebe URLs de imagem, vídeo e PDF como null, e uma chave sem permissão de escrita em sessões recebe links e tokens de sessão como null. Consulte https://docs.didit.me/console/api-keys. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.