Getting Started
Sandbox Installation & Testing
this page will guide you through installing, setting up, and testing payments in a salesforce sandbox environment this page assumes you are familiar with basic salesforce concepts prerequisites my domain activate my domain in salesforce lightning for using customized domain names in sandbox environments see https //help salesforce com/s/articleview?id=xcloud domain name overview\ htm\&type=5 1\ install payments https //appexchange salesforce com/appxlistingdetail?listingid=a0n3a00000ecronuaj installation usually only takes a few minutes you will receive email confirmation from salesforce once the process has been completed after successful installation, open the app launcher and visit the unaric payments setup tab click the setup configuration button you will be asked to log in again and allow access permissions to unaric payments to finish the installation visit docid\ dx6cbkhlju t rmmwxddj for a full list disclosure of permissions access to check if your org is successfully connected with unaric payments, check the configuration status displayed on the unaric payments setup tab you should now be connected to an unaric payments test account in this tab, you will see a list of default payment service providers test accounts owned by unaric payments for a selection of currencies these allow you to take immediate test payments y additional features depending on your requirements and licence, unaric payments offers additional features you can set up at this stage during onboarding, support will help you implement these features for additional guidance, contact support at mailto\ support\@asperato com docid\ ilbk tv ycfumgycx0ggp docid\ ydxizy76p2uqbewl7tkex docid\ tgpsyjqqflnuzgilpgs5m 2\ testing at this stage, your sandbox unaric payments environment is connected to default test accounts with payment service providers (psps) for a selection of currencies you can use this psp to test payments this section will suggest different features to test one off payment testing never use real card details in a test payment form doing so can turn into a security breach and break pci compliance regulations this tutorial assumes you're connected to ayden as a test gateway, which is the default on installing the unaric payments package for end to end testing, we recommend connecting unaric payments to the test accounts of your chosen psps to this end, you will need your psp credentials see docid\ dbn9m9and tpg9lusxrqt for more information on testing, see docid\ ma 5nf9 ea5ltn6cp vxn try out the ayden connection by processing a simple, one off card payment navigate to the unaric payments tab click the new button on the action bar to create a new payment record enter any amount and select card as payment route option click save when the payment record has been created, click the process payment button fill in the form using https //docs adyen com/development resources/testing/test card numbers/ for example card number 4444 3333 2222 1111 issuing country/region gb zipcode any uk zipcode, such as sw1w 0ny expiry date 03/2030 cvc 737 click pay with card refresh the salesforce payment record to see the payment record completed once successful, the payment record status will update to collected from customer to test specific scenarios like failed payments due to insufficient funds or card expiration, check your psp’s website for test card details common methods include using specific card numbers, payor names, or amounts authorisation testing authorisations represent saved payment methods that can be used for repeated payments as such, you will use authorisations to process payments from recurring customers for more information, see docid\ f33l 1zecsfrnsvxhueo5 for testing, this tutorial will use a direct debit authorisation trough gocardless using testing credentials however, authorisations support multiple payment methods, including credit/debit cards, direct debit, ach/echeck, and paypal go to the unaric payments authorisations tab click the new button in the action bar select inbound as record type and click next in payment route options , select direct debit this is the only required field, and since it is a test, it is not necessary to fill in more information click save select the authorisation click the process authorisation button in the action bar a pop up screen will ask you to enter the payment information regularly, you would either share the authorisation with customers for them to enter the information or fill it yourself while communicating with them for this test, you can use https //developer gocardless com/resources/test bank details click update authorisation you will be asked to review and confirm the payment details click confirm after submitting the form, details of the authorisation will then show in the authorisation's page if the authorisation fails, the pop up screen will specify the error, the authorisation status will be updated to failed, and you will need to retry again; common fail causes include inaccurate information (such as invalid zip codes) and mismatches between banking and authorisation currency if the authorisation succeeds, it will be updated to pending until further approval from the psp once authorised, the repeated payments once you have set up the authorisation, you can use it to process payments on the unaric payments authorisation tab, select the authorisation record you created under the payments list, click new complete the payment details the authorisation field will be pre populated with the required authorisation record click save navigate to the payment record and click process payment using authorisation on the actions bar a pop up window will show you the authorisation details click process payment to finish payment schedule testing unaric payments' scheduled jobs automate the process of collecting recurring payments it's a background task that runs on a schedule to process due payments without this job, recurring payments wouldn't be automatically handled; you'd likely have to process them manually creating and scheduling apex jobs in salesforce requires system administrator privileges as such, you need to be a system administrator user to create it 1\ setup schedule job this feature is not active by default in non production environments to activate it, you need to schedule the apex job first navigate to setup > custom code >apex classes click the schedule apex button to create a new apex job set unaric payments repeat payment as job name on apex class, click the apex class lookup button (🔍) a new window will open select batchprocesspaymentschedules from the list in the schedule apex execution section, set frequency to weekly and tick all the days under recurs every week on select a start date (defaults to today) set an end date set a value a long time in the future such as 31/12/2050 set the preferred start time a suggestion would be 04 00 or 05 00 save this record and that will schedule the task payments can be used to collect payments automatically from authorisations see docid\ mr7d24nqdmzsfhovef2wd 2\ create a payment schedule on the unaric payments authorisations tab, select the authorisation record created in previous steps select the dropdown arrow by the payment schedules related list and click new the authorisation will already be pre populated fill in the rest of the required fields ( regular amount , frequency , and next payment date ) click save to finish the payment schedule is now active, and will collect overnight each time the following conditions are met the next payment date is set to either today, or is in the past the status of the payment schedule is set to in force the status of the authorisation attached to the payment schedule is in force payments schedules have fixed amounts and dates for collection if you need variable dates and amounts from schedule collecting from authorisations, you can use salesforce tooling to set up your custom schedule psp end to end testing unaric payments comes pre configured with its own testing psp connections so you can test payments out of the box however, you are limited to seeing the results in salesforce and cannot view the payments as they flow through the psp for end to end testing, you'll need to connect your own psp test account see docid\ dbn9m9and tpg9lusxrqt once you go live, it is strongly recommended to process a few live transactions to verify that unaric payments and your psp are configured correctly as such, when you start using live payment credentials, have a method for refunding test transactions below are links to test details for various psps https //docs adyen com/development resources/testing/ https //support authorize net/knowledgebase/article/000001517/en us https //developer blackbaud com/skyapi/docs/getting started/learn api https //braintree gitbook io/in person/get started 1/configure sandbox https //www checkout com/docs/developer resources/testing https //developer cybersource com/hello world/testing guide v1 html https //docs fortebank com/en/integration/card api/testing/ https //www postman com/gocardlessapi/gocardless api/documentation/28f4dal/gocardless https //intellipay com/category/credit cards/card testiing/ https //developer moneris com/more/testing/testing%20a%20solution https //support paya com/44616 paya virtual terminal all articles/315930 list of test card numbers https //github com/payeezy/get started with payeezy?tab=readme ov file#build and test your integration https //paylinedata com/blog/test card numbers https //developer paypal com/api/nvp soap/paypal payments standard/ht test pps buttons/ https //developer paypal com/api/nvp soap/payflow/payflow pro/payflow pro testing/ https //dock co uk/blog/sage pay test card details https //docs stripe com/test mode?locale=en gb https //www takepayments com/media/50rboxji/test card details version 2 2 0 pdf https //developer worldpay com/products/access/payments/testing