Sorry - either this article does not exist or you haven't been given permission to view it.
Knowledgebase

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.

 

 

This KB article just documents how to setup Pulse Telecom SMS.

In System Configuration Settings, please provide values for the following settings:

SMS_USERNAME -> pulse telecom username
SMS_PASSWORD -> pulse telecom password
SMS_SERVER -> The URL that you need to send the messages to
SMS_ENDPOINT -> The endpoint of the URL you need to send the messages to (you do not need to actually add anything here a you can pass the full URL in the SMS_SERVER setting but if you do, please make sure there is a / at the end of the SMS_SERVER setting)
SMS_FROM_NAME -> The name of the person/company sending message

If you need to make any changes to the Pulse Telecom Code due to some issues, you can find the code in the following file:

classes/util/sms/PulseTelecomSMSSender

The KB article will just tell you how to setup the Flagright Integration.

In config_3rdparty.json, complete the settings for the below config

"FLAGRIGHT": {
	"enabled": false,
	"url": "https://sandbox.api.flagright.com/",
	"api_key": "",
	"webhook_hash_secret": "",
	"suspicious_risk_level": { // craRiskLevel
		"remitter": "VERY_HIGH",
		"beneficiary": "VERY_HIGH",
	}
},

In config_notification.json, in realtime subscriptions, add the following subscribers.

"CREATE_REMITTER": [
	"remitone\\integration\\Flagright\\Subscribers\\FlagrightMemberSubscriber"
],
"CREATE_BENEFICIARY": [
	"remitone\\integration\\FlagrightSubscribers\\FlagrightBeneficiarySubscriber"
],
"UPDATE_REMITTER": [
	"remitone\\integration\\Flagright\\Subscribers\\FlagrightMemberSubscriber"
],
"UPDATE_BENEFICIARY": [
	"remitone\\integration\\Flagright\\Subscribers\\FlagrightBeneficiarySubscriber"
],
"NEW_TRANSACTION": [
	"remitone\\integration\\Flagright\\Subscribers\\FlagrightVerifyTransactionSubscriber"
],

If the client wishes to use the Webhook notifications, you need to configure webhooks to point to the following url:

https://{arm-url-here}/Flagright_notify.php

There is also a script to create all the remitters/beneficiaries on the system as a user on flagright, the realtime subscriptions do handle this as well:

php bin/integration flagright:create-users

This is just a guide on how to setup the EDD/Threshold (compliance) forms on the Velocity compliance rules.

The default behaviour is of that if you select that the velocity compliance rule should print the edd form once the rule is triggered, it will use the form that is set in THRESHOLD_OVERRUN_FORM in config.json.

If you want to have multiple EDD/Threshold forms, you need to configure the following:

COMPLIANCE_FORM_PRINT_SELECT

Add the forms you want selectable on the velocity compliance rules to the above config in System Configuration Settings. You can then select which compliance rule should print which form on the select box which appears after the Print Compliance Form select box once values are configured in the above setting.

As of now, there are only three forms available:

1. gsc_form_one_pdf
2. gsc_form_two_pdf
3. threshold_overrun_form_pdf

Any new forms that need to be added need to be passed over to the Change Request team so that the Dev team can add the form to the current available forms.

This article (attachment) explains in depth how our billing function operates and to give examples of how transaction and support incident costs are calculated, our customisation (bespoke development) payment and delivery process and how we allocate your payments made to us. The final sections cover how and when we send out reminders, suspension of service (due to non-payment), late payment fees, disputed items and VAT charges.

Please read this article carefully. If you have any questions regarding this article or your business circumstances please feel free to contact billing@remitone.com

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

Most popular articles 
 
Newest articles