> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/commerce-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/commerce-api/payments/testing-scenarios/testing-standard-payment-methods.md).

# Testing standard payment methods

The payment methods with a `standard` [authentication flow](/commerce-api/payments/sources.md#authentication-flow) that Digital River currently supports in our testing environment are Apple Pay, Credit Cards, and Google Pay. 

Before accepting live payments, you can use the card numbers in this section to test against [success](#success-scenarios-2) and [error](#error-scenarios-2) scenarios. These numbers are only valid in our testing environment. They do not create a real charge or result in a transfer of funds.

To conduct the testing, [create a source](https://www.digitalriver.com/docs/commerce-admin-api/#tag/Source/operation/createSources), and use the appropriate data to set the parameters of the `creditCard` hash table.


---

# 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.digitalriver.com/commerce-api/payments/testing-scenarios/testing-standard-payment-methods.md?ask=<question>&goal=<endgoal>
```

`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.