blink User Guide
Welcome to blink, a Blink Payment product, created and developed in-house.
This user guide will show all the handy features and navigation techniques to provide clarity for you, the Merchant User. This guide will show you how to take payments via the Virtual Terminal, send a Pay Link to your customer, create direct debits, change and personlise your blink account, run repos, check transactions processed and much, much more!
Once we have confirmed your set up, we will provide you with login credentials for access to the portal by the URL -
2. Your blink Dashboard
Your blink dashboard contains everything you need to have a full and comprehensive scope of your payment’s ecosystem. Here we will explain the different aspects of each part of the dashboard and where you can locate each section of the portal.
3. Dashboard Navigation
3.1 Payments/Card Payments
The payments option contains three drop down options which include the Virtual Terminal for over the phone payments. Pay Link to send to your customers via email and SMS and Standard Blink which is a page for your customers to populate for payment.
3.2 Direct Debits
Direct Debits provide the options to either set-up new customers with direct debits or view your existing and pending amounts
3.3 Transaction History
Transactions will allow the user to view all transactions processed internally via blink or externally from another payment source. There are two options, to view all transactions or just Pay Link transactions where you will have the oppounity to view the status, resend or cancel the sent Pay Link where required.
Analytics allows you to view your processing history in various formats relevant to the filters provided. These reports are comprehensive showing the progress of your day, week, and month. This option allows you to either run reports or view your analytics providing clear and comprehensive data of your business’ performance.
3.5 My 360
This section provides you the ability to interact directly with your customer-base and provide means of customising your blink account.
3.6 My Account
My Blink provides the user information regarding their account with Blink Payment. The information will show associated Merchant IDs, physical card terminals, payment gateways and support case history. This part of the portal will also allow the user to create a support ticket that gets sent to the client support team at Blink Payment.
3.7 User Information
User information displays the users full name, when clicked, this allow the user to log out if required.
Setting allows the user to see their information regarding the portal i.e. the lead account holders details, the ability to view and add users to the portal and your plan that shows the amount and access rights to parts of blink.
3.9 Live Chat
Here you can start a live chat with a Blink Payment Representative for any queries you have, big or small.
The Payments option provides two sub-headers – Card Payments (Virtual Terminal, Pay Link and Track Pay Links) and Direct Debits (Customers and Payments)
4.1 Virtual Terminal
The Virtual Terminal is designed for MOTO (Mail Order, Telephone Order) transactions and will allow you to process transactions for customers who provide card details over the telephone. By processing transactions this way, the virtual terminal will check the PAN (card number), expiry date, security code, first line of the address and postcode to ensure that the MOTO transaction is secure by matching the information entered to that which their bank have. Once this has been approved, you will receive a merchant receipt and your customer will receive a customer receipt. You can also create RTAs (Recurring Transaction Agreements) which are useful for processing transactions on a monthly basis and is common for subscription/service and charity industries. You can specify an amount and the number of instalments agreed with your customer.
4.1.A - Merchant account
4.1.B – Transaction type (Sale/Pre-Auth, Verify and Delayed Capture)
4.1.C – Full name of customer
4.1.D – Email address of customer (They will receive their receipt here)
4.1.E – Reference (This is for your reference; it can be in any format you wish)
4.1.F – Amount
4.1.G – Switch recurring ON (once switched ON, you can decide the number of monthly installments for the amount)
4.1.H – PAN (Card Number)
4.1.I – Expiry date
4.1.J – CVV (Security code)
4.1.K – Name of Cardholder
4.1.L – Registered first line of the address and postcode of car
4.1.M – Settle (process transaction)
4.1.N – Your Logo
Pre-Auth, Verify and Delayed Capture(payment functions and transaction history )
ProcessingPre-Auth, Verifications and Delayed Capture transactions on the Virtual Terminal or via a Pay Link allow the option for different method of transactions.
Please see the description of each transaction method below -
Pre-Auth – This allows a merchant to check if a customer has a specific amount available in their account and if the card is genuine. A merchant can then complete that pre-auth for any amount using that same card within 30 days. This allows merchants who work in industries where the final value of an amount is different or work on ad-hoc invoicing. Common with hotels and businesses that only know the final amount once work/product deployment has been completed.
Verify – A merchant can just check if a card is genuine by using this function. There’s no amount captured and just provides peace of mind for the merchant. Also, as we have stored the card data, we run a transaction for any amount in the future.
Delayed Capture – When a customer wants to pay at a later stage, the merchant can run a delayed capture transaction which runs on a timer that will collect the amount between 1-30 days. The merchant nor the customer will need to do anything, the gateway will process the amount once the number of days specified has been reached. If the merchant wants to process the amount sooner, they can capture the amount at any stage within the time-frame selected.
Payment and transaction functions:
This is how Pre-Auth, Verify and Delayed Capture appear in transaction history –
4.2 Pay Link/Pay Link History
The Pay Link function provides you the ability to send a button or link to your customers via email/SMS for them to pay by a hosted page. This very handy function allows your customers to pay at a later stage or if they feel uncomfortable to disclose card details over the telephone. You can also allow repeat payments and even allow your customer to decide the amount, this is quite popular with charities. The Pay Link History displays all the pay links you have sent, to view their statuses and to check if ones have been paid or not.
4.3 Pay Link/Pay Link History
Pay Links are used to send across links to your customers to pay via SMS or email. The Pay Link Generator allows you to just obtain the URL (Web Address) to send across to a customer. Potentially within a messaging service such as social media or live chat.
4.4 Direct Debits
The direct debit function allows you to create direct debits for your customers to pay in instalments, subscriptions or donations. As we have GoCardless plugged into blink, you can either connect to your existing GoCardless account or create one within the portal. Within this function, you can see your paid and pending instalments and once paid, will also be viewable within your transaction history.
4.4.A - Customers on Direct Debit payments
4.4.B - Payments received or pending
4.4.C – Connect to GoCardless
Here is where you can view all your transactions processed. This will include website, Pay Link, Virtual Terminal, Card Present and Direct Debit payments for a full scope of all transactions made within the business. Alongside your transaction history, you also have an analytics and reporting function. Here you can refine your search to a very specific degree and find trends in spending and even nd which type of card has processed the most.
5.1 Transaction History
The Transaction History page will display all transactions you have made via your Virtual Terminal, Pay Link, website or card terminal. Here you can locate a specific transaction to view its status to confirm if a payment was successful or unsuccessful.
5.1.A – Date search field
5.1.B – More Filters (Customer Name, Amount, Reference, Blink Unique Reference)
5.1.C – Date/Time of transaction
5.1.D – Customer name
5.1.E – Card Type used
5.1.F – Order Reference
5.1.G - Amount
5.1.H – Status (Accepted/Captured/Declined)
5.1.I – Transaction details – AVS (Address Check), CV2 (Security Code check), 3DS (3D secure check if applicable), Card Type, Auth Code(Authorisation code), Blink Unique Reference (specific to each transaction).
5.2 Action Button
The ‘Action’ button with the transaction history page provides different options from a transaction post-processed.
The options are –
Refund/Cancel – When a transactions status is listed as ‘Accepted’, a refund is required, this is where funds have been removed from a customer’s bank account and has been fully processed 24 hours after transaction has been processed.
‘Cancel’ will cancel a ‘Captured’ transaction. This can only happen within the same day and prevents funds being removed from the customers bank account.
Receipt – This allows the user to resend a receipt to the customer or to an alternative email address.
Re-Run – If a customer would like to purchase another item, a ‘Re-Run’ transaction will use the same card data to process an additional transaction saving time in re-collecting the card information.
Repeat –For subscriptions or instalments, ‘Repeat’ transactions will allow anunlimited/numbered cycles of transactions with varying frequencies – Once a day, week, month or year.
Our Analytics page is designed to provide a clear understanding and running totals of your payments eco-system. You can view analytics via the date range, Card Type and Card Scheme as well as viewing the totals of the trading week and month.
5.3.A – Running week and month totals
5.3.B – Date search field
5.3.C – Card Type and Card Scheme filter
5.3.D – Line chart of totals
5.3.E – Pie Chart of Card Type and Card Scheme
Along with Analytics, blink has a detailed and very comprehensive reporting function. Here you can maximise or minimize the search parameter to exact requirements and you will be able to download a .csv le to accompany your accounts. You will have the ability to search the card scheme, card type, acquiring bank, currency, transaction type and much more. The reporting feature allows you to save your preferred searches which you can call on at any point.
5.4.A – Date parameter
5.4.B – Card Scheme (Visa, MasterCard, Amex)
5.4.C – Card Type (Credit, Debit)
5.4.D – Acquirer (AIB, Elavon)
5.4.E – Currency
5.4.F – Transaction Type (MOTO, ECOM)
5.4.G – Status
5.4.H – Apply filters selected
5.4.I – Add filters
5.4.J – Additional Filter parameters
5.4.K – Search Operation (equal to, less than etc.)
5.4.L – Search query
5.4.M – Add more filters
6.1. My Account / My Blink
This section of the portal will provide you means of viewing active accounts and equipment you have through Blink Payment. This includes merchant ID(s), card terminals, payment gateways and support cases raised to provide a full overview of information.
6.1.A – Select Merchant Account will display information of your merchant account(s) you would like to view. If you have one account, information for only one will be displayed. If you have more than one, you can tick the top box to display all or click an individual box to display the information for that account.
6.1.B – MID (Merchant ID) – This is your merchant ID supplied by your acquiring bank.
6.1.C – Acquirer – This is the bank that process your transactions and who provides the merchant ID.
6.1.D – Address – Trading address remove ‘site’.
6.1.E – Contact Details – Email address and telephone number of site contact.
6.1.F – Gateway – Payment gateway used to process ECOM/MOTO transactions (Will only show if you have a payment gateway).
6.1.G – MID (Merchant ID) – The merchant ID related to that equipment.
6.1.H – Repo Fault – You can raise a case If you are experiencing technical issues with the gateway
6.1.I – Terminals – The list of hardware equipment.
6.1.J – Info – The full technical specification of your equipment.
6.1.K – Terminal type – The model of card terminal.
6.1.L – TID (Terminal ID) – The unique ID for that terminal.
6.1.M – MID (Merchant ID) – The merchant ID related to the terminal.
6.1.N – Repo Fault – You can raise a case if you are experiencing technical issues with the terminal.
6.1.O – Date/Time – Date and Time of when your support case was raised.
6.1.P – Support Member – Member of the support team dealing with your case.
6.1.Q – Ref Number – Your support case number.
6.1.R – Case Subject – Subject header of case raised.
6.1.S – Status – This will show where your case is up to (New, Pending or Resolved).
Invoices issued by Blink Payment will appear within the My Account area of Blink.
Displayed is the invoice name, amount the status (Paid or not), the date of the collection date and a link to view the invoice on Xero.
At the core of any product or service, support is not just a requirement but an obligation. Within blink, there are two ways you can obtain support from the dashboard by clicking on the icons displayed below
When the telephone receiver is clicked, you will be displayed with three options –
1. Contact Blink Payment by telephone.
2. Start a Live Chat with a support team member within the portal.
3. Create a case where you can raise an issue and have a support team member contact you to discuss. The last option will redirect you to the support case page where you have the ability to clearly dene your issue and submit this to Blink Payment.
When the blue message box is clicked, this will start a Live Chat with a support team member who will be able to diagnose any issue within the portal.
The settings page is located at the top-right of your screen and appears as the ‘gear’ icon. This is the control centre for your blink page and allows you to view and amend your account information, add and remove users, view your blink plan, add a portal logo and create/amend a blink page.
8.1 Account Details
Here you can amend your user details – email address, name, telephone number and update your login password.
Here you can add users you require access to the portal. The users are added in five separate group categories – Lead Admin, Supervisor, General, Payment Tier 1 and Payment Tier 2. Depending on which access level they are provided, will determine what they can view, use or amend within the portal. In order for the new user to gain access, you will need to ‘Activate’ their account which will trigger an email they will receive in their inbox. Once they click the link within that email, they are redirected to the portal to create a password and login.
8.2.E – Edit user information
8.2.F - Access list
8.2.A – Add a new user
8.2.B – Existing user
8.2.C – Activate user account (triggers email to user’s inbox)
8.2.D – Access levels
8.3 My Plan
This section covers exactly what we are charging for in terms of blink usage. You have the option for a free, tier 1 and tier 2 tariffs with blink covers all the benefits surround a specific tariff.
8.4 Portal Logo
Adding your logo to the blink portal provides added customisation for your account. The image needs to be – width: 100px / height: 60px and formatted to jpeg or PNG.
8.4.A – Where your logo will sit on the portal
8.4.B – Where to add your logo
8.5 Blink Page
A Blink Page is used to send a generic link to your customer for payment. It’s similar to a pay link but with the Blink Page you can add additional customisation in the form of a banner. This could be offers or discounts currently running at your business or shop opening times or even events. The blink customiser allows you to add images amend fields and set an appropriate layout of how you wish the page to appear. Once you are happy with everything, save the version, copy the URL link and now you have your Blink Page ready to send out to your customers or even advertise on your website.
8.7 Enhanced URL
A Blink user can process transactions in GBP (Great British Pounds), EUR (Euro), USD (U.S. Dollar), AUD (Australian dollar), CAD (Canadian Dollar), R (South African Rand) and ₪ (Israeli Shekel).
Enabled on the backend of the Blink Page, a merchant can amend the currency setting of that blink page to can add currencies they would expect to process.
When a merchant processes a VT payment or sends a Pay link, they can easily choose which currency they want to process on the front-end by clicking the currency symbol. This will allow merchants the ability to transact on the same blink page/account in varying currencies.
Merchant Blink Page Settings
Front-end VT and Pay Link
An Enhanced URL allows the ability to prepopulate specific fields within a Blink Page via the URL. Auser can amend the URL descriptors to match that of the software being used i.e. Accounting – Xero and QuickBooks
Normally when you’re using a blink page, its left to the customer to enter their name, email address, reference, and amount but with the Enhanced URL, you can add this information within the URL.
The above URL will populate the name and email address field.
A developer can amend fields in the page and add them within the URL with their values so that its prepopulated.
Below are the descriptors under the ‘Modify Fields’ tab of the customiser that can be amend for the URL.
9. Request A Feature
The ‘Request A Feature’ function allows you to notify our development team of any feature(s) you feel is missing from our platform. We consider merchant feedback a cornerstone to our development and growth of Blink. Once submitted you will receive an email notification confirming your feature request has been received and a response will be sent back to you with the result of our consideration.
10. Gift Aid
Charities can have this option added to a Blink Page or Pay Link and earn an extra 25p of each £1 donated when claimed from the HMRC.
A donor lands on the Blink Page or Pay Link page and click the Gift Aid box to declare that they are a UK taxpayer. All donations that have Gift Aid are saved within a separate reporting tool on Blink which can be exported and accompanied with accountsfor the HMRC declaration.
11. Payment settings
Within the payment settings, you can provide an email address where you would like your merchant copy of receipt sent to. Also, if your customer replies to their copy of the receipt, you can have a predefined email for that also.
Virtual Terminal Mandatory Fields will allow you to amend the Virtual Terminal to make specific fields compulsory for a user to populate.
12. Repeat Payments
Located within the transaction history, the Repeat Payments Manager will allow merchants to view all their recurring transactions set up previously or within blink.
What’s more, a merchant can create a Repeat Payment within this area by clicking ‘Create New’