Merchant Company Name (will be shown on customer email receipt)
Provide the URLs of all relevant trading websites
Your trading name will appear on the card holder statement. Cannot exceed 17 characters
Provide your “sent from” email address for receipts to customers
Please provide an email address to receive a copy of email receipts by BCC.
your customers to contact your support team.
Provide a list of authorised users’ email addresses that can access Merchant Reporting. Passwords will be sent directly to the authorised users
The password used for authentication on the return post from the Latpay server to the merchant server.
The IP address of the merchant web server needs to be provided. Please notify Latpay before changing your IP address.
The URL in your server, to which customers must be redirected after 3dsecure authentication;
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.
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.
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.
URL on merchant website to which the customer must be returned when customer opts out of the payment process (by clicking the cancel button)
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.
The URL in your server, to which customers must be redirected after 3dsecure authentication;
URL to redirect the customer back to merchant site after authentication
URL to notify the transaction status in case of asynchronous processing.
URL to redirect the customer back to merchant in case of fatal errors
No. of stores where mPOS will be used
To uniquely identify the location of where the mpos is used. (up to 20 characters)
No. of devices/terminals in each store.
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
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
No. of stores where mPOS will be used
To uniquely identify the location of where the mpos is used. (up to 20 characters)
No. of devices/terminals in each store.
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
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
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.
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.
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.
URL on merchant website to which the customer must be returned when customer opts out of the payment process (by clicking the cancel button)
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.
