Tazapay - Merchant Onboarding

Phil Astall
Phil Astall
  • Updated

All merchants connected to the partner Tazapay will have a unique onboarding set up, with all . Please follow the steps below for MID onboarding guidance for both Asia and EU acquiring MIDS.

 

NOTE: No gateway processing contract required, the partner/merchant will be billed by back office.

 

MID Onboarding

  • Onboard MID using https://onboarding.totalp.dev/ as per normal boarding processes.
  • If the MID is for EU acquiring rails (NETS) via ACI, select 'Nomupay EU' on the onboarder. For all EU MIDs please select 'Tazapay Limited' as the Division Name or UUID, and 'Tazapay - EU' as for the 'Merchant Name'. This process will be handled by EU and UK Support.
  • If MIDS  APAC acquiring rails (PP) via ACI, select Nomupay HK.  select 'Nomupay HK' on the onboarder. For all EU MIDs please select 'Tazapay Limited' as the Division Name or UUID, and 'Tazapay - HK' as for the 'Merchant Name'. This process will be handled by UAE and Asia Support.
  • All merchants should have one EU MID boarded under entity ID 8acda4c999a567c60199ba1756a051c2. And one HK MID boarded under entity 8acda4c999a567c60199ba15269f5191. 
  • All Merchants Require a 3d and non 3d channel for both entities.
  • Select EUR GBP and USD on the onboarder (more currencies will be added via API by the IC's)
  • Channel should read as: {Merchant website} - 3DChannel: {Merchant website} - non3D*no ‘http’ or ‘.com’ needed. 
  • Test using https://api.acceler8.uk/threedsecure_2_2/frame.php - add merchantTransactionId as NP_TEST
  • Should you need to edit the channel name, this can be done directly on the BIP on the channel level. Administration > Account Data > Edit Channel.
  • Custom Descriptor to be set with the Descriptor - TZP. To make this change navigate to Attached Merchant Accounts (Merchant Ids) on the channels.

 

  • Once boarded, support should notify IC's on teams channel to enable the following currencies via API: AED, AFN, ALL, AMD, ANG, AOA, ARS, AUD, AWG, AZN, BAM, BBD, BDT, BGN, BHD, BIF, BMD, BND, BOB, BRL, BSD, BTN, BWP, BYN, BZD, CAD, CDF, CHF, CLP, CNY, COP, CRC, CVE, CZK, DJF, DKK, DOP, DZD, EGP, ERN, ETB, EUR, FJD, GBP, GEL, GHS, GIP, GMD, GNF, GTQ, GYD, HKD, HNL, HRK, HTG, HUF, IDR, ILS, INR, IQD, ISK, JMD, JOD, JPY, KES, KGS, KHR, KMF, KPW, KRW, KWD, KYD, KZT, LAK, LBP, LKR, LRD, LSL, LYD, MAD, MDL, MGA, MKD, MMK, MNT, MOP, MRU, MUR, MVR, MWK, MXN, MYR, MZN, NAD, NGN, NIO, NOK, NPR, NZD, OMR, PAB, PEN, PGK, PHP, PKR, PLN, PYG, QAR, RON, RSD, RUB, RWF, SAR, SBD, SCR, SDG, SEK, SGD, SLL, SRD, SZL, THB, TJS, TMT, TND, TOP, TRY, TTD, TWD, TZS, UAH, UGX, USD, UYU, UZS, VND, VUV, WST, XAF, XCD, XOF, XPF, YER, ZAR, ZMW.

 

Salesforce

  • Ensure all data is correctly reflected within the merchants company salesforce page. Including relevant acquiring information, company address, contact and the MID ticket link.
  • Move status from 'Support' to 'Live not trading'

 

Welcome Email

  • Welcome email should go to onboarding@tazapay.com, support@tazapay.com with James Anstiss james.anstiss@nomupay.com in cc. 
  • Note: You do not need to include the main contact from Salesforce on the MID email within the welcome email.
  • Please use macro 'Welcome Email - Tazapay' and include the details for disputes within the main body of the 

 

 

 

 

 

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request