Need Help? Let's Find the
Answer Together!

Sorry, we didn't find any relevant articles for you.

Send us your queries using the form below and we will get back to you with a solution.

Matching Rules

Topics on Matching Rules

Why is the Account missing on the Payment Txn?

This may happen for organisations that are using the Nonprofit Success Pack. For ...

This may happen for organisations that are using the Nonprofit Success Pack.

For some background: In standard Salesforce, a user would normally create an Account first, then setup the related Contact.

When Payments2Us goes through the matching process to locate contacts and create/update Accounts/Contacts and if it needs to create a new Account/Contact then in a standard Salesforce instance, it creates the Account First, then the Contact.

For Nonprofit Success Pack (NPSP)

When the Nonprofit Success Pack (NPSP) is being used, Payments2Us does NOT create the Account, it simply creates the Contact and the NPSP automatically creates/manages the Household Account for that contact. I.e. Payments2Us are not in control of the creation of the Account and do not have access to the details about the account at the time of processing.

For Person Accounts

Payments2Us will only create/link the Account if the Payment is for an Orgnaisation/Company level type payment. If it is for a contact/person level then it will not create or link the Account.

Possible ways to address

Should your desire to have the Account on the Payment Txn, you'll need to add your own Flow to populate this. Setting up and providing advise on custom Flows is outside the scope of our standard support - If you need assistance, please contact your Salesforce partner or purchase a premium support pack.

What date is used on the opportunity close date?

When a opportunity is created, the close date is set to the related Payment Txn - ...

When a opportunity is created, the close date is set to the related Payment Txn - Bank Deposit Date and NOT the transaction date.

The primary reason for this is some organisations will integration Opportunities to their Finance system and this reflects the date the funds were actually received in their bank account.

If you need to amend this, please work with your Salesforce admin, Salesforce consulting company or our Premium support to create a flow to adjust this. Alternatively, simply add a field on the Opportunity with a type of Date and an API name of Transaction Date. The like for like copy of fields from the Payment Txn will then populate this field.

How can I change the Opportunity Name?

The opportunity name generated is based of the Payment Form - field: Payment Type ...

The opportunity name generated is based of the Payment Form - field: Payment Type, plus the Contacts name and the Close Date.

If you wish to assign your own naming convention, then you can add a custom Flow that updates the Opportunity - Name field.

Working with State and Country/Territory Picklists

At this point in time, Payments2Us does not support working with State and Countr ...

At this point in time, Payments2Us does not support working with State and Country/Territory picklist enabled.

If your organisation has State and Country/Territory enabled, then you can do one of the following:

  • Disable State and Country/Territory. To do this, go to setup (Cog - top right corner), then search "State and Country/Territory", the select Disable Button.
  • Add a new State and Country/Territory. To do this, go to setup (Cog - top right corner), then search "State and Country/Territory", then press Configure "State and Country/Territory picklist" link.
  • Edit the Payment Txn record that has the invalid State/Country and update the State or Country to be a validate value. Also change the "Status" to "Receipting Complete" and save.
  • Add a Flow related to the Payment Txn, when the Status is "Receipting Complete". The Flow changes looks for commonly entered incorrect values and updates the States/Country with a correct value. NOTE: Our standard support does not provide assistance for setting up Flows.
  • If you are only using States with one country, then you could add a new Picklist field to the Payment Txn with a list of States, then create a Flow that copies this new value to MailingState on the Payment Txn when the status is at Receipting Complete and the new field has a value in it. 
    See procedure How to add custom fields on a web form for more details.
    NOTE: Our standard support does not provide assistance for setting up Flows.

Why do I get duplicate contacts when using NPSP

When the Payment Txn status changes from Matching Start to Matching Complete, pot ...

When the Payment Txn status changes from Matching Start to Matching Complete, potential contacts to link with are located using the Matching Rules on the Merchant Facility.

For the Nonprofit Success Pack (NPSP), a final check is made to ensure the First Name is ALWAYS a match as well. If the First Name does not match, then a new contact is created for the same household.

The reason for the First Name having significance in these Matching Rules is due to a "Household" individual contacts often sharing things like emails, address and phone/mobile numbers.

Why is the Payment Txn stuck on Matching Start Status?

If the Payment Txn Status is on Matching Start Status, then check: On the Merchan ...

If the Payment Txn Status is on Matching Start Status, then check:

  1. On the Merchant Facility related to the Payment Txn, check the picklist Field "Automatic Matching". If this is set to blank, "Match Only" or "Do Not Match" then the status is stay at Matching Start and will await for your admin user to go through the Manual Matching Process
  2. Check the "Error Log - Payments2Us" for any errors.