TABLE OF CONTENTS

The ability to seamlessly process online payments is essential for businesses of all sizes. A reliable Payment Service Provider (PSP) acts as the bridge between you and your customers' financial transactions.  Let Asperato, using the Payonomy Gateway provide you with that service.


Setting up your Merchant Management System


Before you can connect to the Payonomy Payment Gateway, you will need to complete the set up of your Merchant Management System (MMS) using the login details contained in the email we have sent you.


If you did not receive this email - please contact support@asperato.com for help


Once logged in to the MMS:

  • Select 'Merchant Account' - you will have a 'Test' option as a minimum and a 'Live' option once your acquirer MID has been provided
  • Select 'Preferences' and then 'Credentials' tab
    • In the 'Direct Integration' section, add the Asperato IP Addresses into both fields (Standard and Advanced)
      • 35.177.118.40
      • 35.179.25.58
    • In the 'Merchant Category Code (MCC)' section - if 3DS is required, please ensure this field is populated
  • Select the 'Acceptance Preferences' tab
    • Check and add/remove Currencies in the 'Merchant Accepted Currencies' section
    • Check and add/remove Card Types in the 'Merchant Accepted Card Types' section
  • All other settings can be left as default, please refer to the MMS User Guide for more information, or contact support@asperato.com



How to Connect Salesforce to the Payonomy Gateway

In order to connect your account to our Payonomy Gateway, you will need your Merchant ID (MID) as provided by your Acquirer and your Signature Key which you will be able to find by logging into your Merchant Management System (MMS) using the credentials we have emailed you.


It's a really simple process to connect once you have that information.  Make sure you have the 'Asperato Full Admin' permissions assigned to your user in Salesforce first and then login to Salesforce and navigate to 'Asperato Set Up' tab from the App Launcher.


Once there, create your Merchant Group/s as required and click 'New PSP Connection' and then enter the following information:


Payment Direction: Inbound

Currency: Choose your required currency from the list

Mode: This is the payment route by which your customers are paying you. If you are sending out a link for them to enter their own details, choose ECOM.  If you have an internal agent within Salesforce entering card details on their behalf i.e over the phone, then your route would be MOTO

PSP: Payonomy Gateway

Use Custom Gateway Details: Selected

Merchant ID: Provided by your Acquirer

Signature Key: Found in your MMS


Click 'Create PSP Connection'.  You should now see a green tick next to that connection on the set up page.  


If you are adding multiple currencies, you will need to complete the same steps for each currency and payment route you are collecting funds in.







Troubleshooting Issues


I can see a red cross next to my new connection - what do I do? 

Firstly - try deleting that connection using the 'Delete' function next to the connection and then try re-adding the details.  Often, we see a cross there if the Merchant ID or Signature Key have not been entered correctly.


Tried that and the connection is still showing as inactive?

Contact our support team at support @asperato.com for further assistance


Test Card Details


The Test Card details you need to use with your Payonomy Gateway:


Overview

Please note, the Card Numbers (PANs) mentioned in this article are to be used with Card Not Present transactions and with Test Accounts only. Do not use these test cards on live merchant accounts.

To test AVS and CV2 verification then the associated CVV and billing addresses are provided for each card. If a different value is used, then the Simulator will mark the responses as ‘not matched’.

The expiry date used for each test card should be December of the current year, in two-digit format

Visa Credit

Card Number

CVV

Address

4929 4212 3460 0821

356

Flat 6

Primrose Rise

347 Lavender Road

Northampton

NN17 8YG

4543 0599 9999 9982

110

76 Roseby Avenue

Manchester

M63X 7TH

4543 0599 9999 9990

689

23 Rogerham

Mansions

4578 Ermine Street

Borehamwood

WD54 8TH

 

Visa Debit

Card Number

CVV

Address

4539 7910 0173 0106

289

Unit 5

Pickwick Walk

120 Uxbridge Road

Hatch End

Middlesex

HA6 7HJ

4462 0000 0000 0003

672

Mews 57

Ladybird Drive

Denmark 65890

 

Electron

Card Number

CVV

Address

4917 4800 0000 0008

009

5-6 Ross Avenue

Birmingham

B67 8UJ

 

 

Mastercard Credit

Card Number

CVV

Address

5301 2500 7000 0191

419

25 The Larches

Narborough

Leicester

LE10 2RT

5413 3390 0000 1000

304

Pear Tree Cottage

The Green

Milton Keynes

MK11 7UY

5434 8499 9999 9951

470

34a Rubbery Close

Cloisters Run

Rugby

CV21 8JT

5434 84999 999 9993

557

4-7 The Hay Market

Grantham

NG32 4HG

 

Mastercard Debit

Card Number

CVV

Address

5573 4712 3456 7898

159

Merevale Avenue

Leicester

LE10 2BU

 

UK Maestro

Maestro Cards are not supported via MOTO on the Gateway. Maestro Test Cards can only be used by Direct and Hosted Integration and cannot be used via the MMS Pay Button Integration.

Card Number

CVV

Address

6759 0150 5012 3445 002

309

The Parkway

5258 Larches Approach

Hull

North Humberside

HU10 5OP

6759 0168 0000 0120 097

701

The Manor

Wolvey Road

Middlesex

TW7 9FF

 

JCB

Card Number

CVV

Address

3540 5999 9999 1047

209

2 Middle Wallop

Merideth-in-the-Wolds

Lincolnshire

LN2 8HG

 

American Express

Card Number

CVV

Address

3742 4545 5400 001

4887

The Hunts Way

Southampton

SO18 1GW

 

Diners Club

Card Number

CVV Number

Address

3643 2685 2602 94

111

N/A

 

 Diners Club do not support AVS. For testing purposes use a separate MID with AVS turned off.

 

 

 

3-D Secure version 2

For 3-D Secure v2 all the standard test cards will show as enrolled, and the authentication status returned by the Directory Server (for frictionless flow simulation) can be selected using the value of the card expiry month as follows:

Card Expiry Month

Auth Status

Simulation (Frictionless)

01 - Jan

Y

Fully authenticated

02 - February

N

Not authenticated

03 - March

U

Unknown authentication status

04 - April

A

Attempted authentication

05 - May

D

Decoupled authentication

06 - June

R

Transaction rejected (do not attempt to send for authorisation)

07 – July

E

Unknown error performing 3-D Secure checks

08 - August

E

Error due to timeout communicating with the Directory Server

09 – September

E

Error due to corrupt response from the Directory Server.

10 – October

I

Information only

11 – November

U

Unknown authentication due to Cardholder not enrolled (error 13)

12 - December

C

Frictionless not possible, challenge Cardholder

 

If the month required has passed for the current year the card will show as expired. Use the month required and the next years date to receive the expected response.

 

An expiry month of 12 will simulate the non frictionless flow and desired authentication status (threeDSAuthenticated) can be selected on the challenge dialog shown by the PIT Access Control Server.


You will be prompted to also enter 3DSv2 simulation responses in the test environment only - select the scenario you are testing from the drop down (NOTE: This is for TEST purposes only, not for LIVE transactions)