To interact with the sandbox, use the endpoints shown in the API Descriptions section on the right.
Step 1: Click the "LOG IN" button on this screen to authenticate.
Step 2: Send requests to the URLs shown in the API Descriptions section. Each endpoint includes an example JSON body to help you get started.
Step 3: Click the received transmissions that appear on the left inbox panel to view any results.
Your unique URL:
Log In - Input your own API key and Merchant UUID or use the freely provided ones.
Version: 1.0.0
API Key
Merchant UUID
Test Card Information
https://paidyet.readme.io/docs/sandboxUse these test cards to test different transaction scenarios in the sandbox environment.
| ID | Card Number | Expiration | CVV | Status | Decline Code | Message | AVS Response | CVV Response |
|---|---|---|---|---|---|---|---|---|
| 1 | 4000100011112224 | 932 | 123 | approved | m | |||
| 22 | 4000100111112223 | 932 | 321 | approved | A | m | ||
| 23 | 4000100211112222 | 932 | 999 | approved | N | m | ||
| 24 | 4000100311112221 | 932 | 999 | approved | W | m | ||
| 2 | 4000300011112220 | 932 | 999 | declined | Declined | |||
| 3 | 4000300001112222 | 932 | 999 | declined | 4 | Pickup Card | ||
| 4 | 4000300211112228 | 932 | 999 | declined | 5 | Do Not Honor | ||
| 5 | 4000300311112227 | 932 | 999 | declined | 12 | Invalid transaction | ||
| 6 | 4000300411112226 | 932 | 999 | declined | 15 | Invalid Issuer | ||
| 7 | 4000300511112225 | 932 | 999 | declined | 25 | Unable to locate Record | ||
| 8 | 4000300611112224 | 932 | 999 | declined | 51 | Insufficient Funds | ||
| 9 | 4000300711112223 | 932 | 999 | declined | 55 | Invalid Pin | ||
| 10 | 4000300811112222 | 932 | 999 | declined | 57 | Transaction Not Permitted | ||
| 11 | 4000300911112221 | 932 | 999 | declined | 62 | Restricted Card | ||
| 12 | 4000301011112228 | 932 | 999 | declined | 65 | Excess withdrawal count | ||
| 13 | 4000301111112227 | 932 | 999 | declined | 75 | Allowable number of pin tries exceeded | ||
| 14 | 4000301211112226 | 932 | 999 | declined | 78 | No checking account | ||
| 15 | 4000301311112225 | 932 | 999 | declined | 97 | CVV failure | n | |
| 21 | 4000100411112220 | 932 | 999 | approved | X | m | ||
| 25 | 4000100511112229 | 932 | 999 | approved | Y | m | ||
| 26 | 4000100611112228 | 932 | 999 | approved | Z | m | ||
| 27 | 4000100811112226 | 932 | 999 | approved | Cardholder name and ZIP match | 1 | m | |
| 28 | 345678901234564 | 932 | 999 | approved | Cardholder name, address, and ZIP match | 2 | m | |
| 29 | 371449635398431 | 932 | 999 | approved | Cardholder name, address match | 3 | m | |
| 30 | 378282246310005 | 932 | 999 | approved | Cardholder name matches | 4 | m |
POST
Create a Transaction
localhost:3000/api/null/v3/transaction
Create a new transaction (sale or auth). Transactions can also be scheduled using this endpoint by simply passing in a schedule object.
Example JSON Body:
{
"credit_card": {
"number": "4000100011112224",
"exp": "0932",
"cvv": "123"
},
"amount": 1.04,
"type": "sale"
}GET
Search for Transactions
localhost:3000/api/null/v3/transaction/search
Get a collection of transactions matching the supplied criteria. At least one parameter is required. Specify the search in the URL query string. Possible query keys are below Example: GET [base_url]transaction/search?date=2022-03-22&amount=1.02 will get all transactions run on the 22nd of march 2022 for $1.02.
GET
Retrieve a Transaction
localhost:3000/api/null/v3/transaction/{transaction_id}
Get a single transaction by its ID.
POST
Refund a Transaction
localhost:3000/api/null/v3/transaction/{refund_transaction_id}
A refund should be used once the transaction you are refunding has settled. If you are trying to cancel a transaction that is still in the currenly open batch, you should use the void command instead. To refund a transaction that has been settled, you will pass in the transaction object with the type of 'refund', the original transaction id, and the amount you would like to refund. Most merchant accounts do not allow you to refund more than the original amount of the transaction. However, depending on the Credit Policy, a refund can be processed for larger than the original transaction amount.
Example JSON Body:
{
"type": "refund",
"transaction_id": "{original_transaction_id}",
"amount": 1.04
}PUT
Capture a Transaction
localhost:3000/api/null/v3/transaction/{capture_transaction_id}
The capture command moves an authorized transaction into the current batch for settlement. It is possible to capture an amount other than the one originally authorized, however, you must follow the guidelines established by the merchant service bank. Capturing a higher or lower dollar amount could result in additional penalties and fees. Most banks typically allow no more than 10 days to pass between the authorization/capture and settlement of a transaction.
Example JSON Body:
{
"type": "capture",
"amount": 1.04
}PATCH
Void a Transaction | Increment a Lodging Transaction
localhost:3000/api/null/v3/transaction/{void_transaction_id}
Once a transaction has been voided, it will not show up on the customer's credit card statement. Customers who have online banking that allows them to see 'Pending' transactions may see the voided transaction for a few days before it disappears. You can only void a transaction that hasn't been settled yet. A transaction is settled when the batch that it is in has been closed. If the transaction has been settled, you must run a refund instead using a void transaction. If you run a credit, both the credit and the initial charge will show up on the customer's credit card statement. You can void a transaction by putting the original transaction with a type of 'void'. For a Lodging transaction, you can increment it by posting it with a type of 'incremental' and the additional amount as the amount. For check-out, post the original transaction with a type of 'sale'.
Example JSON Body:
{
"type": "void"
}