Support

Additional support Contact

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.

Support Home FAQ Import Files Why is an Opportunity not created for the first/ Auth transaction when importing recurring payment data?

Table of Contents

Overview Why this happens Can this behaviour be changed? Important note about customisation Summary

Why is an Opportunity not created for the first/ Auth transaction when importing recurring payment data?

Table of Contents

Overview Why this happens Can this behaviour be changed? Important note about customisation Summary

Overview

In some recurring or face-to-face import scenarios, the first record may appear without an Opportunity being created. This is usually expected behaviour.

Why this happens

The first entry is often an authorisation (Auth) record.
An Auth confirms the card is valid, but no funds are collected.
Since no payment has been received, Payments2Us does not create an Opportunity for this stage.

Opportunities are created only when an actual payment is processed.

Can this behaviour be changed?

Not through standard Payments2Us settings.
If your organisation requires Opportunities for Auth records, this can be done using Salesforce automation added to your own org.

Important note about customisation

Creating custom automation to change this behaviour is outside standard product configuration.
If you need assistance designing or implementing this, our team can help through a Support Package: Payments2Us Support Packages

Summary

Auth records do not create Opportunities because no funds are collected.
Opportunities are created only when the first real payment is taken.
Custom automation is required if you need a different behaviour.
Customisation support is available via Support Packages.

When selecting a file we get BLOB is not a valid UTF-8 string How do we create recurring payments from Import Files? What fields are required to import Credit Cards? What fields are required to import tokenised cards? How can I Import Direct Debits? Which Transactions will be charged when Importing Cards/Direct Debits? Do I need to do anything about the warning that is displayed in step 2 of the import file process? How many rows of data can I Import? Should I import Credit Card and Direct Debits in the one Import Batch? Should we import fundraisers first? Fundraisers are not being correctly matched, or are Created and linked to the wrong Account/Household When I process the batch, the "Import File Line Item Payment Txn's" are not being created In Peer-to-Peer imports, the fundraiser's contact role is being listed as Soft Credit, but I want it to be listed as Fund Raiser. How do I update it? I keep getting errors with "Bad value for restricted picklist", but I checked and the value is exactly as it appears in the picklist. What's wrong with it? How do I remove old custom import templates that I don't use any more? How to Import Expiry Date to Recurring record if the import file feature is not used to charge card or for an auth transaction? Do Import Files send Receipts? Why the Import has not loaded any line items or why is the total amount is $0 Why can users not save the Import File Templates or they are getting an access error to Import File Settings Object Which Campaign is allocated if there are multiple campaigns with the same name - e.g. John’s Birthday Why am I not getting the Import file processing email confirmation? How to trigger the import file processor manually? Why is the Expiry date not being stored on the Payment Txn and Recurring payment? Why is an Opportunity not created for the first/ Auth transaction when importing recurring payment data?

Updated at November 24th, 2025