> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/changelog/2024-codapay-changelog/card-payments-price-point-adjustments.md). # Card Payments Price Point Adjustments Please be informed that the price point has been adjusted for the payment channel below: ### Card Payments Argentina **Previous Price Point:** Minimum: ARS 400 Maximum: ARS 95,000 **New Price Point 🆕** Minimum Price Point: ARS 400 Maximum Price Point: ARS 500,000 *** ### Card Payments Paraguay **Previous Price Point:** Minimum: PYG 3,500 Maximum: PYG 999,999 **New Price Point 🆕** Minimum Price Point: PYG 3,500 Maximum Price Point: PYG 4,000,000 *** ### Card Payments Laos **Previous Price Point:** Minimum: LAK 3,186 Maximum: LAK 999,999.99 **New Price Point 🆕** Minimum Price Point: LAK 8,500 Maximum Price Point: LAK 999,999.99 Thank you for using our services. We hope these updates enhance your payment experience. If you have any questions or concerns, please don't hesitate to contact our Support team. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.coda.co/changelog/2024-codapay-changelog/card-payments-price-point-adjustments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.