Send us your queries using the form below and we will get back to you with a solution.
If you wish to disable Payments2us Managed triggers follow the steps below. Go to ...
If you wish to disable Payments2us Managed triggers follow the steps below.
Go to Setup->Custom Metadata Types->All Custom Metadata Types->Payments2us Triggers->Click on Manage Records->Edit the Trigger you want to disable. Make your changes and Save.
Select the Trigger you want to disable. For example if you want to disable "accountTriggerHandler", click on Edit. Then select the Disable Triggers check box and Save.
When the System Administrator for your organization change and you want the payme ...
When the System Administrator for your organization change and you want the payments to run and authorize you as the user, follow the steps below.
When creating validation rules always include the condition "AND( ISPICKVAL(AAkPa ...
When creating validation rules always include the condition "AND( ISPICKVAL(AAkPay__Status__c,"Confirmation"), NOT(ISPICKVAL( AAkPay__Transaction_Source__c,"Recurring Payment"))" and then add your condition for validation.
Please note: This is for your information and validation rules are not covered by our standard support as they do not come delivered with the product. They are customization as per:Support Packages | Payments2Us
The code for creating the Household Account is completed by the Nonprofit Starter ...
The code for creating the Household Account is completed by the Nonprofit Starter Pack. We create Contact with Account blank and NPSP assigns household account.
The contact should be setup correctly with the household account. However, the Payment Txn will not have an account linked to it. If you want to have Account linked then you can may be create a process on Payment Txn object ( Please be careful while using Process builder as it can break things. use criteria Status- "Receipting Complete")
The person that receives this email is updated on the Payment Form - "Donor Care" ...
The person that receives this email is updated on the Payment Form - "Donor Care" field (1).
You will need to edit all Payment Forms that require this alert to be sent. The email is only sent when the total amount on the Payment Txn record exceeds the value entered on the Payment Form - "Large Payment Amount" (2).
You can specify Opportunity record type by going to Payment form->Opportunity ...
You can specify Opportunity record type by going to Payment form->Opportunity Record Type -> specify the record type you want the opportunities to be created with.
Notes:
If you have added a new Opportunity record type in Opportunity object, in order for that value to be available for selection in the Payment form you will need to add the same value to the Opportunity Record Type field in the Payment form. The values are not added automatically on Payment form.
If Opportunities are created with different record types even after specifying the Opportunity record type at Payment form. Then check the default record type for the Opportunity for the profiles. You can do that by going to Profile->Object Setting->Opportunity->record types.
The default opportunity owner will be the person that started the "Batch Processor" on the Merchant Facility. Batch Processor is found as detailed in FAQ
Please solve the error that has caused the status to be in Error. This could be d ...
Please solve the error that has caused the status to be in Error. This could be due to a flow/process or similar that failed. You can check this by going to the Payments2Us Error logs.
Check if the Payment is successful by going to link-
If so change Payment Txn Status from Error to Receipting Complete (use data loader or similar if large number of transactions) and then let the Batch processor runs and complete the transaction.
You will need to clone our Workflow as assign all of the related actions (Tasks/F ...
You will need to clone our Workflow as assign all of the related actions (Tasks/Field Updates/Alerts etc).
Then disable the Payments2Us original one.
Payments2Us is a managed package that is installed from the AppExchange. This mea ...
Payments2Us is a managed package that is installed from the AppExchange. This means that we can continually upgrade and organisations will get the benefits of enhancements.
The upgrades can be pushed to your organization by us, enabling us to keep all customers on the latest release without customers having to install the upgrades themselves.
To enable the automatic upgrades, not all components (such as workflows, email templates, letterheads) etc. have all items available for end customers to update. Only select details can be tailored by customers. The items that are available for your organisation to update are listed in the (1) Display More Information section.
The (2) "upgrade process" is where we push upgrades to your instance of Salesforce.
For more information about the above, please check salesforce online help guides for "Managed Package Upgrades", or "Managed Package Push" processes.
If your organisation is looking to implement IP Restrictions for the Payments2Us ...
If your organisation is looking to implement IP Restrictions for the Payments2Us User, then following is applicable.
The main Payments2us user that is connecting is the person that Authorises Payments2Us. This is a Salesforce user. So, the IP Address you need to restrict are Salesforce Server IP addresses. Please consult the Salesforce help guides for these IP address ranges.
Please note that Salesforce can change servers for redundancy fail overs or even during upgrades. You should therefore NOT restrict this to a single IP Address, but all that are listed with Salesforce. You should also update this list should Salesforce add new IP Ranges.
Check and Try the following: Delete the DEMO FACILITY in the Merchant Facility Ta ...
Check and Try the following:
The "Card Expiry Date" is automatically updated from the "Expiry MMYYYY" field. Y ...
The "Card Expiry Date" is automatically updated from the "Expiry MMYYYY" field.
You can use Data Loader of similar to update the "Expiry MMYYYY" and that will set the "Card Expiry Date" to the last day in the month from this field.
MM is the Month
YYYYY is the Year.
NOTE, this must be exactly 6 characters long. If updating for May 2022, then enter "052022" and NOT "52022". Ie. this field must have the leading "0" for months 1...9.
NOTE: This process has not been verified/checked. It is outside the scope of our ...
NOTE: This process has not been verified/checked.
It is outside the scope of our standard support and would require subscription to our Premium Support to implement or further guidance.
NOTE: This would work for Once of Payments and would require further refinement for Recurring Payments (E.g. Frequency of Monthly, Quarterly etc.)
1. Check Email Deliverability is Enabled Navigate to: Setup (Top right) Search "d ...
Navigate to:
Review the Workflow or Flow criteria and make sure the data on the triggering record matches the criteria.
For example, see the criteria in Why we are not receiving Large Donations email notification?
If the batch processor is not running, then the workflows could be triggered with the Force.com sites user and therefore do not have the level of access required. Please make sure the Batch Processor is running. Perhaps Stop/Start it if it is already running.
Navigate to:
Once you have a log file, try to locate the recipient email that you were expecting to see the alert sent to.
If you find the email in the log, then Salesforce attempted to send it. If you did not receive this, then this means your email server has blocked it. Please contact your email administrator and ask them to fix - This could include enabling DKIM (see section below).
It might be they need to whitelist Salesforce servers - for more information on this check the Salesforce help guides, or Contact Salesforce support.
The below information is provided as general advise and is NOT covered by the Standard Payments2Us support. If you need more information, please contact Salesforce Support, enquire about our premium support options or speak with your Salesforce Consulting Partner.
Emails being sent from the SALESFORCE server are NOT sent from your orgnisations email servers. Many email servers now check DKIM to ensure the sending server was authorised to send an email on your companies email behalf.
When enabling this, your organisation should setup DMARC/DKIM for all systems that send emails on behalf of your email server, for example Marketing email tools, finance for invoices, ERP etc. etc.
DMARC: (Domain-based Message Authentication, Reporting, and Conformance) is vital in the combating spam, phishing, and spoofing.
SPF: Sender Policy Framework (SPF) is used to authenticate the sender of an email.
You can check your DMARC and other server setups for your domain at: https://mxtoolbox.com/SuperTool.aspx
For information on how to setup DKIM, please see: https://automationchampion.com/2022/03/09/how-to-setup-dkim-key-in-salesforce-2/
For information on how to setup SPF, please see: https://automationchampion.com/2022/03/09/how-to-setup-sender-policy-framework-spf-for-salesforce/
If your Email Admin needs to whitelist Salesforce IP Addresses, please see: https://help.salesforce.com/s/articleView?id=000384438&type=1
If all of the above are checked and you are still not receiving the email alerts, you NEED TO contact Salesforce support. There is no more guidance that we can suggest.
The Created by User and Last Modified User are set by the Salesforce User that Au ...
The Created by User and Last Modified User are set by the Salesforce User that Authorises Payments2Us.
The Last Modified is subsequently set by the Salesforce User that Starts the Batch Processor.
The User the Authorises Payments2Us or Starts the Batch Processor should be a System Administrator.
If you wish to change the user associated with the Created or Last Modified User, then you'll need to re-authorise payments2us and/or stop/start the Batch Processor.
Payments2Us is a Site Based License. This means that all users that you give per ...
Payments2Us is a Site Based License. This means that all users that you give permissions to, can use Payments2Us.
It is imperative that all users that are using Payments2us have a Payments2Us Permission Set.
A user is anyone using any of the features of Payments2Us. This includes:
It is particularly important that the users that start the Batch Processor, Recurring Payment Processor or Xero Sync Processor have a Payments2Us Admin Permission Set.
Also see:
NOTE: For Experience Cloud external facing pages, the setup/security is the same as the Force.com Sites User.
Yes, they absolutely do. When Payments2Us push upgrades to your Salesforce Org, a ...
Yes, they absolutely do.
When Payments2Us push upgrades to your Salesforce Org, any new Fields added to Objects are not visible, even to System administrators. By having the Payments2Us Permission Set assigned, the appropriate level of permissions will ensure the System Administrator gets access to the newly added Fields and features.
Failure to have Permission Set assigned to the User the starts the Recurring Payment Process, Batch Process or Xero Sync Processor could mean these processes fail after a Push Upgrade is performed.
Please see Which Users Require Permission Sets for more details or How to setup Security for Internal Users for details on how to assign Permission Sets.