# Testing Overview

## Testing integration <a href="#testing-integration" id="testing-integration"></a>

After API, PayForm, or widget integration, it is important to login to our Virtual Terminal and make sure the transactions and consents appear correct. The Number Support Team can provide you with Virtual Terminal credentials.

{% hint style="info" %}
An example user name for the Virtual Terminal can look like this: **VT4914533**
{% endhint %}

For more information about the Virtual Terminal, see the [Virtual Terminal](/documentation/getting-started/integration-options/virtual-terminal.md) guide. You can access Virtual Terminal using the link below.

<figure><img src="/files/iVFmK2Cu2IeNgKC8IAxq" alt=""><figcaption></figcaption></figure>

***

## Verifying transactions <a href="#verifying-transactions" id="verifying-transactions"></a>

Once logged in, expand the *Transactions* tab in the navigation on the left, then click on *Search*.

<figure><img src="/files/izpl4EM1RfABKIZtFfkW" alt=""><figcaption></figcaption></figure>

This will show the list of transactions created. Select the transaction to be verified, and click on *Full Detail* button under *Transaction Operations*. A pop up will open to show all the information about the transaction, account holder, and the end customer.

Make sure the amount, last four digits of the credit card, card type, and expiration date are correct.

<figure><img src="/files/7ZJ2aJfIvf6EqsyhVVZN" alt=""><figcaption></figcaption></figure>

### Testing declines <a href="#testing-declines" id="testing-declines"></a>

There are scenarios where the transaction can get declined due to various reasons like insufficient funds, card not allowed, lost/stolen card, etc. In such cases, the transaction would appear as *FAILED*.

{% hint style="info" %}
You can find penny codes for testing declines in the [Global Payments Testing](/documentation/testing/global-payments-testing.md) section.
{% endhint %}

You can click *Full Detail* to try to find out the reason for decline by checking `TxStatus`, `Flags,` and other values.

### Testing partial auth <a href="#doing-a-partial-authorization-with-aspen" id="doing-a-partial-authorization-with-aspen"></a>

#### Partial auth testing data <a href="#partial-auth-testing-data" id="partial-auth-testing-data"></a>

To test a partial authorization, you can use one of these cards:

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>4788 2500 0002 8291</strong></td><td><a href="/files/4WAMdYKoy2zK810bs7gT">/files/4WAMdYKoy2zK810bs7gT</a></td></tr><tr><td><strong>4055 0111 1111 1111</strong></td><td><a href="/files/4WAMdYKoy2zK810bs7gT">/files/4WAMdYKoy2zK810bs7gT</a></td></tr><tr><td><strong>6011 0009 9550 0000</strong></td><td><a href="/files/KqLbqu8tEkA7X8ZKKMmq">/files/KqLbqu8tEkA7X8ZKKMmq</a></td></tr><tr><td><strong>6011 2121 0000 0087</strong></td><td><a href="/files/KqLbqu8tEkA7X8ZKKMmq">/files/KqLbqu8tEkA7X8ZKKMmq</a></td></tr><tr><td><strong>5454 5454 5454 5454</strong></td><td><a href="/files/NfuZ26NdM8pUWAI3vg6Q">/files/NfuZ26NdM8pUWAI3vg6Q</a></td></tr><tr><td><strong>5405 2222 2222 2226</strong></td><td><a href="/files/NfuZ26NdM8pUWAI3vg6Q">/files/NfuZ26NdM8pUWAI3vg6Q</a></td></tr><tr><td><strong>5473 0000 0000 0007</strong></td><td><a href="/files/NfuZ26NdM8pUWAI3vg6Q">/files/NfuZ26NdM8pUWAI3vg6Q</a></td></tr><tr><td><strong>3714 4963 5398 431</strong></td><td><a href="/files/WNacEG1cwaX2b9tiQ2mD">/files/WNacEG1cwaX2b9tiQ2mD</a></td></tr></tbody></table>

{% hint style="info" %}
Using the test cards, if you enter the amount of $2.78, you should get partial approval for $2.57, and if you enter the amount of $3.26, you should get a partial approval for $1.26.
{% endhint %}

### Testing receipts <a href="#testing-receipts" id="testing-receipts"></a>

The receipt can also be printed in the Virtual Terminal by expanding the *Receipts* dropdown and clicking the *Merchant* or *Customer* button.

<figure><img src="/files/aXnRVrqJSNqtlSPf0MmP" alt=""><figcaption></figcaption></figure>

***

## Verifying consents <a href="#verifying-consents" id="verifying-consents"></a>

Click on the *Reports* menu and choose *Consents.*

Select the consent that needs to be verified from the grid. Click the *Full Detail* button and make sure the consent, account holder, and end customer details look correct.

<figure><img src="/files/zrcMzBG8ZN1CH9LoRzYW" alt=""><figcaption></figcaption></figure>

To view the consent agreement, click on the *Merchant Consent* or *Customer Consent*.

<figure><img src="/files/wlc0ZtjHtbjPbRoi4nhZ" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.number.tech/documentation/testing/testing-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.