Address
304 North Cardinal St.
Dorchester Center, MA 02124
Work Hours
Monday to Friday: 7AM - 7PM
Weekend: 10AM - 5PM
SecureCall offers customers (merchants) different ways for their staff to take payments-by-phone.
This document describes the four simple steps staff take when using the SecureCall web based Virtual Payment Terminal to take their customer's payments over the phone.
The four simple steps mapped out below are:
Step 1: Secure the phone call with their customer
Step 2: Enter sales related information
Step 3: Monitor the customer's progress as they enter their card details
Step 4: Submit the payment
From your browser, visit:
Once successfully logged in, your calls are ready to be secured and you will be taken to this screen on the right.
The SecureCall application runs in conjunction with your Cloud telephone service.
By logging into SecureCall a connection is made between your phone service and the SecureCall Virtual Terminal.
Please make sure your phone service is operating normally and you can make and receive phone calls.
A call must be ‘active’ to be secured. That is, you will need to be talking to your customer before attempting to secure the call.
At any time during that conversation with your customer:
1. Open the browser window where you have the SecureCall page.
We suggest you say something like this to your customer:
"Great, now before I take your payment.
I will just secure this call so that you don't need to speak your details to me.
I'll get you to type them into your phone when ready......"
2. When you are ready, click on Press to Secure button.
- This is usually done in the moments just before you want to take the customer's payment.
- There is no need to secure the call until then.
We suggest you say something like this to your customer:
"OK. That's done. The call is secured"
n.b. If you have accidentally closed that window, simply go back to the SecureCall Web Page - https://client.securecall.cloud and login again even if you are already on a phone call with the customer.
Once the call is successfully secured, you and your customer will still be in conversation.
Only once the call has been successfully secured will the payment transaction window be presented to you. So you can be rest assured you won't see or hear the card details as the customer enters them.
You will be entering details in the first three fields.
Your customer will be entering their card details in the bottom three fields using their phone keypad.
We suggest you say something like this to your customer:
"Great, now that this call is secured, you can now go ahead and type your card details into the dial pad of your phone. Let's start with the card number and if you could finish with a hash"
The customer’s card details are masked and shown as asterisk (*).
You can see their progress but cannot interact with these bottom three fields.
If at any point the customer makes a mistake, you can let them know that you can reset that field for them using the reset button.
Once a field is successfully entered, a tick is shown.
Once you have all the details entered, the Submit Payment button will change from opaque to solid. Clicking it will submit the payment.
Once the payment is successful, you will receive a confirmation message from your Payment Gateway provider with the Transaction ID and Receipt Number.
At this point either you or the customer can choose to make another payment by selecting the button at the bottom of that window or complete your call. A hang up will take you back to the Secure Call window.
The following describes each of the fields:
Payment Action:
To only pay once, select Pay
To pay once and store the card details as a ‘token’, select Pay and Tokenise
To only store the card details, select Tokenise
Amount:
This is the amount to pay, in dollars and cents. There is no need to add a $ sign.
Payment Reference:
This is a unique reference for this payment, which will be used by your finance department to perform reconciliation and can be used as a receipt number if required for the customer.
Token Reference:
If you are tokenising the card, this is a unique reference for this tokenisation, which can be passed to your payment systems for future payments.
Name on card:
The name on card is to be used by your customer for this payment. Ask the customer to provide it. For some banks this must be an exact match.
Card:
This is the card number, which is entered by the customer on their keypad and ending with a hash (#). Please ensure that they do not read out this number to you.
Expiry:
This is the expiry date of the card, which is entered by the customer on their keypad, in the format DDYY and ending with a hash (#). This must be a date in the future (i.e., beyond the current month). Please ensure that they do not read out this number to you.
CVV:
This is the security code on the card, which is entered by the customer on their keypad, ending with a hash (#). This must be either 3 or 4 digits (depending on the card). Please ensure that they do not read out this number to you.