From 4ba5ca0fe384be7c134a8915c3633b3d9da3d88c Mon Sep 17 00:00:00 2001 From: liuxinxin Date: Tue, 22 Oct 2019 10:47:39 +0800 Subject: [PATCH 01/24] =?UTF-8?q?=E3=80=90R=E3=80=91=E8=87=AA=E5=8A=A9?= =?UTF-8?q?=E8=BF=9B=E4=BB=B6=E4=B8=9A=E5=8A=A1=E6=8E=A5=E5=8F=A3=E5=BC=80?= =?UTF-8?q?=E5=8F=91?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../manage/appclient/beans/AppClientBean.java | 49 ++++++ .../core/impls/RetailAppServiceImp.java | 5 + .../application/beans/ClientPreApplyBean.java | 157 ++++++++++++++++++ .../core/SimpleClientApplyService.java | 6 + .../impls/SimpleClientApplyServiceImpl.java | 150 ++++++++++++++++- .../web/SimpleClientApplyController.java | 13 ++ .../manage/merchants/core/ClientManager.java | 2 + .../core/impls/ClientManagerImpl.java | 66 ++++++++ src/main/ui/merchant_application.html | 91 ++++++++++ .../merchant_application.js | 65 +++++++- src/main/ui/static/payment/partner/partner.js | 2 +- 11 files changed, 600 insertions(+), 6 deletions(-) diff --git a/src/main/java/au/com/royalpay/payment/manage/appclient/beans/AppClientBean.java b/src/main/java/au/com/royalpay/payment/manage/appclient/beans/AppClientBean.java index 45f022217..c4d663f31 100644 --- a/src/main/java/au/com/royalpay/payment/manage/appclient/beans/AppClientBean.java +++ b/src/main/java/au/com/royalpay/payment/manage/appclient/beans/AppClientBean.java @@ -35,6 +35,11 @@ public class AppClientBean { @JSONField(name = "contact_job") private String contactJob; + private String registered_address; + private String registered_suburb; + private String registered_state; + private String registered_postcode; + public JSONObject updateObject() { JSONObject res = new JSONObject(); if (contactPerson != null) { @@ -84,6 +89,18 @@ public class AppClientBean { if (legalJobTitle != null) { res.put("job_title", legalJobTitle); } + if (registered_address != null) { + res.put("registered_address", registered_address); + } + if (registered_suburb != null) { + res.put("registered_suburb", registered_suburb); + } + if (registered_state != null) { + res.put("registered_state", registered_state); + } + if (registered_postcode != null) { + res.put("registered_postcode", registered_postcode); + } return res; } @@ -205,4 +222,36 @@ public class AppClientBean { public void setLegalPhone(String legalPhone) { this.legalPhone = legalPhone; } + + public String getRegistered_address() { + return registered_address; + } + + public void setRegistered_address(String registered_address) { + this.registered_address = registered_address; + } + + public String getRegistered_suburb() { + return registered_suburb; + } + + public void setRegistered_suburb(String registered_suburb) { + this.registered_suburb = registered_suburb; + } + + public String getRegistered_state() { + return registered_state; + } + + public void setRegistered_state(String registered_state) { + this.registered_state = registered_state; + } + + public String getRegistered_postcode() { + return registered_postcode; + } + + public void setRegistered_postcode(String registered_postcode) { + this.registered_postcode = registered_postcode; + } } diff --git a/src/main/java/au/com/royalpay/payment/manage/appclient/core/impls/RetailAppServiceImp.java b/src/main/java/au/com/royalpay/payment/manage/appclient/core/impls/RetailAppServiceImp.java index 0c32d1df7..ef31e70ab 100644 --- a/src/main/java/au/com/royalpay/payment/manage/appclient/core/impls/RetailAppServiceImp.java +++ b/src/main/java/au/com/royalpay/payment/manage/appclient/core/impls/RetailAppServiceImp.java @@ -67,6 +67,7 @@ import com.alibaba.fastjson.JSONObject; import com.github.miemiedev.mybatis.paginator.domain.Order; import com.github.miemiedev.mybatis.paginator.domain.PageBounds; import com.github.miemiedev.mybatis.paginator.domain.PageList; +import org.apache.commons.codec.binary.Base64; import org.apache.commons.lang3.ArrayUtils; import org.apache.commons.lang3.RandomStringUtils; import org.apache.commons.lang3.RandomUtils; @@ -87,8 +88,10 @@ import org.thymeleaf.context.Context; import org.thymeleaf.spring5.SpringTemplateEngine; import javax.annotation.Resource; +import javax.imageio.ImageIO; import javax.servlet.ServletOutputStream; import javax.servlet.http.HttpServletResponse; +import java.awt.image.BufferedImage; import java.io.*; import java.math.BigDecimal; import java.math.RoundingMode; @@ -668,6 +671,8 @@ public class RetailAppServiceImp implements RetailAppService { if (clientType.equals("iphone")) { res.put("skip_clearing", !res.getBoolean("skip_clearing")); } + sysClientLegalPersonMapper.findRepresentativeInfo(device.getIntValue("client_id")); + res.put("representative_info",sysClientLegalPersonMapper.findRepresentativeInfo(device.getIntValue("client_id"))); return res; } diff --git a/src/main/java/au/com/royalpay/payment/manage/application/beans/ClientPreApplyBean.java b/src/main/java/au/com/royalpay/payment/manage/application/beans/ClientPreApplyBean.java index 30777aeb7..e2b44065d 100644 --- a/src/main/java/au/com/royalpay/payment/manage/application/beans/ClientPreApplyBean.java +++ b/src/main/java/au/com/royalpay/payment/manage/application/beans/ClientPreApplyBean.java @@ -3,6 +3,7 @@ package au.com.royalpay.payment.manage.application.beans; import com.alibaba.fastjson.JSON; import com.alibaba.fastjson.JSONObject; +import com.alibaba.fastjson.annotation.JSONField; import org.apache.commons.lang3.StringUtils; import javax.validation.constraints.NotEmpty; @@ -56,6 +57,50 @@ public class ClientPreApplyBean { private String client_pay_type = "2"; private String client_pay_desc = "201"; + @NotEmpty(message = "contact_job can't be null") + private String contact_job; + @NotEmpty(message = "representative_person can't be null") + private String representative_person; + @NotEmpty(message = "representative_phone can't be null") + private String representative_phone; + @NotEmpty(message = "representative_email can't be null") + private String representative_email; + @NotEmpty(message = "representative_job_title can't be null") + private String representative_job_title; + @NotEmpty(message = "registered_address can't be null") + private String registered_address; + @NotEmpty(message = "registered_suburb can't be null") + private String registered_suburb; + @NotEmpty(message = "registered_state can't be null") + private String registered_state; + @NotEmpty(message = "registered_postcode can't be null") + private String registered_postcode; + @NotEmpty(message = "logo_url can't be null") + private String logo_url; + @NotEmpty(message = "company_website can't be null") + private String company_website; + @NotEmpty(message = "company_photo can't be null") + private String company_photo; + @NotEmpty(message = "royalpayindustry can't be null") + private String royalpayindustry; + @NotEmpty(message = "alipayindustry can't be null") + private String alipayindustry; + + +/* private String contact_job; + private String representative_person; + private String representative_phone; + private String representative_email; + private String representative_job_title; + private String registered_address; + private String registered_suburb; + private String registered_state; + private String registered_postcode; + private String logo_url; + private String company_website; + private String company_photo; + private String royalpayindustry; + private String alipayindustry;*/ public JSONObject insertObject() { JSONObject res = (JSONObject) JSON.toJSON(this); @@ -253,4 +298,116 @@ public class ClientPreApplyBean { public String getClient_pay_desc() { return client_pay_desc; } + + public String getContact_job() { + return contact_job; + } + + public void setContact_job(String contact_job) { + this.contact_job = contact_job; + } + + public String getRepresentative_person() { + return representative_person; + } + + public void setRepresentative_person(String representative_person) { + this.representative_person = representative_person; + } + + public String getRepresentative_phone() { + return representative_phone; + } + + public void setRepresentative_phone(String representative_phone) { + this.representative_phone = representative_phone; + } + + public String getRepresentative_email() { + return representative_email; + } + + public void setRepresentative_email(String representative_email) { + this.representative_email = representative_email; + } + + public String getRepresentative_job_title() { + return representative_job_title; + } + + public void setRepresentative_job_title(String representative_job_title) { + this.representative_job_title = representative_job_title; + } + + public String getRegistered_address() { + return registered_address; + } + + public void setRegistered_address(String registered_address) { + this.registered_address = registered_address; + } + + public String getRegistered_suburb() { + return registered_suburb; + } + + public void setRegistered_suburb(String registered_suburb) { + this.registered_suburb = registered_suburb; + } + + public String getRegistered_state() { + return registered_state; + } + + public void setRegistered_state(String registered_state) { + this.registered_state = registered_state; + } + + public String getRegistered_postcode() { + return registered_postcode; + } + + public void setRegistered_postcode(String registered_postcode) { + this.registered_postcode = registered_postcode; + } + + public String getLogo_url() { + return logo_url; + } + + public void setLogo_url(String logo_url) { + this.logo_url = logo_url; + } + + public String getCompany_website() { + return company_website; + } + + public void setCompany_website(String company_website) { + this.company_website = company_website; + } + + public String getCompany_photo() { + return company_photo; + } + + public void setCompany_photo(String company_photo) { + this.company_photo = company_photo; + } + + public String getRoyalpayindustry() { + return royalpayindustry; + } + + public void setRoyalpayindustry(String royalpayindustry) { + this.royalpayindustry = royalpayindustry; + } + + public String getAlipayindustry() { + return alipayindustry; + } + + public void setAlipayindustry(String alipayindustry) { + this.alipayindustry = alipayindustry; + } } diff --git a/src/main/java/au/com/royalpay/payment/manage/application/core/SimpleClientApplyService.java b/src/main/java/au/com/royalpay/payment/manage/application/core/SimpleClientApplyService.java index 2e7c43c13..1f45ed300 100644 --- a/src/main/java/au/com/royalpay/payment/manage/application/core/SimpleClientApplyService.java +++ b/src/main/java/au/com/royalpay/payment/manage/application/core/SimpleClientApplyService.java @@ -3,8 +3,10 @@ package au.com.royalpay.payment.manage.application.core; import au.com.royalpay.payment.manage.merchants.beans.NewAccountBean; import com.alibaba.fastjson.JSONObject; +import org.springframework.web.multipart.MultipartFile; import javax.servlet.http.HttpServletRequest; +import java.io.IOException; public interface SimpleClientApplyService { void verifyRegisterSMSCode(String codeKey, String phoneNumber); @@ -15,6 +17,8 @@ public interface SimpleClientApplyService { String getAndSendSmsCode(String phoneNumber, String nationCode, HttpServletRequest request); + String sendOpenSms(String phoneNumber, String nationCode); + String checkOrGenerateRegisterProcessKey(String accountName, String codeKey); void deleteRegisterProcessKey(String codeKey); @@ -29,6 +33,8 @@ public interface SimpleClientApplyService { void saveOrUpdateApplyInfo(JSONObject companyBean, String username); + JSONObject getClientAggregateFile(String username, MultipartFile file,String clean_days) throws IOException; + JSONObject getBankInfo(String bsb_no); void checkAccountName(String contact_phone,String nation_code); diff --git a/src/main/java/au/com/royalpay/payment/manage/application/core/impls/SimpleClientApplyServiceImpl.java b/src/main/java/au/com/royalpay/payment/manage/application/core/impls/SimpleClientApplyServiceImpl.java index 402837155..aac1a001f 100644 --- a/src/main/java/au/com/royalpay/payment/manage/application/core/impls/SimpleClientApplyServiceImpl.java +++ b/src/main/java/au/com/royalpay/payment/manage/application/core/impls/SimpleClientApplyServiceImpl.java @@ -15,6 +15,7 @@ import au.com.royalpay.payment.manage.signin.beans.LoginInfo; import au.com.royalpay.payment.manage.signin.core.SignInAccountService; import au.com.royalpay.payment.manage.support.sms.SmsSender; import au.com.royalpay.payment.manage.system.core.MailGunService; +import au.com.royalpay.payment.tools.connections.attachment.core.AttachmentClient; import au.com.royalpay.payment.tools.env.PlatformEnvironment; import au.com.royalpay.payment.tools.env.SysConfigManager; import au.com.royalpay.payment.tools.exceptions.BadRequestException; @@ -24,20 +25,29 @@ import au.com.royalpay.payment.tools.exceptions.ServerErrorException; import au.com.royalpay.payment.tools.locale.LocaleSupport; import au.com.royalpay.payment.tools.utils.PasswordUtils; +import au.com.royalpay.payment.tools.utils.PdfUtils; +import au.com.royalpay.payment.tools.utils.TimeZoneUtils; +import com.alibaba.fastjson.JSON; import com.alibaba.fastjson.JSONObject; +import org.apache.commons.codec.binary.Base64; import org.apache.commons.lang3.RandomStringUtils; import org.apache.commons.lang3.StringUtils; import org.apache.commons.lang3.time.DateFormatUtils; import org.apache.commons.lang3.time.DateUtils; +import org.slf4j.Logger; +import org.slf4j.LoggerFactory; import org.springframework.data.redis.core.StringRedisTemplate; import org.springframework.stereotype.Service; import org.springframework.transaction.annotation.Transactional; import org.springframework.util.Assert; import org.springframework.web.bind.annotation.RequestMethod; +import org.springframework.web.multipart.MultipartFile; import org.thymeleaf.context.Context; -import java.io.IOException; +import java.awt.image.BufferedImage; +import java.io.*; +import java.math.BigDecimal; import java.net.URISyntaxException; import java.util.*; import java.util.concurrent.LinkedBlockingQueue; @@ -47,6 +57,7 @@ import java.util.stream.Collectors; import javax.annotation.PostConstruct; import javax.annotation.Resource; +import javax.imageio.ImageIO; import javax.servlet.http.HttpServletRequest; import cn.yixblog.platform.http.HttpRequestGenerator; @@ -65,14 +76,21 @@ public class SimpleClientApplyServiceImpl implements SimpleClientApplyService { @Resource private MailService mailService; @Resource + private AttachmentClient attachmentClient; + @Resource private PermissionPartnerManager permissionPartnerManager; @Resource private SpringTemplateEngine thymeleaf; @Resource + private SysClientLegalPersonMapper sysClientLegalPersonMapper; + @Resource private ClientManager clientManager; @Resource private SignInAccountService signInAccountService; @Resource + private SimpleClientApplyService simpleClientApplyService; + private Logger logger = LoggerFactory.getLogger(getClass()); + @Resource private ClientAccountMapper clientAccountMapper; @Resource private SysClientPreMapperMapper sysClientPreMapperMapper; @@ -95,6 +113,7 @@ public class SimpleClientApplyServiceImpl implements SimpleClientApplyService { private ClientBDMapper clientBDMapper; private ThreadPoolExecutor pool = new ThreadPoolExecutor(1, 10, 5, TimeUnit.SECONDS, new LinkedBlockingQueue()); + private final String IMG_AGGREGATE_FILE = "https://file.royalpay.com.au/open/2019/09/06/1567741055646_qeWC7kwqEwsJjRHisJSyAjqnB9nnnh.pdf"; @Resource private SmsSender smsSender; @Resource @@ -158,6 +177,29 @@ public class SimpleClientApplyServiceImpl implements SimpleClientApplyService { return registerClientCode; } + @Override + public String sendOpenSms(String phoneNumber, String nationCode) { + String reidsCheckCodeKey = getRegisterClientRedisKey(phoneNumber); + String value = stringRedisTemplate.boundValueOps(reidsCheckCodeKey).get(); + if (StringUtils.isNotEmpty(value)) { + throw new BadRequestException("SMS has been sent，Please check your messages or try again in 3 minutes."); + } + ArrayList param = new ArrayList<>(); + String registerClientCode = RandomStringUtils.random(6, false, true); + param.add("RoyalPay"); + param.add(registerClientCode); + String expireMin = "3"; + param.add(expireMin); + try { + smsSender.getSender().sendWithParam(nationCode.trim(), phoneNumber, REGISTER_CLIENT_TEMPLID, param, "RoyalPay", "", ""); + } catch (Exception e) { + e.printStackTrace(); + throw new ServerErrorException("Phone number is wrong Please try again"); + } + stringRedisTemplate.boundValueOps(getRegisterClientRedisKey(phoneNumber)).set(registerClientCode, Long.parseLong(expireMin), TimeUnit.MINUTES); + return registerClientCode; + } + @Override public void sendVerifyEmail(String address, int client_id, String username) { JSONObject client = clientManager.getClientInfo(client_id); @@ -301,6 +343,87 @@ public class SimpleClientApplyServiceImpl implements SimpleClientApplyService { } } + public JSONObject getPreApplyInfoForAggree(String username ,String clean_days) { + + JSONObject apply = sysClientPreMapperMapper.findByUserName(username); + + String address = apply.getString("address").trim(); + if (address.contains(",")) { + apply.put("address", address.substring(0, address.lastIndexOf(",")).trim()); + apply.put("address_sub", address.substring(address.lastIndexOf(",") + 1).trim()); + } + apply.put("acn_type", "ABN: (" + apply.getString("abn") + ")"); + apply.put("company_name_acn", apply.getString("company_name") + " (ABN " + apply.getString("abn") + ")"); + apply.put("clean", "T+" + clean_days.trim()); + apply.put("clean_days", clean_days); + JSONObject sysConfig = sysConfigManager.getSysConfig(); + JSONObject test = JSONObject.parseObject(sysConfig.getString("sys_apply_rates")); + + JSONObject rate = test.getJSONObject("t"+clean_days.trim()); + + + apply.put("wechat_rate",rate.getString("Wechat")); + apply.put("alipay_rate",rate.getString("Alipay")); + apply.put("alipay_online_rate",rate.getString("AlipayOnline")); + apply.put("cbbank_rate",rate.getString("CB_Bankpay")); + apply.put("bestpay_rate",rate.getString("Bestpay")); + apply.put("jd_rate",rate.getString("JDpay")); + + JSONObject bankInfo = getBankInfo(apply.getString("bsb_no")); + apply.put("bank", bankInfo.getString("bank")); + apply.put("bsb_no", apply.getString("bsb_no")); + apply.put("account_no", apply.getString("bank_no")); + apply.put("account_name", apply.getString("bank_name")); + + String start_date = DateFormatUtils.format(new Date(), "dd/MM/yyyy"); + apply.put("start_date", start_date); + Date endDate = TimeZoneUtils.nextYearByCurrDay(); + String end_date = DateFormatUtils.format(endDate, "dd/MM/yyyy"); + apply.put("end_date", end_date); + + apply.put("legal_person", apply.getString("representative_person")); + apply.put("legal_job_title", apply.getString("representative_job_title")); + apply.put("legal_phone", apply.getString("representative_phone")); + apply.put("legal_email", apply.getString("representative_email")); + + return apply; + } + + + @Override + public JSONObject getClientAggregateFile(String username, MultipartFile file ,String clean_days) throws IOException{ + JSONObject apply = getPreApplyInfoForAggree(username ,clean_days); + apply.put("full_name", file.getOriginalFilename()); + BufferedImage img = ImageIO.read(file.getInputStream()); + ByteArrayOutputStream out = new ByteArrayOutputStream(); + ImageIO.write(img, "png", out); + apply.put("img","data:image/png;base64," + Base64.encodeBase64String(out.toByteArray())); + + return exportImgAggregateFile(username, apply); + } + + private JSONObject exportImgAggregateFile(String username, JSONObject apply) throws IOException{ + InputStream stream = null; + JSONObject contractInfo = new JSONObject(); + try { + PdfUtils pdu = new PdfUtils(); + pdu.setTemplatePdfPath(IMG_AGGREGATE_FILE); + pdu.setPdfTemplate(apply); + File file = new File(username + "_agreement.pdf"); + ByteArrayOutputStream bos = pdu.templetPdfBos(file,"STSong-Light","UniGB-UCS2-H"); + stream = new ByteArrayInputStream(bos.toByteArray()); + JSONObject fileInfo = attachmentClient.uploadFile(stream, username + "_" + System.currentTimeMillis() + "_agreement.pdf", false); + + contractInfo.put("contract_url",fileInfo.getString("url")); + } catch (Exception e) { + logger.error("合同制作出现问题：", e); + throw new BadRequestException("合同制作出现问题：" + e.getMessage()); + } finally { + stream.close(); + } + return contractInfo; + } + //todo private void applyerToClient(String username) { JSONObject sysConfig = sysConfigManager.getSysConfig(); @@ -343,8 +466,14 @@ public class SimpleClientApplyServiceImpl implements SimpleClientApplyService { sysClient.put("suburb", apply.getString("suburb")); sysClient.put("state", apply.getString("state")); sysClient.put("postcode", apply.getString("postcode")); - sysClient.put("royalpayindustry", apply.getString("industry")); + sysClient.put("royalpayindustry", apply.getString("royalpayindustry"));//修改industry成royalpay + sysClient.put("alipayindustry", apply.getString("alipayindustry")); + sysClient.put("industry", apply.getString("industry"));//微信支付行业 sysClient.put("contact_person", apply.getString("contact_person")); + sysClient.put("contact_job", apply.getString("contact_job")); + sysClient.put("logo_url", apply.getString("logo_url")); + sysClient.put("company_website", apply.getString("company_website")); + sysClient.put("company_photo", apply.getString("company_photo")); sysClient.put("contact_email", apply.getString("contact_email")); sysClient.put("contact_phone", "+61"+apply.getString("contact_phone")); sysClient.put("company_phone", apply.getString("company_phone")); @@ -356,7 +485,7 @@ public class SimpleClientApplyServiceImpl implements SimpleClientApplyService { sysClient.put("approve_time", new Date()); sysClient.put("creator", 0); sysClient.put("business_name", apply.getString("short_name")); - sysClient.put("industry", 331); + /*sysClient.put("industry", 331);*/ sysClient.put("merchant_id", subMerchant.getString("merchant_id")); sysClient.put("sub_merchant_id", subMerchant.getString("sub_merchant_id")); sysClient.put("common_sub_merchant_id", 1); @@ -367,6 +496,18 @@ public class SimpleClientApplyServiceImpl implements SimpleClientApplyService { sysClient.put("ali_sub_merchant_id", clientMoniker); clientMapper.save(sysClient); + JSONObject representativeInfo = new JSONObject(); + representativeInfo.put("client_id", sysClient.getIntValue("client_id")); + representativeInfo.put("representative_person", apply.getString("representative_person")); + representativeInfo.put("job_title", apply.getString("representative_job_title")); + representativeInfo.put("phone", apply.getString("representative_phone")); + representativeInfo.put("email", apply.getString("representative_email")); + representativeInfo.put("address", apply.getString("registered_address")); + representativeInfo.put("suburb", apply.getString("registered_suburb")); + representativeInfo.put("state", apply.getString("registered_state")); + representativeInfo.put("postcode", apply.getString("registered_postcode")); + sysClientLegalPersonMapper.save(representativeInfo); + JSONObject clientBd = new JSONObject(); clientBd.put("client_id", sysClient.getIntValue("client_id")); clientBd.put("bd_id", followBd.getString("manager_id")); @@ -461,6 +602,9 @@ public class SimpleClientApplyServiceImpl implements SimpleClientApplyService { }; pool.execute(task2); + //发送开通短信和邮件 + //simpleClientApplyService.sendOpenSms(apply.getString("contact_phone"),"61"); + //clientManager.sendOpenEmail(sysClient,apply.getString("username"),apply.getString("password")); } private String generateClientMoniker() { diff --git a/src/main/java/au/com/royalpay/payment/manage/application/web/SimpleClientApplyController.java b/src/main/java/au/com/royalpay/payment/manage/application/web/SimpleClientApplyController.java index 59d77997b..4080c2351 100644 --- a/src/main/java/au/com/royalpay/payment/manage/application/web/SimpleClientApplyController.java +++ b/src/main/java/au/com/royalpay/payment/manage/application/web/SimpleClientApplyController.java @@ -3,15 +3,19 @@ package au.com.royalpay.payment.manage.application.web; import au.com.royalpay.payment.manage.application.beans.ClientPreApplyBean; import au.com.royalpay.payment.manage.application.beans.ClientPreApplyStep1Bean; import au.com.royalpay.payment.manage.application.core.SimpleClientApplyService; +import au.com.royalpay.payment.manage.permission.manager.PartnerMapping; +import au.com.royalpay.payment.tools.CommonConsts; import au.com.royalpay.payment.tools.env.SysConfigManager; import com.alibaba.fastjson.JSONObject; import org.apache.commons.lang3.StringUtils; import org.springframework.web.bind.annotation.*; +import org.springframework.web.multipart.MultipartFile; import org.springframework.web.servlet.ModelAndView; import javax.annotation.Resource; import javax.servlet.http.HttpServletRequest; import javax.validation.Valid; +import java.io.IOException; @RestController @RequestMapping("/register") @@ -70,6 +74,15 @@ public class SimpleClientApplyController { simpleClientApplyService.saveOrUpdateApplyInfo(applyBean.insertObject(), username); } + @PostMapping(value = "/clientCompliance/{clientMoniker}/commit_aggregate_file") + @ResponseBody + public JSONObject getClientArregateFile(@RequestParam MultipartFile file, @RequestHeader("User-Agent") String userAgent, HttpServletRequest request) throws IOException { + //这个是上传合同的接口，现在为了测试方便，返回一个带上传url的JSONObject，需要传入username，clean_days，签名图片 + String username = "111"; + String clean_days = "11"; + return simpleClientApplyService.getClientAggregateFile(username, file,clean_days); + } + @GetMapping("/info/bank/{bsb_no}") public JSONObject getBankInfo(@PathVariable String bsb_no, @RequestParam String username, @RequestParam String codeKey) { simpleClientApplyService.checkOrGenerateRegisterProcessKey(username, codeKey); diff --git a/src/main/java/au/com/royalpay/payment/manage/merchants/core/ClientManager.java b/src/main/java/au/com/royalpay/payment/manage/merchants/core/ClientManager.java index e7b2f4372..67b4f3952 100644 --- a/src/main/java/au/com/royalpay/payment/manage/merchants/core/ClientManager.java +++ b/src/main/java/au/com/royalpay/payment/manage/merchants/core/ClientManager.java @@ -82,6 +82,8 @@ public interface ClientManager { void checkAndSendInitEmail(JSONObject manager, String clientMoniker); + void sendOpenEmail(final JSONObject client, String username, String pwd); + // void sendInitEmail(JSONObject account,JSONObject client, String username, String pwd); void markApproveEmailSendStatus(String clientMoniker, JSONObject manager); diff --git a/src/main/java/au/com/royalpay/payment/manage/merchants/core/impls/ClientManagerImpl.java b/src/main/java/au/com/royalpay/payment/manage/merchants/core/impls/ClientManagerImpl.java index 9c6c48c07..7727a4161 100644 --- a/src/main/java/au/com/royalpay/payment/manage/merchants/core/impls/ClientManagerImpl.java +++ b/src/main/java/au/com/royalpay/payment/manage/merchants/core/impls/ClientManagerImpl.java @@ -1185,6 +1185,72 @@ public class ClientManagerImpl implements ClientManager, ManagerTodoNoticeProvid } } + + @Override + public void sendOpenEmail(final JSONObject client, String username, String pwd) { + JSONObject model = new JSONObject(); + model.put("username", username); + model.put("password", pwd); + model.put("client_moniker", client.getString("client_moniker")); + model.put("contact_person", client.getString("contact_person")); + model.put("credential_code", client.getString("credential_code")); + List bds = clientBDMapper.listClientBDInfoAvailable(client.getIntValue("client_id"), new Date()); + // todo Velocity + Context ctx = new Context(); + ctx.setVariable("bds", bds); + ctx.setVariable("password", pwd); + ctx.setVariable("username", username); + ctx.setVariable("client_moniker", client.getString("client_moniker")); + ctx.setVariable("contact_person", client.getString("contact_person")); + ctx.setVariable("credential_code", client.getString("credential_code")); + + final String content = thymeleaf.process("mail/new_client_notice", ctx); + // final String content = VelocityEngineUtils.mergeTemplateIntoString(null, "mail/new_client_notice.vm", + // "utf-8", model); + ctx.setVariable("password", "*****"); + final String contentBd = thymeleaf.process("mail/new_client_notice", ctx); + final List mailTos = new ArrayList<>(); + String mailTo = client.getString("contact_email"); + if (StringUtils.isEmpty(mailTo)) { + throw new EmailException("Client Contact Email is invalid"); + } + mailTos.add(mailTo); + JSONObject clientLegal = sysClientLegalPersonMapper.findRepresentativeInfo(client.getIntValue("client_id")); + if (clientLegal != null && StringUtils.isNotBlank(clientLegal.getString("email"))) { + mailTos.add(clientLegal.getString("email")); + } + + final List emails = new ArrayList<>(); + for (JSONObject bd : bds) { + String email = bd.getString("email"); + if (StringUtils.isNotEmpty(email)) { + emails.add(email); + } + } + new Thread() { + @Override + public void run() { + try { + String emailId = mailService.sendEmail("Your RoyalPay Cross-border Payment has been set up", StringUtils.join(mailTos,","), "", content); + mailService.sendEmail("Your RoyalPay Cross-border Payment has been set up", emails.isEmpty() ? "" : StringUtils.join(emails, ","), + "", contentBd); + JSONObject clientUpdate = new JSONObject(); + clientUpdate.put("client_id", client.getIntValue("client_id")); + clientUpdate.put("approve_email_send", 3); + clientUpdate.put("approve_email_id", emailId); + clientMapper.update(clientUpdate); + } catch (Exception e) { + JSONObject clientUpdate = new JSONObject(); + clientUpdate.put("client_id", client.getIntValue("client_id")); + clientUpdate.put("approve_email_send", 0); + clientUpdate.put("approve_email_id", null); + clientMapper.update(clientUpdate); + throw new EmailException("Email Sending Failed", e); + } + } + }.start(); + } + public void sendInitEmail(final JSONObject client, String username, String pwd) { logger.debug("sending email after comply"); JSONObject model = new JSONObject(); diff --git a/src/main/ui/merchant_application.html b/src/main/ui/merchant_application.html index 2cd8e68d6..b8c23a350 100644 --- a/src/main/ui/merchant_application.html +++ b/src/main/ui/merchant_application.html @@ -33,6 +33,7 @@ + + + +
+ +
+ + +
+
+
+
+
+ +
+ +
+
+ + +
+

+

1

+

1

+

1

+

1

+

CORNWALL STODART

+

Level 10

+

114 William Street

+

DX 636

+

MELBOURNE VIC 3000

+

Telephone: +61 3 9608 2000

+

Facsimile: +61 3 9608 2222

+

Email: j.masterson@cornwalls.com.au

+

Reference: Joel Masterson:1040326

+
+

SERVICES AGREEMENT

+

+

Date

+ + +

+

+

+

This Services Agreement is made on the day it is signed by all parties.

+

+

PARTIES

+

+
+ + +
+ + + + + + + + + + + + + + + + + + +
+

+ 		+

The Supplier

+ 		+

The Client:

+
+

Name:

+ 		+

Tunnel Show Pty Ltd (ACN 601 619 685)

+

trading as RoyalPay

+ 		+ + +

+

+

+

Address:

+ 		+

Level 11
15 William Street
Melbourne VIC3000

+ 		+


{{aggregateFileInfo.address_sub}}

+
+
+ +
+ + +
+

INTRODUCTION

+

+
    +
  • The Supplier is a leading Australian financial technology company dedicated to providing mobile payment platforms to facilitate simple and efficient cross-border payments.
    • +
  • To this end, the Supplier has developed a certain software application and platform which provides Clients (who have web-based gateway APIs (being application programming interfaces) and point-of-sale payment processing and settlement capabilities in the Chinese currency) with a payment integration system, which:
    • +
+
    +
  1. utilises the WeChat Pay payment technology that is owned by Tencent Holdings Limited (China) and that is licensed to the Supplier to facilitate third party payments in Australia;
    2. +
  2. utilises the Alipaypayment technology that is owned by Alipay.com Co., Ltd. (China) and that is licensed to the Supplier to facilitate third party payments in Australia;
    3. +
  3. utilises the BestPaypayment technology that is owned by China Telecom Orange Finance (China) and that is licensed to the Supplier to facilitate third party payments in Australia;
    4. +
  4. utilises theJDpay payment technology that is owned by Chinabank Payment (Beijing) Technology Co., Ltd.and that is licensed to the Supplier to facilitate third party payments in Australia;
    5. +
  5. utilisesthe CB BankPay payment technology licensed to the Supplier by Lakala Payment Co., Ltd, Yeepay Co., Ltd, PnR Data Service Co.,Ltdand other companiesto facilitate third party payments in Australia;
    6. +
  6. processes payments from users of the WeChat Pay, Alipay, BestPay, JDpay, CB BankPay and otherpayment technologies and Chinese bank cardsin Chinese Yuan, converts such payments to the Australian Dollar equivalent and then sends such payments to the Client by utilising settlement functions forming part of the software application;
    7. +
  7. allows the Client to access the merchant management portal feature of the software application which facilitates transaction management, reporting and provides transactional analytics; and
    8. +
  8. provides the Client with opportunity to access to additional unique WeChat Pay marketing features including WeChat Lucky Money (an incentive program where payers randomly receive cashbacks) and WeChat Moment (being social media advertising aimed at enhancing a Clients brand awareness).
    9. +
  9. provides the Client with access to additional Alipay Discovery marketing features such as 12% Off Event (an incentive program where payers randomly receive discount) and Discovery Channel (location based services to attract nearby clients).
    10. +
+

+

(RoyalPay Cross-Border Payment Services)

+
    +
  • The Client wishes to use the RoyalPay Cross-Border Payment Services provided by the Supplier for receiving payments from the Clients customers, for the Clients own goods and/or services provided by the Client to its customers at the Clients own retail outlets and/or through the Clients own website.
    • +
  • The parties agree that the Supplier will supply the Client with the RoyalPay Cross-Border Payment Services in accordance with the terms of this Agreement.
    • +
+

+

OPERATIVE PROVISIONS

+

+

The Parties agree as follows:

+

+

1.Agreement

+
    +
  • 1.1 The Supplier agrees to provide the RoyalPay Cross-BorderPaymentServices (and to provide the Client with any applicable documentationor guidancepertaining to the Clients use of the RoyalPay Cross-Border Payment Services) subject to the terms of this Agreement.
    • +
  • 1.2 The Client agrees to pay to the Supplier the Fees and charges for the RoyalPay Cross-Border Payment Services as set out in Schedule B.
    • +
  • 1.3 This Agreement shall apply to the supply and provision of any and all RoyalPay Cross-Border Payment Services to the Client during the Term.
    • +
+

2.Contract Manager

+
    +
  • 2.1 The Clientmay nominate a manager in Schedule Bor otherwise in writing from time to time to act as the Clients contract manager in dealing with the Supplier under this Agreement (ContractManager).
    • +
  • 2.2 If the Supplier appoints a Contract Manager, the Contract Manager will be the authorised representative of the Supplier for the purposes of this Agreement.
    • +
+

3.Term

+
    +
  • 3.1 This Agreement commences on the Commencement Date and continues for the Initial Term (Term), unless extended under clause 3.2or otherwise terminated earlier in accordance with clause 15.
    • +
  • 3.2 The Term of this Agreement will automatically extend beyond the Initial Term for subsequent rolling 12 month periods (Renewed Term), unless:
    • +
      +
    • (a) either party notifies the other of termination in writing, at least thirty (30) calendar days before the end of the Initial Term or any Renewed Term (as the case may be); or
      • +
    • (b) this Agreement is terminated earlier pursuant to clause 15.
      • +
    +
+

4.Acceptance Testing

+
    +
  • 4.1 The Client shall conduct and complete all Acceptance Testing as soon as practicable but within five (5) Business Days of the delivery of the RoyalPay Cross-Border Payment Services by the Supplier. The Client will allow the Supplier to be present at any Acceptance Testing, provided that the Supplier gives the Client sufficient notice of its wish to be present.
    • +
  • 4.2 Where, during Acceptance Testing and for a reasonable period after Acceptance Testing is completed, the Client encounters any malfunction, defect or suspected error in the Suppliers RoyalPay Cross-Border Payment Services, the Supplier will correct any such malfunction, defect and suspected errors as soon as practicable.
    • +
  • 4.3 If the Supplier disputes the validity of the Acceptance Testing, the parties agree to resolve the dispute as set out in clause 17.
    • +
  • 4.4 In the event of a malfunction, defect or suspected error relating to the integration of a product or service supplied to the Supplier by a third party, the Supplier will provide reasonable and prompt assistance to the Client to identify the problem and who is responsible for resolving it.
    • +
+

5.Delivery and Provision of RoyalPay Cross-Border Payment Services

+
    +

    5.1 The Client engages the Supplierto provide the RoyalPay Cross-Border Payment Services and the Supplier agrees to use reasonable endeavours to provide the RoyalPay Cross-Border Payment Services(together with any applicable documentation or guidance pertaining to the Clients use of the RoyalPay Cross-Border Payment Services)to the Client, in accordance with the terms and conditions of this Agreement.

    +
  • 5.2 The Supplier shall endeavour to provide a reasonably commercial level of availability of the RoyalPay Cross-Border Payment Services for twenty-four (24) hours a day, seven (7) days a week, with at 99.98% up time (annualised), excluding:
    • +
      +
    • (c) any planned maintenance periods of which the Supplier will provide the Client with at least seven (7) Business Days prior written notice of;
      • +
    • (d) any unscheduled maintenance periods which the Supplier will endeavour to perform outside of the Suppliers normal business hours. In situations where unscheduled maintenance is required, the Supplier shall use its best efforts to provide the Client with at least six (6) hours notice in advance of such maintenance taking place; and
      • +
    • (e) any communications, banking, terminal and external systems failures which are outside of the control of the Supplier.
      • +
    +
  • 5.3 The Supplier shall, as part of the provision of the RoyalPay Cross-Border Payment Services, provide to the Client (at no additional cost to the Client) standard customer support during the Suppliers normal business hours in accordance with the Suppliers Service Level Agreement (SLA) which is operative during the Term. In particular, the Supplier shall provide the Client with Level 1, 2 and 3 support (as detailed in the SLA) as part of the provision of the RoyalPay Cross-Border Payment Services.
    • +
  • 5.4 Further to clause 5.3, the Client may (in its sole discretion) elect to purchase additional and/or enhanced support services which shall be provided by the Supplier at the Suppliers hourly rate applicable at the relevant time.
    • +
  • 5.5 The Client acknowledgesthat the Supplieris providing the RoyalPay Cross-Border Payment Services to the Client on a non-exclusive basis and that the Supplier may provide services of the same or a similar nature to any third party.
    • +
  • 5.6 The Suppliermay provide the RoyalPay Cross-Border Payment Services in the manner determined by it in its absolute and sole discretion, so longas in doing so, it does not breach any material provision of this Agreement.
    • +
  • 5.7 The parties acknowledge that the Supplier has entered this Agreement with the Client on the basis that the RoyalPay Cross-Border Payment Services utilise the WeChat Pay payment technology licensed to the Supplier by Tencent Holdings Limited (China). The parties agree that, should the WeChat Pay payment technology become unavailable to the Supplier (for any reason whatsoever), the Supplier shall be entitled, without penalty, to immediately terminate this Agreement by providing written notice of such termination to the Client.
    • +
  • 5.8 The parties acknowledge that the Supplier has entered this Agreement with the Client on the basis that the RoyalPay Cross-Border Payment Services utilise the Alipay payment technologylicensed to the Supplier by Alipay.com Co., Ltd.. The parties agree that, should the Alipaypayment technology become unavailable to the Supplier (for any reason whatsoever), the Supplier shall be entitled, without penalty, to immediately terminate this Agreement by providing written notice of such termination to the Client.
    • +
  • 5.9 The parties acknowledge that the Supplier has entered this Agreement with the Client on the basis that the RoyalPay Cross-Border Payment Services utilise the BestPaypayment technology licensed to the Supplier by China Telecom Orange Finance. The parties agree that, should the BestPaypayment technology become unavailable to the Supplier (for any reason whatsoever), the Supplier shall be entitled, without penalty, to immediately terminate this Agreement by providing written notice of such termination to the Client.
    • +
  • 5.10 The parties acknowledge that the Supplier has entered this Agreement with the Client on the basis that the RoyalPay Cross-Border Payment Services utilise the JDpaypayment technology licensed to the Supplier by Chinabank Payment (Beijing) Technology Co., Ltd. The parties agree that, should the JDpaypayment technology become unavailable to the Supplier (for any reason whatsoever), the Supplier shall be entitled, without penalty, to immediately terminate this Agreement by providing written notice of such termination to the Client.
    • +
  • 5.11 The parties acknowledge that the Supplier has entered this Agreement with the Client on the basis that the RoyalPay Cross-Border Payment Services utilise the CB BankPay payment technology licensed to the Supplier byLakala Payment Co., Ltd, Yeepay Co., Ltd, PnR Data Service Co.,Ltd and other companies. The parties agree that, should the CB BankPay payment technology become unavailable to the Supplier (for any reason whatsoever), the Supplier shall be entitled, without penalty, to immediately terminate this Agreement by providing written notice of such termination to the Client.
    • +
  • 5.12 The parties acknowledge that at any time, the Supplier may become licensed to use other payment technologies to provide the RoyalPay Cross-Border Payment Services, in which event the Supplier will endeavour to provide notice together with any applicable rates and details to the Client.
    • +
  • 5.13 The Client acknowledges that:
    • + +
      +
    • the RoyalPay Cross-Border Payment Services consists of complex software which may never be wholly free from defects, errors, bugs and compatibility issues and, in this respect, the Supplier gives no warranty or representation that the software pertaining to the RoyalPay Cross-Border Payment Services will be wholly free from such defects, errors, bugs or compatibility issues;
      • +
    +

    +
      +
    • complex software may be applied by the Supplier when upgrading existing functionalities of the RoyalPay Cross-Border Payment Services and, where this occurs, the Client shall not be subject to any additional fees or charges as a result of such upgrade, except where such upgrade introduces new functionalities to the RoyalPay Cross-Border Payment Services for which the Client will be notified in advance; and
      • +
    +

    +
      +
    • the Supplier will not, and does not, purport to provide any legal, accountancy, taxation or any other financial advisory services under this Agreement or in relation to the RoyalPay Cross-Border Payment Services, except as otherwise expressly provided herein.
      • +
    +

    +
  • 5.14 The Supplier has no obligation to the Client to rectify any defect or fault in the RoyalPay Cross-Border Payment Services caused or contributed to by:
    • +
      +
    • (a)the acts or omissions of the Client or the Clients Personnel; or
      • +
    • (b)faults or defects that arise in telecommunication services provided to the Client by a third party supplier other than such suppliers engaged or contracted by the Supplier, regardless of whether the costs associated with such services are paid or reimbursed by the Client or relate specifically to the RoyalPay Cross-Border Payment Services provided to the Client.
      • +
    +
+

6.RoyalPay Cross-Border Payment Services Fees, Settlement Terms and Refunds

+
    +
  • 6.1 The details relating to Fees pertaining to the RoyalPay Cross-Border Payment Services, as well as the settlement terms for remittance of payments to the Client that have been made by the Clients customers and the terms and conditions regarding refunds are described in Schedule B.
    • +
  • 6.2 If the Client fails to pay the Fees to the Supplier in accordance with the Payment Terms, the Client is liable to pay the Supplier:
    • +
      +
    • (a)interest at the interest rate set out under the Penalty Interest Rate Act 1983 (Vic)from time to time, calculated daily, on all outstanding amounts from the date upon which payment was due until payment is received by the Supplier in full; and
      • +
    • (b)all reasonable costs and expenses incurred by the Supplier (including legal costs on a full indemnity basis) in relation to the recovery of the Fees and interest from the Client.
      • +
    +
  • 6.3 For the avoidance of doubt, the Client will not be liable for Fees which are not described in Schedule B, other than those that may be agreed to by the Client in writing from time to time.
    • +
  • 6.4 Unless otherwise agreed by the parties in writing, all expenses incurred by the Supplier in the provision of the RoyalPay Cross-Border Payment Services are to be borne by the Supplier.
    • +
  • 6.5 The Supplier may reissue an invoice if any error in the invoice is later discovered. Where:
    • +
      +
    • (a)the Client has overpaid any Fees as a result of such an error, the Clients accountwill be credited with the overpayment or, if the Client has stopped acquiring the RoyalPay Cross-Border Payment Services from the Supplier, the Supplier will refund the overpayment promptly after the Clients request but after deduction of any other amounts due by theClient; or
      • +
    • (b)the Client has underpaid any charges as a result of the error, the Client will be required to pay the correct amount to the Supplier after the invoice is reissued in accordance with the Payment Terms.
      • +
    +
  • 6.6 In the event that the Client fails to promptly notify the Supplier of any changes to, or termination of, its business or contact method which materially impacts the Suppliers settlement process for remittance of payments to the Client, and where the Supplier receives no response from the Client within three (3) Business Days after contacting the Client to ascertain this information, then the Supplier may, upon a customers request and in relation to payments already made by a customer but not yet settled with the Client, disburse or refund such payment directly to the customers nominated account.
    • +
  • 6.7 It would not be settled on both public holidays of Australia and China.
    • +

    + 6.8 In the case of special circumstances, it is subjected to Supplier liquidation notice (e-mail, WeChat, management platform, App and other channels) +
+

7.GST

+
    +
  • 7.1 Unlessotherwise stated in Schedule B, the charges and other amounts payable by the Clientunder this Agreement are calculated or expressedexcludingGST.
    • +
  • 7.2 The Supplier warrants that it is registered for GST and will remain so registered for the duration of the Agreement.
    • +
  • 7.3 The Client warrants that it is registered for GST and will remain so registered for the duration of the Agreement.
    • +
+

8.Supplier Obligations, Warranties and Representations

+
    +
  • 8.1 The Supplier shall be solely responsible for the establishment, integration, operation and management of the RoyalPay Cross-Border Payment Services in accordance with established administrative rules, system functionalities and other applicable terms and conditions, and shall provide all necessary trainings and documentations to facilitate the understanding and operation of Supplier's products and services provided.
    • +
  • 8.2 In addition, the Supplier shall be responsible for receiving, addressing and resolving any complaints that may arise from defects pertaining to the RoyalPay Cross-Border Payment Services.
    • +
  • 8.3 The Supplier represents and warrants that the RoyalPay Cross-Border Payment Services:
    • +
      +
    • (a)do not infringe the Intellectual Property Rights of any third party, other than with respect to the WeChat Pay payment technology that is owned by Tencent Holdings Limited (China), the Alipay payment technology that is owned by Alipay.com Co., Ltd., the BestPaypayment technology that is owned by China Telecom Orange Finance, the JDpay payment technology that is owned by Chinabank Payment (Beijing) Technology Co., Ltd.And the CB BankPay payment technology that is owned by Lakala Payment Co., Ltd, Yeepay Co., Ltd, PnR Data Service Co.,Ltdand other companies; and
      • +
    • (b)will be supplied:
      • +
        +
      • (i)in accordance with the terms of this Agreement,
        • +
      • (ii)in a professional and timely manner, in accordance with best industry practices, and with reasonable care and skill; and
        • +
      • (iii)in accordance with all relevant Laws.
        • +
      +
    +
  • 8.4 The Supplier warrants that it will provide necessary customer support functions relating to business and system enquiries and relating to the RoyalPay Cross-Border Payment Services to the Client in accordance with the terms of the SLA.
    • +
  • 8.5 The Supplier is fully authorised in all commercial and technical capacities by Tencent Holdings Limited (China) to offer the WeChat Pay payment gateway to users in Australia.
    • +
  • 8.6 The Supplier is fully authorised in all commercial and technical capacities by Alipay.com CO., Ltd. (China) to offer the Alipay payment gateway to users in Australia.
    • +
  • 8.7 The Supplier is fully authorised in all commercial and technical capacities by China Telecom Orange Finance (China) to offer the BestPaypayment gateway to users in Australia.
    • +
  • 8.8 The Supplier is fully authorised in all commercial and technical capacities by Chinabank Payment (Beijing) Technology Co., Ltd. to offer the JDpaypayment gateway to users in Australia.
    • +
  • 8.9 The Supplier is fully authorised in all commercial and technical capacities by Lakala Payment Co., Ltd, Yeepay Co., Ltd, PnR Data Service Co.,Ltdand other companiesto offer the CB BankPay payment gateway to users in Australia.
    • +
  • 8.10 The Supplier:
    • +
      +
    • does not represent, warrant or guarantee that any Service will be free of interruptions, delays, faults or errors; and
      • +
    +

    +
      +
    • except as expressly provided in this Agreement, is not liable to the Client or any other third party for any interruptions, delays, faults or errors in connection with the supply of the RoyalPay Cross-Border Payment Services (in part or in full).
      • +
    +

    +
  • 8.11 The Supplier agrees that it will not employ any reverse engineering method aimed at deciphering any computer system or procedures operated by the Client and the Supplier further agrees that it will not copy, amend edit, consolidate, or alter the said computer systems or procedures (including, without limitation, any source programs, object programs, software files, data processing in local computer storage devices, data from the Clients terminals which is transmitted to servers, server data, etc.).
    • +
  • 8.12 The parties agree that the Supplier may, provided the Client has given its express written consent to do so, promote the RoyalPay Cross-Border Payment Services and its business association with the Client by using the Clients name, trademark, marketing materials and any such like details.
    • +
  • 8.13 The Supplier represents and warrants, as at the date of this Agreement, that:
    • +
      +
    • (a)it has the power and has taken all corporate and other action required, to enter into this Agreement and to authorise the execution and delivery of this Agreement and the performance of the Suppliers obligations under this Agreement;
      • +
    • (b)this Agreement constitutes a valid and legally binding obligation of the Supplier in accordance with its terms except to the extent of discretions of courts regarding the availability of equitable remedies and Laws affecting creditors rights generally; and
      • +
    • (c)the execution, delivery and performance of this Agreement does not violate any existing Law or any document or agreement to which the Supplier is a party or which is binding on the Supplier or any of its assets.
      • +
    +
  • 8.14 The Supplier acknowledges that all representations, covenants and warranties in this Agreement are provided on an ongoing basis and will survive the execution, performance and termination of this Agreement.
    • +
  • 8.15 The Suppler is an Australian company incorporated in Melbourne, Victoria and is classified as a finance service company with the official status of Authorised Representative of Flexewallet Pty Ltd (ACN 164 657 032 and Australian Financial Services Licensee 448066) and is legally bound by various compliance regimes for the delivery of services such as the RoyalPay Cross-Border Payment Services.
    • +
+

9.Client Obligations, Warranties and Representations

+
    +
  • 9.1 The Client must:
    • +
      +
    • (a)ensure that, in respect of the RoyalPay Cross-Border Payment Services, the Client meets, and continues to meet all pre-requisites or conditions for supply of the RoyalPay Cross-Border Payment Services;
      • +
    • (b)ensure that its network and systems comply with the relevant specifications provided by the Supplier from time to time and, in this respect, the Client shall be solely responsible for procuring and maintaining its network connections and telecommunications link from its systems to the Suppliers system. The Client is required to notify the Supplier of any system changes that might impact the RoyalPay Cross-Border Payment Services and allow the Supplier to perform any necessary system testing to ensure the full integrity of RoyalPay Cross-Border Payment Services is maintained.
      • +
    • (c)use the RoyalPay Cross-Border Payment Services for its intended purpose;
      • +
    • (d)perform all tasks and provide all materials required of it, and by the dates specified, in this Agreement;
      • +
    • (e)co-operate with the Supplier to allow the Supplier to provide the RoyalPay Cross-Border Payment Services and ensure that the Clients procedures for handling orders and delivering goods and/or services are compatible with the settlement process that forms part of the RoyalPay Cross-Border Payment Services;
      • +
    • (f)provide the Supplier with accurate information regarding the commercial aspects of the Client such as changes to company ownership, corporate structure, business domicile and website details and details of products and/or services offered by the Client which may materially affect the scope of the RoyalPay Cross-Border Payment Services;
      • +
    • (g)provide the Supplier with all information in the Clients possession, custody or control that the Supplier reasonably requires to provide the RoyalPay Cross-Border Payment Services and ensure that all information it gives to the Supplier is correct, current and complete;
      • +
    • (h)in the event that the Supplier reasonably believes or has been given notice of an unauthorised or fraudulent use of the RoyalPay Cross-Border Payment Services, provide the Supplier with all information in the Clients possession, custody or control which may be relevant to the unauthorised or fraudulent use;
      • +
    • (i)comply with all applicable Laws, regulations, codes and standards (including any technical standards of a Government Agency);
      • +
    • (j)comply with all requirements, documentation, user manuals and specifications referred to in the Schedules and any additional documents that are provided by the Supplier to the Client and which the Client has agreed in writing to be bound by, such agreement not to be unreasonably withheld;
      • +
    • (k)conduct and retain backups of any of the Clients data (whether hosted on the Suppliers systems or provided to the Supplier in connection with the RoyalPay Cross-Border Payment Services) to the extent reasonable, having regard to the nature of the data;
      • +
    • (l)immediately report to the Supplier, in writing, any unauthorised use of the RoyalPay Cross-Border Payment Services;
      • +
    • (m)use its best endeavours to display (in accordance with directions of the Supplier) relevant visual merchandise items such as trademarks, logos, branding and advertising materials of the Supplier pertaining to the RoyalPay Cross-Border Payment Services provided pursuant to this Agreement in prominent positions and on the Clients website
      • +
    • (n)not:
      • +
        +
      • (i)employ any reverse engineering method aimed at deciphering any computer system or procedures operated by the Supplier and the Client further agrees that it will not copy, amend edit, consolidate, or alter the said computer systems or procedures (including, without limitation, any source programs, object programs, software files, data processing in local computer storage devices, data from the Suppliers terminals which is transmitted to servers, server data, etc.). In addition, the Client agrees that it will not alter or amend the original functions of the software pertaining to the RoyalPay Cross-Border Payment Services or add further functions to the software pertaining to the RoyalPay Cross-Border Payment Services.
        • +
      • (ii)unreasonably delay any action, approval, direction, determination or decision which is reasonably required of the Client under this Agreement or for the Supplier to provide the RoyalPay Cross-Border Payment Services;
        • +
      • (iii)engage in, or procure, assist or allow any of its Personnel or any other person to engage in, any fraudulent or unauthorised use of the RoyalPay Cross-Border Payment Services. If the Client engages in any such use of the RoyalPay Cross-Border Payment Services, the Client must report such use to the Supplier as soon as it becomes aware of such use; or
        • +
      • (iv)engage in unlawful, harmful, threatening, defamatory, infringing, obscene, harassing, sexually explicit or racially offensive activities or facilitate illegal activities, promote unlawful violent or cause damage or injury to any person or property.
        • +
      +
    +
  • 9.2 The Client shall be solely responsible for:
    • +
  • (a)understanding how to access and use the RoyalPay Cross-Border Payment Services;
    • +
  • (b)each of its Personnel who have access to, or use of, the RoyalPay Cross-Border Payment Services;
    • +
  • (c)any use of the RoyalPay Cross-Border Payment Services, or instruction or direction given, through the Clients login and/or using the Clients passwords;
    • +
  • (d)any use of the RoyalPay Cross-Border Payment Services by the Clients Personnel which is fraudulent or not authorised by the Client or the Supplier;
    • +
  • (e)implementing and maintaining the security of the Clients network and systems. The Client is liable for all Fees resulting from any use of the RoyalPay Cross-Border Payment Services by any person, whether or not authorised by the Client, resulting from a virus, trojan, worm or other malicious computer code, denial of service attacks, a hacking incident (including a SIM, PABX, IP PBX or SIP Gateway device hack), or other means of exploiting a weakness in the Clients network, systems or security measures.
    • +
  • 9.3 Upon request from the Supplier, the Client must (in accordance with various compliance obligations including those set out in the Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (Cth)and the Corporations Act 2001 (Cth)), duly provide to the Supplier within five (5) Business Days of receiving a request from the Supplier, all necessary documentation relating to Know Your Customer / Know Your Customers Business, including (but not limited to) company ultimate beneficial ownership details and identifications, evidence of incorporation, compliance AML/CTF programs and any licensing registrations(if applicable), etc.). Notwithstanding any other clause in this Agreement, failure by the Client to provide such required documentation may result in the immediate termination of this Agreement by the Supplier. Information provided to the Supplier by the Client pursuant to this clause shall be retained by the Supplier for a period of at least seven (7) years.
    • +
  • 9.4 The Client acknowledges and agrees that the Supplier is not liable (whether in contract, tort or otherwise) whatsoever for any Loss suffered or incurred by the Client as a result, whether directly or indirectly, of any fact, matter or circumstance that is within the responsibility of the Client under this clause except to the extent caused or contributed to by the Supplier.
    • +
  • 9.5 The Client acknowledges and agrees that:
    • +
  • (a)if the Supplier acquires products or services from any supplier including a carrier (as defined under the Telecommunications Act) in connection with the supply of the RoyalPay Cross-Border Payment Services, the Client will comply with all reasonable directions given by the Supplier as are necessary for the Supplier to comply with its obligations under any agreement with that Supplier;
    • +
  • (b)the Supplier may:
    • +
      +
    • (i)be required by Law, to retain metadata, information and other content in relation to the Clients use of the RoyalPay Cross-Border Payment Services, intercept the Clients communications and pass on details of the Clients use of the RoyalPay Cross-Border Payment Services (including any retained metadata, information and content) to a Government Agency, a law enforcement authority or other authority;
      • +
    • (ii)monitor the Clients usage of the RoyalPay Cross-Border Payment Services including where requested, or directed, to do so by a Government Agency, a law enforcement authority or other authority; and
      • +
    • (iii)investigate any alleged misuse of the RoyalPay Cross-Border Payment Services by the Client including where requested, or directed, to do so by a Government Agency, a law enforcement authority or other authority.
      • +
    +
  • If the Supplier is so required to retain, intercept, monitor or investigate, then the Supplier will immediately provide the Client with written notice to the extent that the Supplier is permitted to do so by Law.
    • +
  • 9.6 The supply of the RoyalPay Cross-Border Payment Servicesmay rely on:
    • +
      +
    • (a)systems, networks, infrastructure and services provided by a third party (whether or not that third party has an agreement or understanding with the Client) including a third party who provides carriage services; and
      • +
    • (b)the Clients systems, networks and infrastructure (Third Party Facilities).
      • +
    +
  • 9.7 Without limiting any other provision of this Agreement, the Client acknowledges and agrees that:
    • +
      +
    • (a)due to reasons beyond the Suppliers control, a defect or failure in one or more Third Party Facilities may cause a delay, failure or interruption to the RoyalPay Cross-Border Payment Services;
      • +
    • (b)without limiting the Clients entitlements under the SLA, the Supplier is not liable to the Client in any way for any Loss (including Consequential Loss) that the Client may incur or suffer as a result of any such delay, failure or interruption; and
      • +
    • (c)if the Client requires the Supplier to undertake any remedial work to repair the RoyalPay Cross-Border Payment Services affected by such a delay, failure or interruption, the Supplier may charge the Client, and the Client must pay, an additional charge, the amount of which will be agreed in advance, for the remedial work that the Supplier undertakes. The Client acknowledges that in some cases the agreed additional charge will be payable by the Client even if the Supplier commences such remedial work and only discovers, after commencing such remedial work, that the delay, failure or interruption to the RoyalPay Cross-Border Payment Services was caused by a defect or failure in Third Party Facilities.
      • +
    +
  • 9.8 The Client represents and warrants to the Supplier that, as at the date this Agreement is formed:
    • +
      +
    • (a)it has had the opportunity to obtain independent professional advice in relation to the legal, taxation, accounting and financial consequences of this Agreement, and has not relied on the Supplier in relation to any of those matters; and
      • +
    • (b)where the Supplier has provided the Client with information about any of the Suppliers Personnel, each of the Personnel has consented to the Client disclosing the information to the Supplier and for the Supplier to use, or disclose, the information to provide the RoyalPay Cross-Border Payment Services and exercise any rights and perform any obligations in respect of the RoyalPay Cross-Border Payment Services.
      • +
    • (c)it has the power and has taken all corporate and other action required, to enter into this Agreement and to authorise the execution and delivery of this Agreement and the performance of the Clients obligations under this Agreement;
      • +
    • (d)this Agreement constitutes a valid and legally binding obligation of the Client in accordance with its terms except to the extent of discretions of courts regarding the availability of equitable remedies and Laws affecting creditors rights generally; and
      • +
    • (e)the execution, delivery and performance of this Agreement does not violate any existing Law or any document or agreement to which the Client is a party or which is binding on the Client or any of its assets.
      • +
    +
  • 9.9 The Client acknowledges and agrees that the Supplier has the right to permanently or temporarily cease providing the RoyalPay Cross-Border Payment Services, withhold any monies payable to the Client under this Agreement (including unsettled funds), suspend the operation of this Agreement or terminate this Agreement in accordance with clause 15:
    • +
      +
    • (a)if the Supplier suspects on reasonable grounds that the Client does not comply with all applicable Laws, regulations, codes and standardsrequired to provide the RoyalPay Cross-Border Payment Services and the Client fails within a reasonable time or refuses to provide information or documents sufficient to demonstrate that it does comply with all such laws and standards; or
      • +
    • (b)if the Supplier suspects on reasonable grounds that the Client has fraudulently or otherwise misused the RoyalPay Cross-Border Payment Services and the Client fails within a reasonable time or refuses to provide information or documents sufficient to demonstrate that it has not committed such activities; or
      • +
    • (c)if the Client has failed or refused to comply with any of its obligations under this clause 9.
      • +
    +
  • 9.10 The parties acknowledge and agree that in the event an investigation is carried out by the Supplier under clause 9.5(b) and it is reasonably concluded that the Client has fraudulently or otherwise misused the RoyalPay Cross-Border Payment Services causing loss to the Supplier:
    • +
      +
    • (a)the Supplier may issue a written notice to the Client to:
      • +
        +
      • (i)transfer a sum to the Supplier sufficient to cover the loss that the Supplier has or is expected to incur (including any amounts the Supplier has refunded to third parties affected by the Clients misuse of the RoyalPay Cross-Border Payment Services); or
        • +
      • (ii)refund a sum directly to any third parties affected by the Clients misuse of the RoyalPay Cross-Border Payment Services;
        • +
      +
    • (b)the Client is deemed to have given express authorisation to the Supplier to offset or otherwise apply any unsettled funds ordinarily payable to the Client for the purpose of making good any loss caused to the Supplier by the Clients misuse of the RoyalPay Cross-Border Payment Services.
      • +
    +
  • 9.11 The Client acknowledges that all representations, covenants and warranties in this Agreement are provided on an ongoing basis and will survive the execution, performance and termination of this Agreement.
    • +
+

10.Confidential Information

+
    +
  • 10.1 Subject to clause 10.2each party must:
    • +
      +
    • (a)keep confidential the Confidential Information of the other party and must ensure that it does not disclose or permit the disclosure of that Confidential Information to any person; and
      • +
    • (b)take all steps and do all things that are reasonably necessary or prudent or desirable in order to safeguard the confidentiality of the Confidential Information of the other party.
      • +
    +
  • 10.2 A party may disclose the Confidential Information of the other party:
    • +
      +
    • (a)to its Affiliates, employees, agents, advisers or financiers (each a Recipient) if, and only if:
      • +
        +
      • (i)the Recipient reasonably needs to know that Confidential Information in order for that party to comply with is obligations under this Agreement;
        • +
      • (ii)that party has informed the Recipient of the obligations of confidentiality under this Agreement; and
        • +
      • (iii)the Recipient has accepted the obligation to treat the Confidential Information as confidential in the same manner and to the same extent as required of that party;
        • +
      +
    • (b)with the consent of the other party;
      • +
    • (c)in connection with legal or other proceedings relating to this Agreement; or
      • +
    • (d)if compelled by Law or by a Government Agency, court, tribunal or stock exchange.
      • +
    +
  • 10.3 Notwithstanding clause 10.1, each party may:
    • +
      +
    • (a)disclose the other partys Confidential Information to any third party where it is necessary, on a need to know basis, in order to perform this Agreement; and
      • +
    • (b)use or disclose the other partys Confidential Information to make contact with, or to deal directly with, the Clients end users and other Personnel in connection with the provision and invoicing of the RoyalPay Cross-Border Payment Services;
      • +
    +
  • 10.4 For the purposes of this clause, the terms of this Agreement will be considered Confidential Information of each party.
    • +
  • 10.5 The rights and obligations of each party pursuant to this clause, survive the expiry or termination of this Agreement.
    • +
+

11.Intellectual Property

+
    +
  • 11.1 Any Intellectual Property Rights owned by either party prior to entry into this Agreement, or developed independently of this Agreement by either party, will continue to be owned by that party. In particular, all Intellectual Property Rights pertaining to the RoyalPay Cross-Border Payment Services will at all times remain the sole and exclusive property of the Supplier.
    • +
  • 11.2 None of the Suppliers Intellectual Property Rights are transferred to the Client and, unless specifically authorised by this Agreement, the Client cannot and will not use or reproduce such Intellectual Property Rights for any purpose unconnected with this Agreement.
    • +
  • 11.3 The rights and obligations of each party pursuant to this clause survive the expiry or termination of this Agreement.
    • +
  • 11.4 The Supplier will not infringe the Intellectual Property rights of the Client or any other person in the provision of the RoyalPay Cross-Border Payment Services.
    • +
  • 11.5 If either party becomes aware of any infringement or potential infringement of the other partys Intellectual Property Rights, it must immediately notify the other party.
    • +
  • 11.6 Neither party will remove or modify any Intellectual Property Rights labels or ownership designations or symbols from any of the other partys information or data, including the TM, ® or © symbols.
    • +
+

12.Privacy

+
    +
  • 12.1 Each party must comply with the Privacy Act 1988 (Cth) in respect of any personal or sensitive information (as those terms are defined in the Privacy Act 1988 (Cth)) to which it obtains access as a result of its performance of this Agreement.
    • +
+

13.Subcontractors

+
    +
  • 13.1 The Supplier may not sub-contract the whole or any part of its obligations under this Agreement without the prior written consent of the Client, such consent not to be unreasonably withheld but on such reasonable conditions as the Client may impose and such consent may be withdrawn or varied by the Client in its absolute discretion.
    • +
  • 13.2 Prior to engaging any approved subcontractor, the Supplier must enter into agreements with that approved subcontractor that must include terms necessary or desirable for the Supplier to comply with all of its obligations under this Agreement.
    • +
  • 13.3 The Clients consent to a sub-contract will not relieve the Supplier of any liability, obligation, guarantee or indemnity under this Agreement. The Supplier will be liable to the Client for the acts or omissions (including negligent acts or omissions) of all subcontractors and their employees and agents as fully as if they were the acts or omissions of the Supplier or any of its employees or agents.
    • +
+

14.Restraint

+
    +
  • 14.1 Neither party will ridicule or disparage the other.
    • +
  • 14.2 The Client acknowledges that the Supplier has the exclusive right to supply the WeChat Pay/Alipay/BestPay/JDpay/CB BankPaypayment technology in Australia and consequently the Client acknowledges and agrees that it is restrained from entering into any agreement with third parties relating to the provision of a service similar to the RoyalPay Cross-Border Payment Services. The exclusivity shall remain in effect for twelve (12) months from the Commencement Date of this Agreement.
    • +
+

15.Termination

+
    +
  • 15.1 Without prejudice to any other rights or remedies to which the parties may be entitled, either party (TerminatingParty) may immediately terminate this Agreement without liability to the other (Non-TerminatingParty) in the event that the Non-Terminating Party:
    • +
      +
    • (a)commits a material breach of any of the terms of this Agreement and (if such a breach is remediable) fails to remedy that breach within thirty (30) calendar days of the Non-Terminating Party being notified in writing of the breach by the Terminating Party; or
      • +
    • (b)an order is made or a resolution is passed for the winding up of the Non-Terminating Party, or circumstances arise which entitle a court of competent jurisdiction to make a winding-up order in relation to the Non-Terminating Party; or
      • +
    • (c)an order is made for the appointment of an administrator to manage the affairs, business and property of the Non-Terminating Party, or documents are filed with a court of competent jurisdiction for the appointment of an administrator of the Non-Terminating Party, or notice of intention to appoint an administrator is given by the Non-Terminating Party or its directors; or
      • +
    • (d)a receiver is appointed of any of the Non-Terminating Party's assets or undertaking, or if circumstances arise which entitle a court of competent jurisdiction or a creditor to appoint a receiver or manager of the Non-Terminating Party, or if any other person takes possession of or sells the Non-Terminating Partys assets; or
      • +
    • (e)the Non-Terminating Party makes any arrangement or composition with its creditors, or makes an application to a court of competent jurisdiction for the protection of its creditors in any way; or
      • +
    • (f)the Non-Terminating Party ceases, or threatens to cease, to trade; or
      • +
    • (g)the Non-Terminating Party takes or suffers any similar or analogous action in any jurisdiction in consequence of debt.
      • +
    +
  • 15.2 Upon the termination of this Agreement for any reason:
    • +
      +
    • (a)the supply of the RoyalPay Cross-Border Payment Services provided by the Supplier to the Client pursuant to this Agreement shall cease immediately;
      • +
    • (b)each party shall return and make no further use of any equipment, property, documentation and other relevant items (including copies) belonging to the other party; and
      • +
    • (c)each party shall settle all unpaid invoices and expenses incurred under this Agreement.
      • +
    +
  • 15.3 The provisions of Clause 15.1 notwithstanding, the client may terminate this Agreement upon 30 days written notice to the supplier.
    • +
+

16.Liability and Indemnity

+
    +
  • 16.1 Subject to clauses 16.2to 16.11(inclusive), each party indemnifies, holds harmless and keeps indemnified the other party against any Loss incurred or suffered by the indemnified party, resulting directly from any breach by the party providing the indemnity of any provision of this Agreement or any act, omission, misconduct or negligence of the party providing the indemnity, including (without limitation) any costs incurred in enforcing this indemnity.
    • +
  • 16.2 Without limiting any other provision in this Agreement, the Client shall fully indemnify, hold harmless and defend Flexewallet Pty Ltd (Flexewallet Pty Ltd AFSL #448066 which is a wholly owned subsidiary of publicly listed company Novatti Group Limited ASX code: NOV, both incorporated in Melbourne Australia and which has officially registered the Supplier as an Authorised Representative of their licensing regime in order to enable the offering of non-cash products and services) and its directors, officers, employees, agents, shareholders and related bodies corporate from and against all claims, demands, actions, suits, damages, liabilities, losses, settlements, judgments, costs and expenses (including but not limited to reasonable legal fees), whether or not involving a third party claim, which arise out of or relate to:
    • +
      +
    • (a)any breach of any representation or warranty of the Client contained in this Agreement;
      • +
    • (b)any breach or violation of any term, covenant, undertaking or other obligation or duty under this Agreement or under applicable Law, in each case whether or not caused by the negligence of Flexewallet Pty Ltd or any other indemnified party and whether or not the relevant claim has merit.
      • +
    +
  • 16.3 The indemnity in this Clause 16is a continuing obligation, and continues after this Agreement ends. It is not necessary for the indemnified party to suffer loss, incur expense or make payment before enforcing its right under this Clause 16.
    • +
  • 16.4 Subject always to the following clauses, to the maximum extent permitted by Law, the Supplier makes no representation nor gives any guarantee or warranty (including of merchantability, acceptable quality, fitness for any particular purpose or fitness for disclosed result) in connection with the RoyalPay Cross-Border Payment Services.
    • +
  • 16.5 There may be non-excludable statutory guarantees, implied conditions, and warranties or liabilities that the Supplier has to the Client under the Competition and Consumer Act 2010 (Cth)and other consumer protection laws that may apply to the RoyalPay Cross-Border Payment Services and that cannot be excluded (Non-Excludable Conditions or Liabilities).Nothing in this Agreement removes or limits any of the Non-Excludable Conditions or Liabilities.
    • +
  • 16.6 Notwithstanding clause 16.5, to the extent that the Suppliers liability can be limited under the Competition and Consumer Act 2010 (Cth)and other consumer protection laws that may apply to the RoyalPay Cross-Border Payment Services, the Supplier limits its liability to the Client for any breach of or non-compliance with, any of the Non-Excludable Conditions or Liabilities, at the Suppliers sole discretion, to resupplying the RoyalPay Cross-Border Payment Services or payment of, or reimbursement for, the cost of having the RoyalPay Cross-Border Payment Services resupplied, and the Client acknowledges that this limitation of liability is fair and reasonable in all the circumstances.
    • +
  • 16.7 Neither party will be liable to the other for any Consequential Loss suffered or incurred by the other party under, or in connection with this Agreement (whether based in contract, tort (including negligence), statute or otherwise.
    • +
  • 16.8 Either partys total liability to the other for any and all Loss in connection with this Agreement shall be limited to the sum of $50,000.
    • +
  • 16.9 The exclusions and limitations of liability in this clause do not apply to any Loss arising from any fraudulent act or omission of either party or its employees, agents or contractors in connection with the supply or use of the RoyalPay Cross-Border Payment Services.
    • +
  • 16.10 The Suppliers liability for any Loss suffered or incurred by the Client under, or in connection with this Agreement (whether based in contract, tort (including negligence), statute or otherwise) is reduced to the extent that:
    • +
      +
    • (a)the acts or omissions of the Client or the Clients Personnel;
      • +
    • (b)the use of any Third Party Facilities (as defined in clause 9.6); or
      • +
    • (c)the acts, omissions or equipment of a third person
      • +
    • caused or contributed to that Loss.
      • +
    +
  • 16.11 The Suppliers liability to the Client will be reduced to the extent that the Client has not taken reasonable steps to mitigate or avoid the Loss flowing from the event giving rise to the Suppliers liability to the Client.
    • +
+

17.Dispute Resolution

+
    +
  • 17.1 Any dispute arising in connection with this Agreement which cannot be settled by negotiation between the parties in accordance with the procedure detailed in clause 17.2must be submitted for mediation.
    • +
  • 17.2 Prior to referring a matter to mediation, the parties must:
    • +
      +
    • (a)refer the dispute to their respective Contract Managers for consideration who must meet (either in person or via teleconference) and undertake genuine and good faith negotiations with a view to resolving the dispute or difference within five (5) Business Days of referral of the dispute; and
      • +
    • (b)if the respective Contract Managers do not resolve the dispute within five (5) Business Days, the dispute must be referred to the relevant C-level executive (or equivalent) of each party who must meet (either in person or via teleconference) and undertake genuine and good faith negotiations with a view to resolving the dispute or difference within a further ten (10) Business Days.
      • +
    +
  • 17.3 If the process in clause 17.2is unsuccessful or the parties fail or refuse to meet then a mediator will be appointed by the parties acting at all times reasonably and if not so appointed within seven (7) Business Days from actual or scheduled completion of the procedure detailed in clause 17.2, either party may refer the dispute to the President of the Law Institute of Victoria who will appoint a suitable mediator with adequate experience in mediating the type of dispute and issues in question.
    • +
  • 17.4 Mediation must take place in Melbourne, Victoria and the parties may attend mediation by way of audio-visual or such other technological means.
    • +
  • 17.5 During such dispute resolution process, the parties may be legally represented.
    • +
  • 17.6 The parties must act in good faith during the dispute resolution process with a view to resolving the dispute.
    • +
  • 17.7 The dispute resolution process procedure is confidential and any written statements prepared for the mediator or for a party and any discussion between the parties and between the parties and the mediator before or during the mediation, are made on a without prejudice basis and cannot be used in any legal proceedings.
    • +
  • 17.8 Nothing in this clause will prevent a party from seeking urgent equitable relief before an appropriate court or tribunal; or seeking orders to enforce this clause 17.
    • +
  • 17.9 Each party will bear their own costs and the costs of the mediation will be borne equally by the parties to the dispute.
    • +
  • 17.10 The parties must continue to perform their respective obligations under this Agreement pending resolution of a dispute.
    • +
  • 17.11 Resolution in a court or tribunal should only be considered as a last resort and failure to institute court or tribunal proceedings does not amount to a breach of this Agreement or this clause 17.
    • +
  • 17.12 If, in relation to a dispute, a party breaches any provision of this clause 17, each other party need not comply with this clause 17in relation to that dispute.
    • +
  • 17.13 If a party does not observe the procedure in this clause 17then this clause 17may be pleaded as a bar to any proceeding, pending the outcome of the proper observance of the procedure in this clause 17.
    • +
+

18.Independent Contractor

+
    +
  • 18.1 The Client and Supplier acknowledge that they are in a relationship of principal and independent contractor and that the Supplier provides the RoyalPay Cross-Border Services in the capacity of independent contractor only. In no circumstances will the Supplier or any of its employees, agents, officers, advisers or sub-contractors claim or be deemed to be an employee, servant or agent of the Client. Further, the parties agree that:
    • +
      +
    • (a)the liabilities and obligations of the parties arising out of or in connection with this Agreement are several and not joint or joint and several; and
      • +
    • (b)a party does not have the authority to pledge the credit of or to act for the other party or to make representations, warranties or undertakings or assume obligations for or on behalf of the other party; and
      • +
    • (c)a party is not an employee of the other party and does not have any claim against the other party for superannuation, annual leave, public holiday, sick leave, long service leave, or, to the extent permitted by the Law, in respect of any claims under any Workers Compensation legislation, or on any other basis.
      • +
    +
+

19.Assignment

+
    +
  • 19.1 A party must not assign its rights or obligations under this Agreement without the prior written consent of the other party (not be unreasonably withheld).
    • +
  • 19.2 Any Change of Control of a party is deemed to constitute an assignment of this Agreement for the purposes of clause 19.1and a party must not effect a Change of Control without the prior written consent of the other party (not to be unreasonably withheld).
    • +
+

20.Inconsistency with Other Agreements

+
    +
  • 20.1 This Agreement, together with the SLA, constitute the entire agreement between the parties and no alternative agreements, terms, conditions, obligations or other provisions of any nature not contained in this Agreement or the SLA will be of any effect, shall add to or vary the terms and conditions of this Agreement.
    • +
  • 21.Miscellaneous Provisions
    • +
  • 21.1 Any notice to be given by any party to the other must be given by delivery to the other partys address as shown in this Agreement or as notified by any party to the other in writing as the address for notices.
    • +
  • 21.2 This Agreement will be governed by, and construed in accordance with, the Laws in force in the State of Victoria, Australia and the parties agree to submit to the non-exclusive jurisdiction of the courts in the State of Victoria, Australia.
    • +
  • 21.3 The obligations and liabilities imposed and the rights and benefits conferred on the parties under this Agreement will be binding upon and enure in favour of the respective parties and each of their respective successors in title, legal personal representatives and permitted assigns.
    • +
  • 21.4 No variation or waiver of any provision of this Agreement, nor consent to any departure by any party from its terms, will be of any effect unless it is confirmed in writing and then such variation, waiver or consent will be effective only to the extent for which it is made or given.
    • +
  • 21.5 No failure, delay or indulgence on the part of any party in exercising any power or right conferred upon such party under this Agreement will operate as a waiver of such power or right, nor will any single or partial exercise of any such power or right preclude any other future exercise of it, or the exercise of any other power or right under this Agreement.
    • +
  • 21.6 The Supplier shall have no liability to the Client under this Agreement if the Supplier is prevented from or delayed in performing its obligations, or from carrying on its business, or from providing the RoyalPay Cross-border Payment Services by virtue of a Force Majeure Event.
    • +
  • 21.7 If any provision of this Agreement will be invalid or unenforceable in accordance with its terms, it will be read down to the extent of such invalidity or unenforceability or, if incapable of such construction, it will be severed and all other provisions, which are self-sustaining and capable of separate enforcement without regard to the invalid or unenforceable provisions, will be and continue to be valid and enforceable in accordance with their terms.
    • +
  • 21.8 The parties will bear their own costs in connection with the preparation, negotiation and execution of this Agreement.
    • +
  • 21.9 Time is of the essence in this Agreement.
    • +
  • 21.10 This Agreement may be executed in any number of counterparts including by way of a countersigned PDF scanned and emailed between the parties. All counterparts will be taken to constitute one Agreement.
    • +
+

22.Glossary

+
    +
  • Definitions and Interpretation
    • +
  • Definitions: In this Agreement, unless the context otherwise dictates:
    • +
  • +
  • 22.1 Acceptance Testingmeans testing of the RoyalPay Cross-Border Payment Services by the Client in order to determine whether the RoyalPay Cross-Border Payment Services meet the Clients needs and expectations.
    • +
  • 22.2 Agreementmeans these terms and conditions and the Schedules.
    • +
  • 22.3 Affiliatemeans, in respect of a party:
    • +
      +
    • (a)the partys related bodies corporate (as that term is defined in the Corporations Act 2001 (Cth)) or any other bodies corporate associated with the party (including anybody corporate one of whose directors is also a director of the party); and
      • +
    • (b)Without limiting paragraph (a) of this definition, if the Client is a franchisee, its franchisor and each of the franchisors related bodies corporate.
      • +
    +
  • 22.4 BusinessDaymeans a day that falls between Monday and Friday (inclusive) and is not public holiday in bothAustraliaand China.
    • +
  • 22.5 Change of Controlmeans a change in the ownership or control (either directly or indirectly) of more than 50% of the voting share capital of the relevant undertaking or the ability to direct casting of more than 50% of the votes exercisable at general meetings of the relevant undertaking;
    • +
  • 22.6 CommencementDatemeans the date of this Agreement.
    • +
  • 22.7 ConfidentialInformationmeans all information related to the Supplier or the Client and includes, but is not limited to, this Agreement , any alliances, artwork, budgets, business affairs, client details, colour schemes, concepts, copyrightable work, customer list, data, designs, drawings, expertise, financials, formulae, functionality, human resources, ideas, information, Intellectual Property, intentions, inventions, joint ventures, know-how, layout, logos, literary works, market opportunities, methodologies, operations, partners, passwords, patent, personnel, plans, policies, procedures, processes, production information, projections, questions/answers, research, schematics, shareholders, slogans, software code, specifications, statistics, studies, supplier details, systems, trademarks (registered or otherwise), trade secrets, web developments, written materials, in any form or media, whether in writing or oral.
    • +
  • 22.8 ConsequentialLossmeans:
    • +
      +
    • (a)any loss of revenue, loss of profits, loss of anticipated savings or business, pure economic loss, loss of data, loss of value of equipment (other than cost of repair), loss of opportunity or expectation loss even if any of that Loss arises naturally (according to the usual course of things) from the fact, matter or circumstance giving rise to the Loss;
      • +
    • (b)any Loss that is suffered or incurred by a party as a result of a fact, matter or circumstance which does not arise naturally (that is, according to the usual course of things) from the fact, matter or circumstance giving rise to the Loss;
      • +
    • (c)any penalties imposed by a Government Agency; but
      • +
    • (d)this definition does not include PCI Fines.
      • +
    +
  • 22.9 ContractManageris as defined in clause 2.1.
    • +
  • 22.10 Feesmean the fees payable in respect of the RoyalPay Cross-Border Payment Services as detailed in Schedule B.
    • +
  • 22.11 ForceMajeureEventmeans a circumstance beyond a parties reasonable control, including acts or omissions of third party network operators or service providers, other than the partys Affiliates, fire, flood, earthquake, elements of nature or acts of God, acts of war, terrorism, riots, civil disorders, rebellions or revolutions, strikes or lockouts other than industrial action, howsoever described of the party or partys Personnel.
    • +
  • 22.12 GovernmentAgencymeans any governmental, semi-governmental, administrative, fiscal, statutory, judicial or quasi-judicial body, department, commission, authority, tribunal, agency or entity having operation or jurisdiction within Australia or anywhere else in the world.
    • +
  • 22.13 GSTmeans goods and services tax or any similar tax imposed by reason of a supply of goods or services under or in connection with this Agreement;
    • +
  • 22.14 Initial Termis as set out in Schedule B.
    • +
  • 22.15 IntellectualPropertymeans registered and unregistered business names, copyright, patents, trade marks, trade names, domain names, social media handles, know how, designs, plans, ideas, trade secrets, concepts, discoveries, inventions, brands, specifications and similar industrial and commercial intellectual property in Australia and worldwide, whether capable of registration or otherwise, both subsisting now or coming into existence at any time after the Commencement Date and includes the Confidential Information.
    • +
  • 22.16 IntellectualPropertyRightsmeans all and any patents, trademarks, service marks, trade names, registered designs, unregistered design rights, copyrights and rights in confidential information, and all and any other intellectual property rights, whether registered or unregistered, and including all applications and rights to apply for any of the same.
    • +
  • 22.17 Lawincludes any statute, rule, regulation, proclamation, order, ordinance or by-law (whether federal, state, territorial or local), codes of practice, Australian Standards and compliance codes.
    • +
  • 22.18 Lossincludes all loss, damage or liability (including liability to a third party) of any kind.
    • +
  • 22.19 PCI Finemeans any fine or other financial penalty imposed on the Supplier by a bank as a result of the Supplier being non-compliant with the then-current version of the Payment Card Industry Data Security Standard.
    • +
  • 22.20 PaymentTermsis defined in clause Error! Reference source not found..
    • +
  • 22.21 Personnelmeans in respect of a party, the employees, agents, contractors and Affiliates of the party and the employees, agents, contractors of the partys Affiliates and includes, in the case of the Client, the Clients end users of the RoyalPay Cross-Border Payment Services.
    • +
  • 22.22 RenewedTermis defined in clause 3.2.
    • +
  • 22.23 RoyalPay Cross-Border Payment Services mean the services to be supplied by the Supplier to the Client in accordance with this Agreement, namely the services described in Schedule B.
    • +
  • 22.24 Schedulesmean the schedules and appendices to this Agreement.
    • +
  • 22.25 SLAmeans the service level agreement separately provided to the Client by the Supplier and which may be amended by the Supplier in its absolute discretion from time to time.
    • +
  • 22.26 Tax Invoicehas the same meaning as that given in section 195-1 of A New Tax System (Goods and Services Tax) Act 1999 (Cth).
    • +
  • 22.27 Termis defined in clause 3.1.
    • +
  • 22.28 Third Party Facilitiesis defined in clause 9.6.
    • +
  • Interpretation: In this Agreement, unless the context otherwise dictates:
    • +
  • +
  • 22.29 Includes:the words includes, include, including, for example or such as must be read to mean includes, but is not limited to.
    • +
  • 22.30 SingularandPlural:words importing the singular (where appropriate) mean and include the plural and vice versa.
    • +
  • 22.31 Gender:words importing any one gender (where appropriate) mean and include the other genders and vice versa.
    • +
  • 22.32 NaturalPersons:words importing natural persons (where appropriate) mean and include corporations and unincorporated associations and vice versa.
    • +
  • 22.33 Headings:the headings are for convenience of reference only and are not to be construed as affecting the meaning or interpretation of this Agreement.
    • +
  • 22.34 StatutoryEnactments:all references in this Agreement to Law mean and are to be construed as references to that Law as amended or modified, consolidated, re-enacted or replaced from time to time and to the corresponding provisions of any similar Law of any other relevant jurisdiction.
    • +
  • 22.35 ReferencestopartsofthisAgreement:all references in this Agreement to sections, articles, clauses, sub-clauses, paragraphs and schedules mean, and are to be construed as, references to the sections, articles, clauses, sub-clauses, paragraphs and schedules of this Agreement.
    • +
  • 22.36 Party:references to any party to this Agreement or any other document or agreement include its successors, permitted assigns, heirs or legal personal representatives and includes company administrators, liquidators and trustees in bankruptcy.
    • +
  • 22.37 Covenants:any covenants, representations, warranties, indemnities or guarantees made or given by more than one party to another party hereunder are, unless specified otherwise, made or given jointly and severally.
    • +
  • 22.38 Wholeincludespart:a reference to anything includes the whole or any part of that thing and a reference to a group of things or persons includes each thing or person in that group.
    • +
  • 22.39 Partsofspeech:where any word or phrase is given a defined meaning, any other part of speech or other grammatical form of that word or phrase has a corresponding meaning.
    • +
  • 22.40 BusinessDay:Where any obligation under this Agreement falls to be performed on a day other than a Business Day, this Agreement must be construed as requiring that obligation to be performed on the next Business Day.
    • +
  • 22.41 Currency:References to $ or Dollars are references to Australian dollars, unless expressly indicated otherwise.
    • +
  • 22.42 Calendar:a reference to a day, week, month or a year is a reference to a calendar day, week, month or a year.
    • +
  • 22.43 Contraproferentemexcluded:a provision must not be construed against a party merely because that party was responsible for preparing this Agreement or that provision.
    • +
  • 22.44 Pre-Authorisation: refers to system functions which allow the placement of funds on hold for a pre-determined time, giving the Client the full control to exercise the option of completing the transaction at a later date.
    • +
+
+
+ + + +
    +
  • CONTRACTING PARTY DETAILS
    • +
+ +
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ 		+

THE SUPPLIER

+ 		+

THE CLIENT

+
+

Name:

+ 		+

Tunnel Show Pty Ltd trading as RoyalPay

+ 		+ +

+

+

ACN:

+ 		+

601 619 685

+ 		+

+
+

Address:

+ 		+

Level 11

+

15 William Street
Melbourne Vic 3000

+ 		+

+

+

{{aggregateFileInfo.address_sub}}

+
+

Contact Person:

+ 		+

+ 		+ +

+

+

Position:

+ 		+

+ 		+

+
+

Phone:

+ 		+

+ 		+ +

+

+

Fax:

+ 		+

+ 		+

+
+

Email:

+ 		+

+ 		+ + +

+

+ + + + + + + + + + + + + + + + + + + + + + + + +
+

Legal Representative:

+ 		+ + +

+

+

Position:

+ 		+ +

+

+

Phone:

+ 		+ +

+

+

Fax:

+ 		+
+

Email:

+ 		+ + +

+

+
+ +

+
    +
  • PARTICULARSOF THE ROYALPAY CROSS-BORDER PAYMENT SERVICES
    • +
+

+ + + + + + + + + + + + + + + + + + + + + + + +
+

Contract Manager (cl. 2)

+ 		+

+
+

Initial Term (cl. 3)

+ 		+

Twelve(12) months (unless terminated earlier in accordance with the terms of this Agreement)

+
+

Description of the RoyalPay Cross-Border Services

+ 		+

A software application and platform developed by the Supplier which provides Clients (who have web-based gateway APIs (being application programming interfaces) and point-of-sale payment processing and settlement capabilities in the Chinese currency) with a payment integration system, which:

+

(a)utilises the WeChat Pay payment technology that is owned by Tencent Holdings Limited (China) and that is licensed to the Supplier to facilitate third party payments in Australia;

+

(b)utilises the Alipay payment technology that is owned by Alipay.com Co., Ltd (China) and is licensed to the Supplier to facilitate third party payments in Australia;

+

(c)utilises the BestPaypayment technology that is owned by China Telecom Orange Finance and is licensed to the Supplier to facilitate third party payments in Australia;

+

(d)utilises the JDpaypayment technology that is owned by Chinabank Payment (Beijing) Technology Co.,Ltd.and is licensed to the Supplier to facilitate third party payments in Australia;

+

(e)utilises CB BankPay Payment technology licensed to the Supplier by Lakala Payment Co., Ltd, Yeepay Co., Ltd, PnR Data Service Co.,Ltdand other companies to facilitate third party payments in Australia;

+

(f)processes payments from users of Chinese bank cards and the WeChat Pay/Alipay/BestPay/JDpay/CB BankPay payment technology in Chinese Yuan, converts such payments to the Australian Dollar equivalent and then sends such payments to the Client by utilising settlement functions forming part of the software application;

+

(g)allows the Client to access the merchant management portal feature of the software application which facilitates transaction management, reporting and provides transactional analytics; and

+

(h)provides the Client with access to additional unique WeChat Pay marketing features including WeChat Lucky Money (an incentive program where payers randomly receive cashbacks) and WeChat Moment (being social media advertising aimed at enhancing a Clients brand awareness).

+
+

Commencement Date

+ 		+

The date of this Agreement

+
+

Fees

+ 		+

An integration fee and ongoing maintenance fee for the RoyalPay Cross-Border Payment Services shall be AUD $0, plus GST.

+

In addition, the Supplier shall charge a Merchant Service Fee (MSF) to the Client, per transaction, which shall be calculated in a percentage amount. The calculation schedule is as follows:

+

·the MSF is %(GST exclusive) of payments made using the RoyalPay Cross-Border Payment Services; (WeChat Pay)

+

·the MSF is %(GST exclusive) of payments made using the RoyalPay Cross-Border Payment Services; (AlipayOffline)

+

·the MSF is %(GST exclusive) of payments made using the RoyalPay Cross-Border Payment Services; (AlipayOnline)

+

·the MSF is %( GST exclusive) of payments made using the RoyalPay Cross-Border Payment Services; (Bestpay)

+

·the MSF is %(GST exclusive) of payments made using the RoyalPay Cross-Border Payment Services; (JDpay)

+

·the MSF is %(GST exclusive) of payments made using the RoyalPay Cross-Border Payment Services; (CBBankPay)

+

·the Supplier reserves the right to adjust the MSF rate mentioned above without prior consent from the Client. The Supplier will notify the Client of such change through the Suppliers website, portal and/or by email thirty (30) calendar days in advance before the MSF rate is adjusted;

+

·the parties agree that, when calculating the MSF, the figure shall be rounded to two decimal places; and

+

·the Client may elect to pass on the MSF to its customers or to bear the MSF itself, as per system configuration.

+
+

+ + + + + + + + + + + +
+

Settlement Method

+ 		+

The Supplier shall, after deducting all agreed service charges payable to the Supplier from the corresponding transaction, remit the balance to the Client by ways of Electronic Fund Transfer to the Client's nominated bank account in the currency of Australian Dollars (AUD). If the Client changes the bank account for any reason, it shall promptly give a valid notification to the Supplier of such change seven (7) calendar days in advance, and shall provide any other information required by the Supplier. Any Loss arising from an un-notified change of bank account details shall be solely borne by the Client.

+

Particulars of the bank account nominated by the Client:

+
    +
  • ·Name of the bank:
    • +
  • ·Country where the bank is located:Australia
    • +
  • ·BSB:
    • +
  • ·Account number:
    • +
  • ·Account name:
    • +
+
+

Settlement Terms

+ 		+

Settlement Cycle: . Funds will be settled on or beforeBusiness Day after the transaction has occurred.

+

For Settlement Cycle T+1: the provision of the above Settlement Cycle notwithstanding, the transaction occurred on Friday will be settled on the following Monday, and the transaction occurred on Saturday and Sunday will be settled on the following Tuesday.

+

+

Settlement Amount Calculation:

+

·If the Client elects to pass on the MSF to its customers, then the Client shall receive the full face-value settlement amount (e.g. the Client shall invoice its customers $100AUD and the Client shall receive $100AUD); or

+

·If the Client elects to bear the MSF itself, then the Client shall receive the full face-value settlement amount minus the MSF applied to the face value (e.g. the Client shall invoice its customers $100AUD and the Client shall receive $100AUD - $100 x MSF)

+

The Client acknowledges that the actual time of receipt of the payment is based on the notice that provided by Supplier.

+

The Client shall not be affected by any foreign exchange movement regarding payment processing and settlement, as indicated above in the Settlement Amount Calculation. During the payment process, the Clients customers will be prompted with daily AUD/CNY spot rate on the payment page.

+

The Client shall not be subject to any chargebacks in the event of transaction fraud, technical error or administrative error unless caused or contributed to by the Client. Any and all investigative and transactional duties in such events will be carried out by Tencent Holdings Limited (China), the provider of WeChat Pay technology; Alipay.com Co., Ltd. (China), the provider of Alipay payment technology;China Telecom Orange Finance, the provider of BestPaypayment technology; Chinabank Payment Technology, the provider of JDpay payment technology; andLakala Payment Co., Ltd, Yeepay Co., Ltd, PnR Data Service Co.,Ltdand other companies, the providers of CB BankPay technology.

+
+

+ + + + + + + +
+

Refund Process

+ 		+

Any authorisation-only or non-delivery or disputes or defects or warranty issues etc., arising from the Client's services rendered to its customers may incur refunds in the normal course of business after a transaction has been completed, which shall be dealt with in accordance with the following procedures:

+

·the Client shall be solely responsible for investigating and initiating refunds to its customers;

+

·if the related refund amount has been settled to the Client by the Supplier, the Client shall be solely responsible for processing the refund amount as per the Client's refund policy with its customers;

+

·if the related refund amount has not been settled to the Client by the Supplier, the Client can either: a) refund the amount as per the Client's refund policy to its customers, using its own funds prior to receiving the settlement amount; or b) the Client may make a refund request to the Supplier and the Supplier shall debit directly the refund amount from the unsettled amount payable to Client in order to initiate the refund;

+

·Due to settlement turnarounds and bank operations, it is possible that the unsettled funds with the Client may be insufficient to cover the actual refund amount, in which case the Client shall make the refund request to the Supplier at a later time when the required amount becomes available, given that the Client continues accumulating further unsettled transactions or alternatively, the Client may resort to a combination of method a) and b) above;

+

·except in the event that the Client ceases its business functions and is unable to refund its customers, the Supplier may request during the application process, a refundable security deposit to be paid by the Client upfront in order to cover such refund scenarios;

+

·the Client shall reserve the right to investigate the transaction before the refund is given and shall ultimately decide whether or not the refund is to be given; and

+

·the Supplier shall not impose any handling fee for any refund request.

+
+


Service Level Agreement

+

Key contact details:

+ + + + + + + +
+

Client Support

+ 		+

Email: info@royalpay.com.au

+

Contact: Customer Service Officer

+
+

+ + + + + + + +
+

Commercial Support

+ 		+

Email: Mona.Zhang@royalpay.com.au

+

Contact: MonaZhang

+
+

+ + + + + + + +
+

Technical Support

+ 		+

Email: leo.huang@royalpay.com.au

+

Contact: Leo Huang

+
+

+ + + + + + + +
+

Financial Support

+ 		+

Email: accountofficer@royalpay.com.au

+

Contact: Account Officer

+
+

+ + + + + + + +
+

Compliance Support

+ 		+

Email: Compliance@royalpay.com.au

+

Contact: Compliance

+
+

+

Recommended Information to be included in the support email:

+


- Nature of the issue
+ - Date and time of occurrence
+ - Impact on operation

+


Level of Support:

+


RoyalPay provides three (3) levels of support: Level 1, Level 2, Level 3. The Client needs to identify the nature of the issue and appropriate level of support in order for RoyalPay to achieve optimal client support experience, and Client should use always use Level 1 support as priority support option.

+


Level 1 support functions include:

+


- First level of contact for Client Service Representatives
- General facilitation of day-to day operations
- System monitoring, including regular checking of system mail, error logs, alarms, system performance, utilisation and capacity, user logins, etc
- Access and interpretation of system logs and traces
- Archiving of data and backup related to RoyalPay platform(if applicable)
- Ensuring and maintaining remote access
- Loading authorised software update
- Attend to escalated problems from the Client Service Department
- Attend to internal business support
- System, and where practical, network reporting
- Within reason and on a best endeavours basis, RoyalPay will provide limited reporting based fault recognition, isolation and forward to Level 2

+


Level 2 support functions include:

+

- Diagnosis of Hardware and Software faults
+ - Monitoring progress
+ - Problem resolution
+ - Where the Client has purchased hardware directly from RoyalPay
+ - RoyalPay will process hardware faults through to the original hardware vendors standard support infrastructure and leverage off standing agreements and nominated response times
+ - Escalation to Head Office/Technical Team or Level 3 support as required

+


Level 3 support functions include:

+

- Any problem as escalated from Level 2.
- Interaction with Level 1 & 2 support and 3rd parties as relevant.
- Acting as interface with 3rd Party software support organisations

+

+

Support not included:

+

- Rectification of defects or errors resulting from any modification of the system not approved by RoyalPay
+ - Rectification of defects or errors resulting from use of the system in combination with anything not forming part of the original intent of the system
+ - Rectification of a fault in anything not forming part of the system
- Any modification of the system which represents a departure from the specifications
+ - Electrical or environmental adjustment or damage caused by electrical or environmental factors
+ - Repair or damage arising out of misuse or unauthorised use of the system by or any person
+ - Furnishing accessories
+ - Any rectification arising from any substitution, alteration or relocation of the System made by any person that is not approved by RoyalPay
+ - Rectification of errors or defects which are the subject of a warranty under another agreement
+ - Any rectification arising from failing to install supplied updates or upgrades
+ - Any defect arising from the use of the system other than in accordance with applicable user ocumentation
+ - Rectification of errors or defects resulting from improper operation of the system by any person
+ - Any defect arising from misuse, negligence or abuse of the software and/or database(s)
+ - Any rectification arising from failing to comply with its obligations under these terms.
+ -Maintenance of hardware or items external to the system, or for added accessories for which maintenance charges have not been paid
+ - Engineering modifications (other than those normally performed as part of RoyalPay support)
+ - Supply and installation of consumables, or damage caused by use of incompatible consumables
+ - Rectification of problems caused by the connection of or use of third party products, hardware and /or software which are not maintained by RoyalPay
+ - Refurbishment of product, or damage or wear due to overuse or use outside published specifications
+ - Hardware and/or Software covered by third party maintenance agreements

+

+

Support Priority and Response time:

+

The normal response time is 9am – 6pm, Mon – Fri (Excluding public holidaysin both Australia and China)

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

Criticality

+ 		+

Description

+ 		+

Client Notification Time

+ 		+

Response Time

+ 		+

Resolution

+
+

1

+ 		+

RoyalPay system is down

+ 		+

Instantaneous

+ 		+

2 hours

+ 		+

5 hours

+
+

2

+ 		+

Major problem inhibiting operation

+ 		+

Instantaneous

+ 		+

4 hours

+ 		+

12 hours

+
+

3

+ 		+

Minor problem causing inconvenience

+ 		+

Instantaneous

+ 		+

24 hours

+ 		+

14 days

+
+

4

+ 		+

Other commercial/financial request

+ 		+

N/A

+ 		+

48 hours

+ 		+

Tentative

+
+


Emergency/After Hour Contact:

+


To ensure high availability and reliability of RoyalPays uninterrupted services, any serious issue/after hour escalation contact details might be established by agreed methods between RoyalPay and the Client. Once established, an amended SLA shall be advised to the Client.

+

+

+

Execution Page

+

+

Executed as an agreement by being signed in accordance with section 127 of the Corporations Act2001 (Cth) by:

+

+

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+

Tunnel Show Pty Ltd (ACN 601 619 685) trading as RoyalPay

+
+

Signature of Director/Secretary:

+ 		+

+ 		+

+
+

Print Full Name:

+ 		+

Yangfan Ge

+ 		+

+
+

Position:

+ 		+

Director

+ 		+

Director/Secretary

+
+

Date:

+ 		+ +

+

+

+
+
+ +
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + +
+

Client Name/ACN:

+
+

Signature of Director/Secretary: +

+ + 		+ + +

+
+

Print Full Name:

+ + 		+ + +

+
+

Position:

+ 		+

Director

+ 		+

Director/Secretary

+
+

Date:

+ 		+ +

+

+

+
+
+ +
+
+ + +
+
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/src/main/ui/merchant_application.html b/src/main/ui/merchant_application.html index 9cc659951..696291205 100644 --- a/src/main/ui/merchant_application.html +++ b/src/main/ui/merchant_application.html @@ -427,76 +427,77 @@ maxlength="10" name="postcode"> - - - -
+ ng-class="{'has-error':companyForm.contact_job.$invalid && companyForm.contact_job.$dirty}">
-
- -
- -
-
- {{partner.nation_code}} - +
+
Legal person information
+
+
+ +
+
+
+ {{partner.nation_code}} + +
+
+
+ +
+

The mailbox is incorrect

+
+
+
+ +
+
-
- -
-

The mailbox is incorrect

+
+
Registered Address
+
+
+ +
+
+ +
+
+ +
+
+ +
+
-
- -
- -
- -
- -
- -
-
- -
-
- -
- - - -
@@ -516,6 +517,28 @@
+ +
+ +
+ + +
Merchant Payment Scenario
@@ -703,15 +726,6 @@
- -
+ + + Sign Contract +
-
- -
-
- -
- - -
-
-
- -
- -
- -
-
Legal person information
-
-
- -
-
-
- {{partner.nation_code}} - -
-
-
- -
-

The mailbox is incorrect

-
-
-
- -
- -
-
- -
-
Registered Address
-
-
- -
-
- -
-
- -
-
- -
- -
-
-
@@ -933,7 +845,6 @@
-
From bd6e58ee3b5bd93a6981f52a92255e22879e75a0 Mon Sep 17 00:00:00 2001 From: luoyang Date: Fri, 1 Nov 2019 18:20:33 +0800 Subject: [PATCH 16/24] =?UTF-8?q?add=20app=E8=87=AA=E5=8A=A9=E8=BF=9B?= =?UTF-8?q?=E4=BB=B6=E4=BC=98=E5=8C=96?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../core/impls/RetailAppServiceImp.java | 47 +++++- .../application/beans/ClientPreApplyBean.java | 145 +----------------- .../merchants/beans/ClientUpdateInfo.java | 102 ++++++++++-- .../core/impls/ClientManagerImpl.java | 13 ++ .../resources/templates/app/app_customer.html | 2 +- 5 files changed, 144 insertions(+), 165 deletions(-) diff --git a/src/main/java/au/com/royalpay/payment/manage/appclient/core/impls/RetailAppServiceImp.java b/src/main/java/au/com/royalpay/payment/manage/appclient/core/impls/RetailAppServiceImp.java index c77446f8a..bb5cc2cff 100644 --- a/src/main/java/au/com/royalpay/payment/manage/appclient/core/impls/RetailAppServiceImp.java +++ b/src/main/java/au/com/royalpay/payment/manage/appclient/core/impls/RetailAppServiceImp.java @@ -696,6 +696,17 @@ public class RetailAppServiceImp implements RetailAppService { public JSONObject getClientInfoRealtime(JSONObject device) { JSONObject clientWithConfig = clientManager.getClientInfo(device.getIntValue("client_id")); clientWithConfig.putAll(clientConfigService.find(device.getIntValue("client_id"))); + JSONObject legalInfo = sysClientLegalPersonMapper.findRepresentativeInfo(device.getIntValue("client_id")); + if (legalInfo != null) { + clientWithConfig.put("representative_person", legalInfo.getString("representative_person")); + clientWithConfig.put("representative_phone", legalInfo.getString("phone")); + clientWithConfig.put("representative_email", legalInfo.getString("email")); + clientWithConfig.put("representative_job_title", legalInfo.getString("job_title")); + clientWithConfig.put("registered_address", legalInfo.getString("address")); + clientWithConfig.put("registered_suburb", legalInfo.getString("suburb")); + clientWithConfig.put("registered_state", legalInfo.getString("state")); + clientWithConfig.put("registered_postcode", legalInfo.getString("postcode")); + } return clientWithConfig; } @@ -719,6 +730,7 @@ public class RetailAppServiceImp implements RetailAppService { public JSONObject getClientInfoMe(JSONObject device) { JSONObject result = new JSONObject(); result.put("base_info_lack", false); + result.put("legal_info_lack", false); result.put("compliance_info_lack", false); JSONObject client = clientMapper.findClient(device.getIntValue("client_id")); if (StringUtils.isEmpty(client.getString("business_structure")) || StringUtils.isEmpty(client.getString("logo_url")) @@ -728,7 +740,16 @@ public class RetailAppServiceImp implements RetailAppService { || (StringUtils.isEmpty(client.getString("company_website")) && StringUtils.isEmpty(client.getString("company_photo")) && StringUtils.isEmpty(client.getString("store_photo")))) { result.put("base_info_lack", true); - + } + JSONObject legalInfo = sysClientLegalPersonMapper.findRepresentativeInfo(device.getIntValue("client_id")); + if (StringUtils.isEmpty(legalInfo.getString("representative_person")) || StringUtils.isEmpty(legalInfo.getString("job_title")) + || StringUtils.isEmpty(legalInfo.getString("phone")) + || StringUtils.isEmpty(legalInfo.getString("email")) + || StringUtils.isEmpty(legalInfo.getString("address")) + || StringUtils.isEmpty(legalInfo.getString("suburb")) + || StringUtils.isEmpty(legalInfo.getString("state")) + || StringUtils.isEmpty(legalInfo.getString("postcode"))) { + result.put("legal_info_lack", true); } JSONObject file = clientManager.getAuthFiles(null, client.getString("client_moniker")); for (String s : fileName) { @@ -2631,9 +2652,11 @@ public class RetailAppServiceImp implements RetailAppService { private JSONObject getClientBaseInfo(JSONObject clientWithConfig) { JSONObject res = SignInAccountServiceImpl.clientInfoWithNoSecretInfo(clientWithConfig); res.put("is_skip_clearing", res.getBoolean("skip_clearing")); + JSONObject clientLegalInfo = null; if ("4".equals(clientWithConfig.getString("source"))) { res.put("refuse_remark", clientWithConfig.getString("refuse_remark")); res.put("base_info_lack", false); + res.put("legal_info_lack", false); res.put("compliance_info_lack", false); if (StringUtils.isEmpty(clientWithConfig.getString("business_structure")) || StringUtils.isEmpty(clientWithConfig.getString("logo_url")) || StringUtils.isEmpty(clientWithConfig.getString("description")) @@ -2642,7 +2665,16 @@ public class RetailAppServiceImp implements RetailAppService { || (StringUtils.isEmpty(clientWithConfig.getString("company_website")) && StringUtils.isEmpty(clientWithConfig.getString("company_photo")) && StringUtils.isEmpty(clientWithConfig.getString("store_photo")))) { res.put("base_info_lack", true); - + } + clientLegalInfo = sysClientLegalPersonMapper.findRepresentativeInfo(res.getIntValue("client_id")); + if (StringUtils.isEmpty(clientLegalInfo.getString("representative_person")) || StringUtils.isEmpty(clientLegalInfo.getString("job_title")) + || StringUtils.isEmpty(clientLegalInfo.getString("phone")) + || StringUtils.isEmpty(clientLegalInfo.getString("email")) + || StringUtils.isEmpty(clientLegalInfo.getString("address")) + || StringUtils.isEmpty(clientLegalInfo.getString("suburb")) + || StringUtils.isEmpty(clientLegalInfo.getString("state")) + || StringUtils.isEmpty(clientLegalInfo.getString("postcode"))) { + res.put("legal_info_lack", true); } JSONObject file = clientManager.getAuthFiles(null, clientWithConfig.getString("client_moniker")); for (String s : fileName) { @@ -2651,12 +2683,11 @@ public class RetailAppServiceImp implements RetailAppService { } } } - JSONObject clientLegal = sysClientLegalPersonMapper.findRepresentativeInfo(res.getIntValue("client_id")); - if (clientLegal != null) { - res.put("legal_person", clientLegal.getString("representative_person")); - res.put("legal_job_title", clientLegal.getString("job_title")); - res.put("legal_phone", clientLegal.getString("phone")); - res.put("legal_email", clientLegal.getString("email")); + if (clientLegalInfo != null) { + res.put("legal_person", clientLegalInfo.getString("representative_person")); + res.put("legal_job_title", clientLegalInfo.getString("job_title")); + res.put("legal_phone", clientLegalInfo.getString("phone")); + res.put("legal_email", clientLegalInfo.getString("email")); } return res; } diff --git a/src/main/java/au/com/royalpay/payment/manage/application/beans/ClientPreApplyBean.java b/src/main/java/au/com/royalpay/payment/manage/application/beans/ClientPreApplyBean.java index 6160a9211..d51a6becd 100644 --- a/src/main/java/au/com/royalpay/payment/manage/application/beans/ClientPreApplyBean.java +++ b/src/main/java/au/com/royalpay/payment/manage/application/beans/ClientPreApplyBean.java @@ -57,22 +57,7 @@ public class ClientPreApplyBean { private String client_pay_type = "2"; private String client_pay_desc = "201"; - private String contact_job; - private String representative_person; - private String representative_phone; - private String representative_email; - private String representative_job_title; - private String registered_address; - private String registered_suburb; - private String registered_state; - private String registered_postcode; - private String logo_url; - private String company_website; - private String company_photo; - private String alipayindustry; - private String wechatindustry; - private String store_photo; - private String contract_url; + public JSONObject insertObject() { JSONObject res = (JSONObject) JSON.toJSON(this); @@ -270,132 +255,4 @@ public class ClientPreApplyBean { public String getClient_pay_desc() { return client_pay_desc; } - - public String getContact_job() { - return contact_job; - } - - public void setContact_job(String contact_job) { - this.contact_job = contact_job; - } - - public String getRepresentative_person() { - return representative_person; - } - - public void setRepresentative_person(String representative_person) { - this.representative_person = representative_person; - } - - public String getRepresentative_phone() { - return representative_phone; - } - - public void setRepresentative_phone(String representative_phone) { - this.representative_phone = representative_phone; - } - - public String getRepresentative_email() { - return representative_email; - } - - public void setRepresentative_email(String representative_email) { - this.representative_email = representative_email; - } - - public String getRepresentative_job_title() { - return representative_job_title; - } - - public void setRepresentative_job_title(String representative_job_title) { - this.representative_job_title = representative_job_title; - } - - public String getRegistered_address() { - return registered_address; - } - - public void setRegistered_address(String registered_address) { - this.registered_address = registered_address; - } - - public String getRegistered_suburb() { - return registered_suburb; - } - - public void setRegistered_suburb(String registered_suburb) { - this.registered_suburb = registered_suburb; - } - - public String getRegistered_state() { - return registered_state; - } - - public void setRegistered_state(String registered_state) { - this.registered_state = registered_state; - } - - public String getRegistered_postcode() { - return registered_postcode; - } - - public void setRegistered_postcode(String registered_postcode) { - this.registered_postcode = registered_postcode; - } - - public String getLogo_url() { - return logo_url; - } - - public void setLogo_url(String logo_url) { - this.logo_url = logo_url; - } - - public String getCompany_website() { - return company_website; - } - - public void setCompany_website(String company_website) { - this.company_website = company_website; - } - - public String getCompany_photo() { - return company_photo; - } - - public void setCompany_photo(String company_photo) { - this.company_photo = company_photo; - } - - public String getAlipayindustry() { - return alipayindustry; - } - - public void setAlipayindustry(String alipayindustry) { - this.alipayindustry = alipayindustry; - } - - public String getStore_photo() { - return store_photo; - } - - public void setStore_photo(String store_photo) { - this.store_photo = store_photo; - } - - public String getWechatindustry() { - return wechatindustry; - } - - public void setWechatindustry(String wechatindustry) { - this.wechatindustry = wechatindustry; - } - - public void setContract_url(String contract_url) { - this.contract_url = contract_url; - } - - public String getContract_url() { - return contract_url; - } } diff --git a/src/main/java/au/com/royalpay/payment/manage/merchants/beans/ClientUpdateInfo.java b/src/main/java/au/com/royalpay/payment/manage/merchants/beans/ClientUpdateInfo.java index 3d82ed400..b0851cae3 100644 --- a/src/main/java/au/com/royalpay/payment/manage/merchants/beans/ClientUpdateInfo.java +++ b/src/main/java/au/com/royalpay/payment/manage/merchants/beans/ClientUpdateInfo.java @@ -57,18 +57,18 @@ public class ClientUpdateInfo { private String country; @Pattern(regexp = "^((Australia/West)|(Australia/Eucla)|(Australia/North)|(Australia/South)|(Australia/Brisbane)|(Australia/Melbourne)|(Australia/LHI))$", message = "error.payment.valid.invalid_timezone") private String timezone; -// private String jdindustry; -// private String royalpayindustry; - -// private String referrer_id; -// private String referrer_name; -// private String client_apply_id; -// -// private String business_hours; -// private String merchant_introduction; -// private String merchant_tag; -// private String merchant_video_url; + private String contact_job; + private String representative_person; + private String representative_phone; + private String representative_email; + private String representative_job_title; + private String registered_address; + private String registered_suburb; + private String registered_state; + private String registered_postcode; + private String logo_url; + public JSONObject insertObject() { JSONObject res = (JSONObject) JSON.toJSON(this); @@ -325,9 +325,87 @@ public class ClientUpdateInfo { this.businessStructure = businessStructure; } + public String getContact_job() { + return contact_job; + } + + public String getLogo_url() { + return logo_url; + } + + public String getRegistered_address() { + return registered_address; + } + + public String getRegistered_postcode() { + return registered_postcode; + } + + public String getRegistered_state() { + return registered_state; + } + + public String getRegistered_suburb() { + return registered_suburb; + } + + public String getRepresentative_email() { + return representative_email; + } + + public String getRepresentative_job_title() { + return representative_job_title; + } + + public String getRepresentative_person() { + return representative_person; + } + + public String getRepresentative_phone() { + return representative_phone; + } + + public void setContact_job(String contact_job) { + this.contact_job = contact_job; + } + + public void setLogo_url(String logo_url) { + this.logo_url = logo_url; + } + public void setRegistered_address(String registered_address) { + this.registered_address = registered_address; + } + + public void setRegistered_postcode(String registered_postcode) { + this.registered_postcode = registered_postcode; + } + + public void setRegistered_state(String registered_state) { + this.registered_state = registered_state; + } + + public void setRegistered_suburb(String registered_suburb) { + this.registered_suburb = registered_suburb; + } + + public void setRepresentative_email(String representative_email) { + this.representative_email = representative_email; + } + + public void setRepresentative_job_title(String representative_job_title) { + this.representative_job_title = representative_job_title; + } + + public void setRepresentative_person(String representative_person) { + this.representative_person = representative_person; + } + + public void setRepresentative_phone(String representative_phone) { + this.representative_phone = representative_phone; + } -// public String getReferrer_id() { + // public String getReferrer_id() { // return referrer_id; // } // diff --git a/src/main/java/au/com/royalpay/payment/manage/merchants/core/impls/ClientManagerImpl.java b/src/main/java/au/com/royalpay/payment/manage/merchants/core/impls/ClientManagerImpl.java index 10f627a83..27fdbf713 100644 --- a/src/main/java/au/com/royalpay/payment/manage/merchants/core/impls/ClientManagerImpl.java +++ b/src/main/java/au/com/royalpay/payment/manage/merchants/core/impls/ClientManagerImpl.java @@ -906,6 +906,19 @@ public class ClientManagerImpl implements ClientManager, ManagerTodoNoticeProvid } } clientMapper.update(info); + if (StringUtils.isNotBlank(info.getString("representative_person"))) { + JSONObject legal = new JSONObject(); + legal.put("client_id", client.getIntValue("client_id")); + legal.put("representative_person", info.getString("representative_person")); + legal.put("job_title", info.getString("representative_job_title")); + legal.put("phone", info.getString("representative_phone")); + legal.put("email", info.getString("representative_email")); + legal.put("address", info.getString("registered_address")); + legal.put("suburb", info.getString("registered_suburb")); + legal.put("state", info.getString("registered_state")); + legal.put("postcode", info.getString("registered_postcode")); + sysClientLegalPersonMapper.update(legal); + } saveOrUpdateMailList(info, client); clientInfoCacheSupport.clearClientCache(clientId); } diff --git a/src/main/resources/templates/app/app_customer.html b/src/main/resources/templates/app/app_customer.html index f4b10a712..bd3b689c1 100644 --- a/src/main/resources/templates/app/app_customer.html +++ b/src/main/resources/templates/app/app_customer.html @@ -10,7 +10,7 @@ +