Send us your queries using the form below and we will get back to you with a solution.
The most common cause for this is importing a file that is not a CSV (for example ...
The most common cause for this is importing a file that is not a CSV (for example, importing an Excel format file). Check you're importing a CSV. If that doesn't solve it, try the steps below.
The simplest way to fix this is to open with windows notepad, then select File > Save As - Next ot the SAVE button, select "UTF-8" from the encoding picklist and then SAVE.
The different options for importing are: Import Credit Cards and Charge: [Payment ...
The different options for importing are:
NOTE: Data Trans payment Gateway does Not support items 1,2,3,4,5,7 . For item 6, it only supports to loading of the recurring payment, it cannot charge on import.
NOTE: For Stripe, EziDebit Payment Gateways do not support 4,5. You can import tokens, but not use those tokens for charging during the import process.
For the import process to create a recurring payment, you need to map:
Recommended additional fields
For the expiry date, this must be in MMYYYY format. Where MM is the expiry date and YYYY is the Expiry Year.
NOTE, the Month must be zero padded. I.e. "22024" is INVALID, but "022024" is VALID.
Ensure the values of the frequency match exactly with one of the valid picklist values. Failure to do so might result in the frequency being treated as daily. Valid values include: Daily, Weekly, Fortnightly, Monthly, Bi-Monthly, Quarterly, Six Monthly, Annually, Two Yearly
It is very important that your "Import Type Template" starts with "Credit Card - ". This sets the Payments Source to "Credit Card" and ensures processing works as designed.
When importing and uploading you should try and include as much contact informati ...
When importing and uploading you should try and include as much contact information information as possible. This will help for the matching de-duplication.
As a minimum the following are required:
Recommended additional fields
If you are looking at importing cards that have already been charged and you'd like the next payment to be scheduled, then you will need to set the (Payment Day to not be todays day of the month OR Start Date as a future date) AND have the "Enable Recurring" on the Payment Form set to "Yes - Tokenise on Signup, Charge on Selected Date"
If you are looking for more help, then contact support @ payments2us.com for a request to purchase premium support or consulting services.
It is very important that your "Import Type Template" starts with "Credit Card - ". This sets the Payments Source to "Credit Card" and ensures processing works as designed.
For Direct Debits, your Import Type Template (1) File type selected on the first ...
For Direct Debits, your Import Type Template (1) File type selected on the first step must start with "Direct Debit - ".
The Direct Debit mapping is not delivered with the product by default. You will need to set this up on the first import by saving the Import File Template on Step 2 as Direct Debit.
Note: If your import file is for initial loads only and you do not wish to create Opportunities, then select "Contact Load Only" checkbox on the first step of the import wizard.
Make sure you map the Account No. and BSB fields as part of the import
Please note the BSB need to be in "XXX-XXX" format.
Credit Cards For both Importing of Credit Cards or Tokens, the following apply: I ...
Credit Cards
For both Importing of Credit Cards or Tokens, the following apply:
Direct Debits
The warning "This Import Line Item field has no equivalent in the Payment Txn Obj ...
The warning "This Import Line Item field has no equivalent in the Payment Txn Object" message indicates that the Import is being uploaded, but will not stored on the Payment Txn object as part of the down stream processing. Many of these fields have special meaning and are only temporarily used as part of the upload process.
However, should you add a custom field to the Import File Line Item record and this message appears, then it may indicate that you have an issue or a typo. The normal reason for adding a custom field is so that the imported (Import File Line Item) is so data is uploaded to the Import File Line Item and once the Import File is processed, this value will be copied to a field with the same API name on the Payment Txn. The ultimate aim is to then have the field on the Payment Txn copied to the field of the same API name on the Account, Contact, Opportunity or Campaign Member objects when the batch processor runs.
The imports are not restricted by the number of rows, but by the overall size of ...
The imports are not restricted by the number of rows, but by the overall size of the CSV file. If you have a smaller number of columns, then you can Import more rows of data. As a general guide, you should be able to import 30,000 and possibly upto 55,000 rows of data.
Should you require more rows of data than allowed, then simply split your files into multiple CSV files and import separately.
Our recommendation is to split the two imports out. One particular thing to keep ...
Our recommendation is to split the two imports out. One particular thing to keep in mind is that Direct Debits need to have the Import File Type set to Direct Debit (See FAQ above on How to Import Direct Debits)
Absolutely. In particular if you are looking to Soft Credit a fundraiser, then we ...
Absolutely. In particular if you are looking to Soft Credit a fundraiser, then we recommend importing the fundraisers and selecting the "Contact Only Load" on the first step.
The Contact Only Load checkbox will import the contact and de-duplicate the contact with existing contact or create a new contact if they do not already exist. This will NOT create any related opportunities though.
Loading the contact first will ensure the contact can be found and when using the Nonprofit Success Pack, can be soft credited for with the subsequent uploads.
Import the Fundraisers First Most of the 3rd party providers only provide a few ...
Import the Fundraisers First
Most of the 3rd party providers only provide a few details about the fundraisers in their import files. These details are often just First Name, Last Name and Fundraiser Id's.
The Matching Process relies a lot on the Fundraiser Id on the Contact record already existing. The best practice is to Import the Fundraiser details first, then import the donation details as a second import.
When importing the Fundraiser Details, you can use the "Contact Load Only" option so that the process does not expect to be processing donations. If this option is checked, the creation of opportunities will be turned off.
Note: Make sure when the fundraisers are imported to be created as contacts first, map them to the First Name, Last name fields. Then in the donor import after the fundraiser import, the fundraisers' first and last names are to be mapped to Fundraiser First name, Fundraiser Last name fields.
To try and locate the cause of this, please check the following. Check error logs ...
To try and locate the cause of this, please check the following.
The NPSP application allows for soft crediting to contacts. It is based on the th ...
The NPSP application allows for soft crediting to contacts. It is based on the the contact role field is part of the Payment Item object.
You can repeat this procedure if you want to add the same or different default to other Record Types.
Once the fundraiser and donor details have been imported, the fundraiser contact will be added to the payment item as the Fund Raiser in their contact role and will be soft credited for that donated amount. For more information on how the NPSP soft crediting works, visit https://powerofus.force.com/articles/Resource/NPSP-Soft-Credits-Overview
Check to see if the picklist that is being used is a Global Picklist. If so, you ...
Check to see if the picklist that is being used is a Global Picklist. If so, you need to use the API Name value instead of the "Values" value. Regular local restricted picklists use the Value field.
If possible, set the Values and API names in your Global Picklist to the same values to make this step easier.
The templates are stored in a Custom Object called "Import File Mappings". Paymen ...
The templates are stored in a Custom Object called "Import File Mappings".
Payments2Us does not include a tab for this by default for the package. You can add a Custom Tab under setup.
After adding the Custom Tab, you will be able to then see the entries and remove those that you do not currently need.
Please add the following fields to the Import File Line Item object. Payment_CC_E ...
Please add the following fields to the Import File Line Item object.
Then while importing assign the values from the CSV / import files to these columns. This will set the Expiry date correctly on the Recurring Payment record.
YES - If importing and charging Credit Card details or Tokens. For this use case, ...
YES - If importing and charging Credit Card details or Tokens. For this use case, the Payment Txns are created with a Status of "Receipting Complete".
NO - For everything else. The Payments Txns are created with a Status of "Payment Complete". The assumption is the 3rd party system has already generated and sent a receipt.
If you would like to send receipts, then you will need to clone the Payments2Us Workflows that send receipts and adjust these to also send the receipts for import files. If you need a hand with this change, please consult your Salesforce implementation partner or ask us about our Premium Support options to help with the custom setup.
If the Import File is showing the "No. of Line Items" as being zero, then: Make s ...
If the Import File is showing the "No. of Line Items" as being zero, then:
The template mappings are saved into a Custom Setting File called AAkonsult Impor ...
The template mappings are saved into a Custom Setting File called AAkonsult Import File Settings. The users will need to have the profile setting "Customize Application" enabled.
For more information on custom settings, please see https://help.salesforce.com/articleView?id=cs_limits.htm&type=5
Campaigns that are visible to the user and are active are the ones considered. If ...
Campaigns that are visible to the user and are active are the ones considered. If multiple Campaigns with the same name exist, then the one with the more recent (highest) Start Date is used.