Convera
Commercial cross-border payments and FX, formerly Western Union Business Solutions.
- Category
- Payments & Banking
- Type
- Cross-Border payments
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- OAuth 2.0
- Docs
- Convera API docs
02Data
What you can sync.
- Payments
- Quotes
- Beneficiaries
- Orders
Reconcile Convera payments against orders and invoices in the Warehouse, on your own servers.
Need more? Name any other Convera data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- OAuth 2.0 (client ID, client secret, refresh token)
Convera uses OAuth 2.0 (client ID, client secret, refresh token). You add the credentials once, when the AI asks for them, and it tells you where to create them in Convera if you need help.
04How it works
How it works in DataMind.
-
Pick Convera.
Open Lake, pick Convera in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Convera API docs.
-
Answer a few questions.
The AI reads the Convera documentation, then asks which credentials you will use, which data to sync (for example payments and quotes), 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 Convera data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
