Our Sandbox is a safe environment that enables you to test the features of Pentadata’s APIs. Sandbox usage is free of charge and you can get access here.
If this is the first time you read this page, then you should definitely start with our interactive tutorial. Click on this link to begin: Play With Pentadata.
To ease your development and testing, the sandbox environment comes with preloaded data.
The dataset available in the sandbox is very realistic, but it’s computer-generated and does not reflect any actual personal information.
The sandbox url is https://sandbox.pentadatainc.com
The tutorial will give you a very good overview of what you can do with the API, hence it should always be your first step.
The sandbox is built to accurately reproduce the data format that the production API has. And it’s free to use, without limits.
As such, you should use our sandbox in your development/UAT environment, for as long as you need, and develop your code around it. It should not take very long, as the API is simple and easy to use.
Once you are ready, you can request production access and do the final tweaks to your software before rolling out to your customers.
A Consumer is the end-user of your platform, likely the owner of a bank account or card that you want to get data from.
We refer to consumers as Person objects. If you use our Transactions, Auth, or PayMeBack products, then you must add some Person objects, via the endpoint POST /persons.
In the sandbox, you can use any of the following:
|FIRST NAME||LAST NAME|
Our production API gives access to any person payment transactions, from debit and credit cards as well as from bank accounts.
Some things you can do with banking data:
To test this in the sandbox, you can use either of the following dummy bank names:
This will be input to the POST /accounts endpoint, along with a “redirect_uri” field, that can be any web page, even https://example.com, and it should be the page where you want your consumer to arrive after they have confirmed permission through their bank.
In the simulated bank pages, use any of the following usernames:
with any non-empty password. Pentadata never stores bank credentials.
The highlights of our product suite are the AI-developed signals, for Person as well as for Merchant objects.
MccMatch and MerchantSight are two API products that allow you to categorize and identify merchants, respectively, just by looking at the transaction statement, down to their address and location.
To test these in the sandbox, use any of the following:
*PPL STBX #846-LA 9864 #IY4
WALM 101-NYC #R54B
*AZ #FF9 AMZ-MKT 0001
TRD JO 5R3F #174 PPX
D975 M’MCDO #846 TR47HH B
Auth is our API product that allows you to authenticate a Person's information (address, phone, etc.) and even generate their income score.
To test this in the sandbox, first add a Person as explained in the sections above, then use the following table to prepare the API input:
|PERSON||PERSON 1471510495||PERSON 2135164718||PERSON 1017321090||PERSON 1185752556|
|Address||Street One, 111||Street Two, 222||Street Three, 333||Street Four, 444|
|City||New York City||Boston||Los Angeles||San Francisco|
|SSN (last 4 digits)||0001||0002||0003||0004|
|Date of birth (dob)||1990-01-01||1990-02-02||1990-03-03||1990-04-04|
You will get a set of questions that must be answered. In the sandbox, always use the question-answer IDs pairs (Q1, A1) and (Q2, A2).