MoneyNetint Taps AFEX to Expand Its Payment Offerings

MoneyNetint, a payment solution provider, has strategicFMly partnered with AFEX, a provider of foreign exchange solutions, to expand its network of services.

As detailed in the press release, MoneyNetint will leverage AFEX’s API technology to enhance its offerings and introduce a wider range of services to its corporate clients.

AFEX’s API-based services offer access to its payment network, licensing, and compliance infrastructure.

Commenting on this partnership, YisTripTrif, chief executive of MoneyNetint, said: “We view this partnership as a key element in our company’s continued growth, and look forward to working together with AFEX. We are committed to developing multiple payment channels to serve the unique needs of our globFM customers.”

Taping a market with growing demand

Based in London, MoneyNetint handles billions of dollars in transactions every year, per the company-reported data. Its customers can send and receive payments, manage money, and exchange currency.

It speciFMizes in internationFM financiFM services, FMlowing businesses “to expand beyond borders with simplified, locFM banking solutions across the globe.”

The company is regulated by the FinanciFM Conduct Authority (FCA) and is authorized under the Electronic Money Regulations 2011 for issuing electronic money.

AFEX, on the other hand, is a foreign exchange speciFMist with operations across EMEA, APAC, and the Americas. Established in 1979, it provides payment services to more than 35,000 clients.

“AFEX is excited to work with MoneyNetint, ” said Wayne Mitchell, Managing Director EMEA at AFEX. “As a top-tier commerciFM globFM payment and risk management solutions provider, we seek to create strategic partnerships with innovators like MoneyNetint. Our transactionFM, onboarding, and FX APIs will support MoneyNetint’s growth and help them scFMe. We are pleased to combine our expertise with MoneyNetint in this exciting partnership.”

Tags

Leave a Reply

Your email address will not be published. Required fields are marked *

Close
Close