> 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-receiver-payment-methods.md).

# Testing receiver payment methods

Wire Transfer is currently the only payment method with a `receiver` [authentication flow](/commerce-api/payments/sources.md#authentication-flow) that Digital River [supports in our testing environment](#supported-payment-methods-in-test-environment).

{% hint style="warning" %}
You should coordinate with your support team when testing wire transfers. They can provide instructions on how to move your orders into a completed state.
{% endhint %}

## Success scenarios

Use the [create source method](/commerce-api/resources/reference/digital-river-payment-objects.md#create-source-error-object) for receiver-type payment methods to provide success scenario test data. Once you've done this, you should receive a Source in a `pending_funds` state. You can then use the Source to complete your Checkout or Order.

## Error scenarios

First, identify the error scenario you would like to test against from the following table. When [creating a source](/commerce-api/shopper-apis/cart/payment-sessions.md#creating-a-source-with-payment-sessions), set the `lastName` parameter in the [Owner object](/commerce-api/payments/payments-solutions/digitalriver.js/payment-methods/common-payment-objects.md#owner-object) to the value you expect to trigger the scenario.

| Scenario                   | Description                                                                                                                                  |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| `lastName` parameter       | Expected result                                                                                                                              |
| SourceCreationFail         | A Source is not created. The `state` of the Source is `failed`.                                                                              |
| SourceFailWithDelay        | A Source is successfully created but the Charge fails. The `state` of the Charge is `failed`.                                                |
| RefundFailWhileCreation    | Both a Source and the Charge are successfully created but refunds against the Charge fail. The `state` of the Refund is `failed`.            |
| RefundFailAfterPaymentInfo | Both a Source and the Charge are successfully created, and a Refund request against the Charge is successful but ultimately fails to refund. |


---

# 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-receiver-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.