Getting Started
Last updated
Was this helpful?
Last updated
Was this helpful?
, to sign up for a sandbox account.
That's it! Now you have everything you need to be able to start playing with Synapse's APIs.
We usually recommend downloading Postman and getting a feel for our APIs before writing code. The following steps will make this process easier.
If you've downloaded our Postman collection, you should be seeing our APIs on the left and the appropriate environment variables on the right.
The next step is to add your own client keys into the environment variables.
The next step is to create a user account and supply all of their KYC.
If you are curious about the user profile and want to see more details, just click on the user, the dashboard will show you all the information you just added to the user profile.
Same as before, we will automatically set the appropriate OAuth key for you.
Also, when you Sign in as a User on the dashboard, the same operation is happening behind the scenes.
You can Sign In by supplying the fingerprint you created the user account with:
Now, you can perform all the actions on behalf of the user from the dashboard, like how you can with the APIs.
Now if you'll go back to the dashboard, you will see the Deposit Node under the user profile.
Congratulations! 🎊 🎈 🎉 You've successfully created a deposit account for your user.
Now let's enable some features on this deposit account.
In this case, our user would like to enable ACH Credits and Debits via an External Account. So let's link an external ACH account:
Now let's verify the ACH account via Micro-deposits:
Now if you go to the dashboard, you will see an ACH-US
node linked under the user profile with Credit and Debit
permissions.
Our user would also like to issue an account and routing number that they can give to their payroll provider and apps like Venmo and PayPal. So let's issue an account number for them:
Now if you go to the dashboard, Sign In as User, and click on the Deposit Account, you will see the account and routing numbers issued on the account:
Our user would also like to issue a card so they can use this account for shopping and other expenses. So let's issue one for them:
Now if you go to the dashboard, Sign In as User, and click on the Deposit Account, you will see the card number issued on the account:
Now your user has a fully functioning Deposit Hub!! 😀
Let's get our Webhook URL:
Now let's create a Subscription:
You will be able to see this subscription created on the dashboard as well:
To test this, let's issue another account number for our user:
Since we had subscribed to SUBNETS|POST
updates, you will see a webhook set to your Webhook Site link:
You can view the logs on the dashboard as well:
As our final step of this tutorial, let's fund our user's deposit account so that they can go out and spend:
If you'll go to the dashboard, you will see the transaction created:
In a few minutes, the transaction will move to settled:
Now our user has funds in their account to spend:
2. Finish On-Boarding. This step might feel onerous, but behind the scenes, it gives us the information we need to enable the appropriate features for you on sandbox. KYC information supplied here can be fake or real. If it is real, we can use this information to enable production access for you when you are ready to go live with us. If fake, you will need to finish the same setup on our .
3. to get client credentials.
|
Once the user account is created, to see the user there. If everything is right, you will see the user go to Send and Receive
Permissions on the dashboard.
The next step will be to start performing actions on behalf of the user. To do that, you need to grab an token for the user.
To do that, usually, make a API call and grab the refresh_token
from the user profile. With our Postman collection, all of that is automated.
So the next step is to . Currently, we will make an OAuth key with all the scopes. .
In this section, pick a hub you wish to enable for the user ( or ). In this example, we will pick Deposit Hub.
PS: We would also recommend trying out our to emulate some card transactions.
In our next step, let's use to test subscribing to updates as they occur in the system.
As next steps, we would recommend: 1. Taking our language SDKs for a spin: | | | | .
2. Reviewing our Resource.
3. when ready.