NewTemplate

Technical Information Required for Account Set up and Activation
Company Name
Merchant Company Name (will be shown on customer email receipt)
Hidden
Application Reference
Technical Contact
If not previously provided
First Name
Last Name
Phone
Email
Skype ID
Website
Provide the URLs of all relevant trading websites
Currencies Required
Settlement Currency/Currencies
Processing Currency/Currencies
If other currencies?
Special Requirements
Billing Descriptor
Your trading name will appear on the card holder statement. Cannot exceed 17 characters
Automated Email Receipt:
Do you require latpay to send out email receipts on your behalf to assist your customers in reconciling their transactions?*
- Yes
- No
Please email a copy of your email receipt to compliance@latpay.com
Email address for Sending Email receipts
Provide your “sent from” email address for receipts to customers
Email Address for Receipt of Email receipts
Please provide an email address to receive a copy of email receipts by BCC.
Support Email Address
your customers to contact your support team.
Billing and Reporting System
Access to Merchant Reports is sent after account set up
Email Address for Merchant Report Login
Provide a list of authorised users’ email addresses that can access Merchant Reporting. Passwords will be sent directly to the authorised users
Choose the type of account*
- Live Account
- Test Account
Select the products to setup accounts:
Products
- API Integration
- Hosted Payment Page
- Alternate Payments
- Recurring Payments
- Invoice Payment Link
- mPOS
- Shopping Cart
- All in one terminal
Please provide the information below to ensure your account is set up securely
Username & Password:
The username and password used for authentication on the return post from the Latpay server to the merchant server
Username
Password
Reply Password
The password used for authentication on the return post from the Latpay server to the merchant server.
IP address of server
The IP address of the merchant web server needs to be provided. Please notify Latpay before changing your IP address.
Do you want 3D secure for API?
Please select yes if you need 3D secure option.
- Yes
- No
3d secure Integration specific
BackToMerchantURL
The URL in your server, to which customers must be redirected after 3dsecure authentication;
HPS INTEGRATION SPECIFIC
Posting Domain & Page
The full URL of the page (including the domain) which will post details to Latpay HPS system.Please notify Latpay before changing your posting page.
Secret Key
Merchants should hash important transaction fields when using HPS system due to inherent risks of “man in middle” attacks. The secret key is used for hashing. Do not use any special characters.
Authorisation result URL
URL on merchant website to which the result of the authorisation will be posted back**** Customer will be redirected along with this post back to merchant site.
Cancel URL
URL on merchant website to which the customer must be returned when customer opts out of the payment process (by clicking the cancel button)
Notify URL
URL on merchant server to which the transaction status should be notified as soon as transaction is completed. This is independent of customer redirection and happens server to server synchronously.
Do you want 3D secure for HPS?
Please select yes if you need 3D secure option.
- Yes
- No
3d secure Integration specific
BackToMerchantURL
The URL in your server, to which customers must be redirected after 3dsecure authentication;
Alternate Payment
Services Needed
Alternate Payment services to be enabled For
- PAYSAFECARD
- GIROPAY
- SOFORT
- QIWI
- TRUSTPAY
- ELV
- EPS
- iDEAL
- POLi
- PRZELEWY24
- SKRILL
- TELEINGRESO
- UKASH
- SAFETYPAY
- ASTROPAY
- Boleto
- Ticket Online (Raberil)
- Instant Transfer
- NETELLER
- BITCOINS
- BANAMEX
- BANCODECHILE
- BRADESCO
- DAVIVIENDA
- EFECTY
- ITAU
- MULTIBANCO
- PSE
- REDPAGOS
- SANTANDER
- ENTERCASH
- ZIMPLERH
- BANCO DO BRASIL
- Alipay
Redirection URL
URL to redirect the customer back to merchant site after authentication
Notification URL
URL to notify the transaction status in case of asynchronous processing.
Error notification URL
URL to redirect the customer back to merchant in case of fatal errors
Recurring Payments
Select Payment
You will be given access to Payment Manager to Schedule payment collections from your customers
- Card Payments
- Bank Payments
Latpay to notify customers of Payment collection 3 days prior to payment collection?
If [no] Please send a copy of the notification of payment collection email or message sent to customer
- Yes
- No
Email Address of Authorised User of Payment Manager
User must be an Authorised Representative of the Company
Invoice Payment Link
Connected Service
- Xero Accounting
- Email Invoice Link
- SMS Invoice Link
User Access - Payment Manager
User must be an Authorised Representative of the Company
USER1
First Name
Last Name
Position
Email
USER2
First Name
Last Name
Position
Email
mPOS
Number of stores
No. of stores where mPOS will be used
Store Reference per store
To uniquely identify the location of where the mpos is used. (up to 20 characters)
Number of devices per store
No. of devices/terminals in each store.
Device type and reference
Make and Model of Android Device eg. Samsung Galaxy 10 and Unique reference to identify devices on which the mpos is running. (Alphanumeric – upto 20 char) eg: Lat02SG10
Phone
If we need to send the apk straight to device
Terminal secret
If apk sent direct to device
Per device provide a Unique Terminal Secret.. Please ensure strong secret key. Terminal Secret (aka Password or Key) - Unique for each Device
Merchants should hash important transaction fields when using mPOS due to inherent risk of “man in middle” attacks. The Terminal Secret is used for hashing
All in one terminal
Number of stores
No. of stores where mPOS will be used
Store Reference per store
To uniquely identify the location of where the mpos is used. (up to 20 characters)
Number of devices per store
No. of devices/terminals in each store.
Device type and reference
Make and Model of Android Device eg. Samsung Galaxy 10 and Unique reference to identify devices on which the mpos is running. (Alphanumeric – upto 20 char) eg: Lat02SG10
Terminal secret
If apk sent direct to device
Per device provide a Unique Terminal Secret.. Please ensure strong secret key. Terminal Secret (aka Password or Key) - Unique for each Device
Merchants should hash important transaction fields when using mPOS due to inherent risk of “man in middle” attacks. The Terminal Secret is used for hashing
Shopping Cart
Select your shopping cart domain
- WooCommerce
- Magento
- VirtueMart
- OpenCart
- osCommerce
- Others
If others
Posting Domain & Page
The full URL of the page (including the domain) which will post details to Latpay HPS system.Please notify Latpay before changing your posting page.
Secret Key
Merchants should hash important transaction fields when using HPS system due to inherent risks of “man in middle” attacks. The secret key is used for hashing. Do not use any special characters.
Authorisation result URL
URL on merchant website to which the result of the authorisation will be posted back**** Customer will be redirected along with this post back to merchant site.
Cancel URL
URL on merchant website to which the customer must be returned when customer opts out of the payment process (by clicking the cancel button)
Notify URL
URL on merchant server to which the transaction status should be notified as soon as transaction is completed. This is independent of customer redirection and happens server to server synchronously.
Phone
This field is for validation purposes and should be left unchanged.

Technical Information Required for Account Set up and Activation

Billing and Reporting System

3d secure Integration specific

HPS INTEGRATION SPECIFIC

3d secure Integration specific

Alternate Payment

Recurring Payments

Invoice Payment Link

User Access - Payment Manager

mPOS

All in one terminal

Shopping Cart