How can RemitONE platform integrate with my correspondent entity (if the bank is not a RemitONE client)?

There are a number of ways through which your correspondent entity can accept and payout transactions. 

RemitONE Payout Interface: Your correspondent entity can simply access your white label RemitONE system to pay out transactions. All they need is a browser and access to Internet. This is the simplest and most cost–effective approach for you and the correspondent entity.  

FTP integration: This is an older communication method, but still used by a large number of players in our money transfer industry. It involves the exchange of formatted CSV files over an FTP location, with a pre-defined protocol and file structure. This protocol and file structure can differ between correspondent entities. There is normally a slight delay in the processing of files. Also, the number of functions available is normally limited to transaction exchange: new transactions, processed transactions and cancellations. 

Simply put, RemitONE system will push file with all the relevant transactional data onto an FTP server. The correspondent entity will pull that file, pay out transactions, and push an updated transactional file back on to the FTP server. The RemitONE system will then pull the new file from the FTP server and update its records. 

API integration: This is the modern method and allows for richer functionality. This integration handles not just transaction flows but also real-time queries for rates and charges, as well as routing information. All calls are instantaneous without delay. There is no need to maintain an interchange FTP server for storing the data files. Each correspondent entity will likely have an API, so again either the other correspondent entity uses the RemitONE API or the RemitONE system will need to develop a module to utilise the correspondent entity’s API.