Community
Top 10 API FAQs
Find answers to 10 frequently asked questions about the TabaPay API.
1. How do I get started with the API?
You will need to reach out to [email protected], to share your business use case to begin your integration. Once you receive a review from compliance, you will get access to the Sandbox environment.
2. What are the card and bank APIs?
Card and Bank APIs include Query Bank and Query Card. These are API requests that return the attributes for a requested payment card or bank. They can be used to check for an existing bank or card and performed with AVS or ANI services.
3. How do I accept a payment?
You can accept a payment multiple ways using the TabaPay API including card, bank and real-time payment options. Accepting payments use the same API endpoint as sending a payout does, but just different parameters including type:pull
. You can transmit card or bank information in the API, use tokenized accounts with TabaPay, RSA encryption, ACH, or RTP payment methods.
4. How do I send a payout?
You can payout funds multiple ways using the TabaPay API including card, bank and real-time payment options. Payouts use the same API endpoint as accepting a payment does, but just different parameters including type:push
. You can transmit card or bank information in the API, use tokenized accounts with TabaPay, RSA encryption, ACH, or RTP payment methods.
5. What is FQDN?
FQDN stands for Fully Qualified Domain Name, which is replaced with your appropriate domain. This will go into your full base URL that you will use for each endpoint. Ensure the domain you're using is consistent with the environment you're testing in (sandbox, production, etc.)
6. Where do I get my client ID?
When you are fully approved you will receive your ClientID from TabaPay. Use this to swap the ClientID section in your endpoints.
7. How can I collect or pass card information through the API?
There are a few different ways you can pass card information. It is important to know Payment Card Industry Standards apply when handling personal information, or PII. To avoid meeting these standards yourself, you can use the Browser SDK to collect credit card information. You can then send a Create Account request using the card information you collected an save card information (accountID) on your platform. You can use this accountID in the Create Transaction API.
If you do meet PCI-DSS you can also pass card information using the full card info using the account object.
If you already use your own card tokens, you can refer to Processor Tokens to see how you can integrate with TabaPay as an additional processor.
8. Where can I find some code samples to get started?
You can refer to the recipes section to grab code snippets for different API requests. You can also refer to the API reference to view different request examples and responses.
9. What options do you have for a payment interface?
You can refer to the Dynamic iFrame for an example regarding a payment interface for clients.
10. I’m getting an error what do I do?
If you are working in Sandbox with the TabaPay API, you can post on the community forum. If you are working in production or working with sensitive information, reach out to [email protected] or contact support.