Tap Payments
GCC payment gateway for cards, KNET, mada, Benefit and wallets.
- Category
- Payments & Banking
- Type
- Payment gateway
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- Access token
02Data
What you can sync.
- Charges
- Refunds
- Customers
- Invoices
- Payouts
Bring Tap Payments charges into the same model as revenue and costs, so finance and operations read the same numbers.
Need more? Name any other Tap Payments data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- An access token
Tap Payments uses an access token. You add the credentials once, when the AI asks for them, and it tells you where to create them in Tap Payments if you need help.
04How it works
How it works in DataMind.
-
Pick Tap Payments.
Open Lake, pick Tap Payments in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Tap Payments API docs.
-
Answer a few questions.
The AI reads the Tap Payments documentation, then asks which credentials you will use, which data to sync (for example charges and refunds), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
It builds the connector, tests it and shows you sample rows. Then Tap Payments data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
