> For the complete documentation index, see [llms.txt](https://doc.ecomm.api.tietoevry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.ecomm.api.tietoevry.com/payment-method/card-payments/partial-authorization-for-card-payments.md).

# Partial Authorization for Card Payments

Enable a merchant to recover otherwise-declined card transactions by automatically capturing the maximum available amount on the customer’s card and allowing the remainder to be paid with an alternate method.

Partial authorization lets you rescue transactions that would otherwise be rejected for “insufficient funds.” When a customer’s card doesn’t have enough balance to cover the full amount, your gateway simply approves – and captures – whatever funds *are* available, then asks the shopper to pay the small remainder with another card or payment method.

## How it feels in practice

1. Customer taps “Pay.” - They expect the purchase to go through, but their card is short by a few dollars.
2. Gateway replies with a partial approval. - Instead of a red-letter “Declined,” the POS or checkout page shows: *“141.00 EUR approved. 9.00 EUR still due.”*
3. Shopper chooses a second tender. - They add a different card, wallet, or cash to clear the balance.
4. Sale completed, smile preserved. - You collect the full 150 EUR, your approval metrics stay healthy, and the customer avoids the frustration (and embarrassment) of a decline.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.ecomm.api.tietoevry.com/payment-method/card-payments/partial-authorization-for-card-payments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.