Processing Instore Transaction
There are 2 ways to process instore transactions for your customers, should they choose to use humm as their payment option:
Two Processes
- Merchant Portal
- PoS Device
Merchant Portal
In order to process an order through the Merchant Portal, you will require an active humm Account, plus your login details.
What are my login details?
If you have misplaced or don't remember your login details, please reach out to [email protected], who will be able to provide this to you
- Login to your Merchant Portal via the login page
- Once you have logged in, select the New Applicationtile from the Dashboard, or select Applications > New Applications
- Enter the Purchase Amount and Barcode/VIP/Pre-Approval Number (if applicable), then press Next.
- Fill in the Customer Details into the form, making sure to verify all the information, then press Next.
- Continue to fill in the Customer Details into the form, again verifying the information, then press Next.
- After all the details have been entered and the application has been submitted, the customer will receive their agreement via email or SMS, which they will need to agree and sign to proceed. The customer will require an Unlock Code, which will be displayed within your Merchant Portal for you to provide to them.
- When the customer has accepted the terms and signed the application, the portal will update to an Application Approved page.
PoS Device
- Select humm as the payment option within your PoS terminal.
- This will prompt your terminal to ask you to scan the humm Barcode.
- The customer will generate this on their humm mobile App by selecting the βPayβ option within their App. This is where you will scan the customers Barcode.
-
Once this verification has taken place, the customer will be presented with the payment schedule and terms of the humm purchase, which they will need to confirm.
-
After the customer has read through their terms and confirmed the purchase, you will receive a response on your PoS terminal advising that the purchase is completed, as will the customer.
2-Barcode
Should you wish to process a humm transaction through your humm-supported PoS terminal, you will require an integration with your PoS platform. Speak with your PoS provider to receive support for this integration
If a customer would like to make a payment in-person via your PoS terminal, they will be required to have an active humm account and use the humm App or use the humm website App on their mobile device.
- The customer will need to login to their humm Account on their mobile device, then select the βBarcodeβ option in their home page.
- Select humm as the Payment Method in your PoS platform, then scan the barcode.
- After scanning the barcode, the customer's App will be updated with a contract and a second barcode. The customer will have to read and accept the T&C's, then scan their second barcode.
- The PoS Machine will then update and complete the transaction.
Pre-Population
This method of order generation suits merchants that use a CMS that captures a lot of the data required for the customer to authorize a payment through humm in their own system, then pre-populates that data into humm Merchant Portal, allowing faster application generation and less double handling.
- Within your CMS platform, enter the details for the customer, then select humm as the customers payment option. This will redirect you to a humm Application Form, within the Merchant Portal.
- The information that is applicable to the customers application details will be pre-populated when going through the process, to reduce the amount of double-handling of information to process the application
- Once the customer has confirmed all their details are correct, process the application.
- The customer will require an Unlock Code to accept and finalise their agreement. This code will be visible within your Merchant Portal.
- The customer will be sent an email with a PDF of their contract.
Require more information?
For more information required to implement this process, please refer to our Pre-Population API documentation.
Updated about 2 months ago