About Xe
Xe provides currency information and money-transfer services. The Crassula connector described here focuses on bringing currency-related data into financial workflows. Teams should distinguish an indicative rate or reference data feed from an executable quote, a booked conversion and an actual payment. The availability of each service depends on the specific integration and commercial arrangement.
Currency workflows in a financial product
Foreign exchange workflows combine currency information, a customer instruction and the operational steps required by the selected provider. A product should make the role of each value clear: displayed information, a quote, an accepted conversion and the resulting payment are different stages of the journey.
- Define the source and freshness of displayed currency information.
- Record the currencies, amounts and provider reference for supported requests.
- Plan how conversion outcomes and payment statuses reach the customer.
For the operating team, the value lies in connecting these stages to the surrounding account and customer context. This supports enquiries about a quoted amount, a conversion result or a related transfer. Final pricing, supported currencies, quote validity and settlement depend on the agreed provider service.
Working with the connector
Crassula provides the software layer for organising customer journeys and operational processes around the connected service. A team can bring the functions included in its implementation into a branded product, while retaining a common place to review customer information, service requests and the resulting operational records. The provider continues to deliver its part of the service under the relevant agreement.
A useful starting point is to map the customer journey from the initial request to its final outcome. Define which information is submitted, what response is expected, which status is shown to the customer and how an operator handles an exception. This makes it easier to design a clear experience and to identify where automated processing or human review is appropriate.
Planning your implementation
Agree the required functions with Crassula and the provider, then test the complete journey in the available test environment. Include successful requests, incomplete data, unsuccessful responses and recovery after an interruption. Establish responsibility for customer support, operational follow-up and changes to the provider service. The connector can then become part of a documented product workflow, with clear expectations for customers and the team operating it.
Provider and connector overview
The gallery gives a provider-specific visual overview. Official imagery is included where available, alongside a simplified explanatory diagram of the connector’s role in a Crassula product.
