Payonomy

payonomy is asperato's psp gateway payonomy routes payment data between your salesforce environment and your chosen psps for payment requests, authorisations, refunds, and recurring billing instructions prerequisites setting up your payonomy merchant ids (mids) before you can connect the payonomy gateway to asperato, complete the setup of your merchant identification numbers (mids) in the merchant management system (mms) you can log in to the mms using the login credentials (username and password) contained in the email we have sent you if you did not receive this email, contact support\@asperato com mailto\ support\@asperato com log in to the mms at payonomy administration upon first login, you will be prompted to set up two factor authentication via the google authenticator app and asked to change your password you need to make some changes to the gateway mid settings within the mms, in readiness to connect to asperato select merchant account you will have a test option as a minimum when your initial user is set up this can be used for testing prior to receiving your live mids from your chosen acquirer when you have the live mid credentials from your acquirer and these have been set up, you will see these listed here click view on the mid that you want to view select preferences and then the credentials tab you need to repeat this step for each mid by selecting each one in turn from the merchant account tab and selecting view all other settings can be left as default, please refer to the mms user guide https //drive google com/file/d/1ri8ccdnf wpnr2ghmndbqszdzngwinzu/view for more information or contact support\@asperato com mailto\ support\@asperato com signature key you will also need the signature key from the mid, this is found by selecting the preferences tab and clicking on credentials connect asperato to payonomy to connect asperato to payonomy, your user must '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 on the asperato setup tab, click new psp connection 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 found in your mms, as described above signature key found in your mms, as described above click create psp connection you should now see a green tick next to this new connection 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 if you see a red cross next to your new connection, it is possible that the merchant id or signature key have not been entered correctly try deleting that connection using the delete function next to the connection and create it again contact support at support\@asperato com if the connection is still showing as inactive test card details the test card details you need to use with your payonomy gateway to test avs and cv2 verification, 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 the following card numbers are to be used with card not present transactions and with test accounts only do not use these test cards on live merchant accounts 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 v2 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 year's date to receive the expected response an expiry month of 12 will simulate the non frictionless flow the desired authentication status ( threedsauthenticated ) can be selected on the challenge dialogue shown by the pit access control server you will also be prompted to 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)