Remittance New Countries

Background:

• Remittance has different providers namely Thunes, GMT, Uniteller and Remitee. All these providers need constantly new payers for the remittance transactions. However, sometimes new payers are coming from new countries that are not configured in our side yet.

Problem:

• When we configure a new payer, we have to add changes in different remittance repositories. We could in some cases forget configuring at some places and then we could start getting erros from upper environments.

• Also, if a new developer is in charge of a new country configuration, we could forget some place at the sharing knowledge.

Solution: 

Here is the list of the common PRs created when a new remittance country is configured.

• be-mf-remittance
• product-datasheets
• be-configuration
• be-mf-configuration

Remember these changes requirements can vary in future but for now, those are the most common changes.

Guide to Monitor

Follow the below steps to monitor the system when a new country is configure:

• Check is the country rates are loaded in the BE as expected.

• Always start updating configuration values for DEV and STG and after succeeding in STG then you could mirror changes into PROD.

• Run some transactions with different transfer type with any payer of the new configured country. Try with both licenses MPS and MUSA.