> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/resources/solution-briefs/2checkout-payment-methods-datasheet.md).
# 2Checkout Payment Methods Datasheet
Last updated: 09-Sep-2021
Use local payment methods in conjunction with localization best practices to simplify payments for your international shoppers. But do so keeping in mind the full customer journey from acquisition and conversion through to activation and ultimately retention. Domestic [payment methods](http://www.2checkout.com/lp/avangate-payment-methods-datasheet.html) are a critical resource to optimize the key stages of transactional processes across the entire customer lifecycle. They fit in the complex puzzle of challenges that includes language and cultural differences, multiple currencies, taxation, user behavior particularities, device and form factor preferences, risk mitigation, legal and regulatory compliance, etc.
Just keep in mind that those so-called “alternative payment methods” can make international customers feel sufficiently “at home” in your shopping cart to result in successful purchases.
[](http://www.2checkout.com/lp/avangate-payment-methods-datasheet.html)
{% hint style="info" %}
Need help?
If you didn’t find the answer you are looking for in our documentation, you can contact our [Support](https://verifone.cloud/support) teams for more information. If you have a technical issue or question, please contact us. We are happy to help.
Get in touch
{% endhint %}
{% hint style="info" %}
Not yet a Verifone customer?
We’ll help you choose the right payment solution for your business, wherever you want to sell, in-person or online. Our team of experts will happily discuss your needs.
Contact sales Get Started
{% endhint %}
---
# 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://docs.2checkout.com/resources/solution-briefs/2checkout-payment-methods-datasheet.md?ask=&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.