Skip to main content
Users may occasionally encounter unpaid charging sessions. This occasionally occurs if the pre-authorization amount is insufficient to cover the final cost or if a remote charge fails due to reasons such as insufficient funds or a requirement for 3D Secure (3DS) user confirmation. In these cases, the platform will block specific operations and return a 400 ("status": "unpaid_debts") or 402 status code. Blocked actions include:
  • Starting a new charging session.
  • Deleting a payment method.
  • Soft-deleting a user account.
{
  "results": [
    {
      "session_id": "68199362-787c-4fe0-ae28-dae0f1da227e",
      "client_secret": "pi_1THkgXHtgZxQ1KXxOhLbYQKU_secret_UGHFCX0iihdboXkwx4QfiR9V2ma55vk",
      "amount": "12.85",
      "currency": "eur"
    }
  ]
}

​
1. Retrieve unpaid sessions

You can retrieve details regarding unpaid sessions via a direct API request to the debts endpoint: 
curl -X GET "https://connect.cariqa.com/api/v1/users/9405cf8c-8375-4373-b4d3-b61f9a0c01eb/debts/" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json"
Response: 
{
  "count": 1,
  "next": null,
  "previous": null,
  "results": [
    {
      "session_id": "68199362-787c-4fe0-ae28-dae0f1da227e",
      "client_secret": "pi_1THkgXHtgZxQ1KXxOhLbYQKU_secret_UGHFCX0iihdboXkwx4QfiR9V2ma55vk",
      "amount": "12.85",
      "currency": "eur"
    }
  ]
}

​
2. Client-Side Payment Confirmation

To resolve unpaid charging sessions, initialize the Stripe SDK on the client using the publishable key provided during onboarding. You must complete the payment manually to satisfy bank-mandated 3DS operations. Provide the payment intent client secret and payment method ID to the respective SDK methods: Android: confirmPayment() iOS: confirmPaymentIntent()
The SDK will automatically redirect the user to their bank issuer’s portal to complete the authentication process. It also may skip 3DS and complete payment immediately.

​
Failed Pre-Authorization

If the backend fails to pre-authorize funds during a “start charging” request, the client-side must confirm the transaction manually. Capture the payment_intent_client_secret from the 402 error response of the failed request to proceed: Check this Error handling Guide for more details