Support Desk

We have a dedicated in-house support team ready to help with all your enquiries on any of our products.

•          Application & Services - All products in our RemitONE suite.
•          Accounts & Billing - Get help with your accounts, subscriptions and payments.

Our technical support team are readily available to help with all your Money Transfer Engine (MTE) related issues and enquiries. They can be reached via the following contact:

Online Helpdesk: https://support.remitone.com/

Telephone: +44 (0)20 8099 5795

Telephone support is provided to customers on Professional & Enterprise Editions only, please consult your agreement if you are unsure if you qualify for telephone support.

To make any fields display or required based on your own needs please follow the information below.

Go to the ARM > Settings > System Configuration Settings > Configuration Classification : UI > Expand "Field Settings"

Just a little recap about the configuration UI settings -

1- the whole system looks at  This includes the ARM, ORM and RWS.

2- The ORM and RWS then look at for any overrides. If you change anything in point 1 and it doesn't reflect on the apps/ORM then you will need to change it here as well.

3- For any country overrides you will need to add them to . "Country Name-Destination" for the ARM , "ORM-Country Name-Destination" for the the ORM/apps. "Country Name" for the source country. "Country Name" will be the exact spelling you use for said country in the Destination/Source country list.

Eg

Please see the information below about the fields:

a- If a field starts with "remitter.registered" then this is for the remitter profile with registration type "Registered". For Edit and Create remitter page.

b- If a field starts with "remitter.basicregistered" then this is for the remitter profile with registration type "Basic registered". For Edit and Create remitter page.

c- If a field starts with "benef" then this is for the beneficiary profile (create and edit page).

d- If a field starts with "trans_new" then it is for the transaction creation page.

e- If a field starts with "trans_payout" then it is for the transaction payout screen (when the bank pays out the transaction).

If there are any further questions please do not hesitate to get in touch.

Configuration

To configure Africell, please open the file custom/config/config_3rdparty.json and copy the following code

"CONFIG_AFRICELL": {
    "enabled": true,
    "debug": false,
    "check_ssl_certificate": false,
    "processing_bank_prefix": "AFRICELL-",
    "base_uri": "XXX",
    "credentials": {
        "auth_token": "XXX",
        "bearerCode": "XX",
        "currency": "101",
        "languageId": "1",
        "languageCode": "en",
        "transactor": {
            "idType": "mobileNumber",
            "msisdn": "",
            "productId": "12",
            "mPin":"XXX"
        }
    },
    "allowed_destination_countries": [
        "SL"
    ],
    "cron_frequency": "*/5 * * * *",
    "max_export_attempts": 3
}

The values of the fields will be given by the client, but few fields will have values that should be standard (see the code above).

State Machine

The second step is to modify the file custom/config/config_state_machine.json, or create it if it does not exist.

In this file search for the section modify_state_machine and comment out AFRICELL in the section BANKS_TO_HQOK.

"modify_state_machine": {
        "BANKS_TO_HQOK": [
            "AFRICELL-"
        ]
}

Entities and Cron Jobs

The next step is to create the entities that will be used by the integraion; to do it, just run the following command in the terminal:

php bin/integration africell:setup-entities

The last step is to configure the cron jobs that will export the transactions and check their status regularly; to do it, configure the cron frequency (see above), and run the following command in the terminal:

php libs/vendor/bin/crunz schedule:run

At this point the integration should be working correctly.

This is an integration to export transactions for Mobile Transfer mainly but Cash Collection is also supported (transaction is created as cash collection but it will still be sent to Panamax to the beneficiary’s mobile number and it is assumed the beneficiary will be notified by mobile and then come and collect cash). It has its own cron job and its own classes. 

Deployment Steps 

1. In config_3rdparty.json copy the variable CONFIG_PANAMAX from the general config_3rdparty.json.in  
2. In the custom CONFIG_PANAMAX fill the fields as follows: 
   "CONFIG_PANAMAX": { 

    "enabled": true,       

    "debug": TRUE,    // true if you need to debug requests and responses     

    "processing_bank_prefix": "Panamax-",     

    "base_url": "https://uat-adp.apsmoney.gm/",     

    "from_user_identifier": "[Client Phone Number]",     

    "export_transactions_cron_frequency": "*/5 * * * *",     

    "mpin": "[Client Pin]",       

    "max_export_attempts": 3,       

    "api_credentials": {    // Given by the api     

        "username": "",       

        "password": "",     

    },       

    "user_credentials": {    // Given by the client 

        "username": "",     

        "password": "",       

    },       

} 

1. In the config/config_state_machine.json file add new entry in `BANKS_TO_HQOK` with the same value as for `processing_bank_prefix` from the previous point.  
2. A processing bank needs to be set up in the country where Panamax will do payout and it needs to begin with the specified prefix in config e.g. PANAMAX-GM. 
3. Set up MNO/MNOs and delivery bank(s) and collection point(s) linked to the Panamax processing bank for the integration to work. There is no delivery import in this integration and there is no mention of MNOs or collection points in the Panamax documentation so it is up to the client to decide how they will setup the delivery entities. 
4. For export transactions manually to Panamax, run this command (from the R1 system root folder): 
   bin/console integration panamax:export-transactions 

Configuration

To configure MagicPay, please open the file custom/config/config_3rdparty.json and copy the following code

"CONFIG_MAGICPAY": {
    "enabled": false,
    "sandbox": false,
    "tokenization_url": "https://tokenization{sandbox}.magicpaysecure.com/tokenization/v0.2/", // {sandbox} will be replaced with .sandbox if needed
    "api_url": "https://api{sandbox}.magicpaysecure.com/v2/", // {sandbox} will be replaced with .sandbox if needed
    "auth": {
        "data-tokenization-key": "",
        "username": "",
        "pin": ""
    }
}

Just set enabled to true, set sandbox to true for test, the URLs will not change.

The values for data-tokenization-key, username and pin will be given by the client, or generated in the configuration panel of MagicPay.

Please note that the accepted currency is only USD, and no conversions have been made for the amount to be sent during the payment.

For this reason this integration can work only if the source currency is USD.

Dear RemitONE customer, let us know how we can help support you with your platform! Best wishes, Reza.