> 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/codapay/direct-api-integration/direct-api-integration-for-cards/getting-started/sandbox-testing-instructions.md).

# Sandbox Testing Instructions

### Testing use cases card

| Use Case                                                                                                    | Test Card           |
| ----------------------------------------------------------------------------------------------------------- | ------------------- |
| <p>Test case 1: Successful</p><p>Response with no 3DS</p>                                                   | 4242 4242 4242 4242 |
| <p>Test case 2: Successful</p><p>Response with 3DS (Form</p><p>Flow)</p>                                    | 4000 0084 0560 0003 |
| <p>Test case 3: Success</p><p>Response with 3DS (Redirect</p><p>flow)</p>                                   | 4000 0084 0560 0003 |
| <p>Test case 4: Failed response</p><p>with “failed” error with</p><p>payment\_declined error</p><p>code</p> | 4000 0084 0560 0003 |

### Testing the notifications

In order to test the notifications, specify a working partner\_webhook\_url and you will receive all possible notifications for the use case on that url. If you want to test the capture request notification, you will also need toprovide a pre\_capture\_ack\_url.


---

# 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.coda.co/codapay/direct-api-integration/direct-api-integration-for-cards/getting-started/sandbox-testing-instructions.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.