Overview

When a Gift Transaction (GT) is scheduled for a future start date in Payments2Us, the system creates an initial Authorization (AUTH) transaction with an Unpaid status. When the first recurring payment is processed, a second GT is created with a Paid status.

Use Case / Scenario

• A recurring gift is scheduled to start in the future.
• Payments2Us creates an AUTH GT record (Unpaid, Banked Payment = No) at import.
• When the first payment runs, a new Paid GT is created.
• The initial Unpaid AUTH GT remains in the database, which can affect reporting if included.

How the “Gift Transaction” Process Works with NPC

• An AUTH GT is created for future commitments before any payment is processed.
• It remains Unpaid, with “Banked Payment” set to No.
• The first actual payment generates a Paid GT.
• The AUTH GT is not updated to Paid; it serves as a historical authorization.
• Reports and processes should exclude Unpaid AUTH GTs to avoid discrepancies.

Relevant Questions This Article Covers

• Why is a GT created for future start dates even before payment?
• Why does the first GT remain Unpaid while subsequent GTs are Paid?
• How should GT reporting handle Unpaid AUTH transactions?

Overview

This article explains the cause and resolution for the Gift Transaction Id: data value too large error that may appear in the Error Logs within Payments2Us.

The error commonly appears as:

Program Area: paymentTxnExtShareLockProcessor.paymentLock
Subject: Gift Transaction Id
Description: data value too large: xxxxxxxxxxxxxxxxxx} (max
length=18)

The log lists multiple Payment Transactions with the above message. 

What the Error Means

The error typically occurs when a flow or automation passes an invalid Gift Transaction ID—for example, including an extra character such as a closing brace (})—causing it to exceed Salesforce’s maximum 18-character ID length limit.

This usually occurs when:

• A flow was created where the Gift transaction ID is passed

Causes:

• Custom flows or automations inserting or updating the Gift Transaction ID field with malformed values.
• Conditional flows that trigger inconsistently, explaining why resetting the Payment Txn can sometimes bypass the issue.
  To confirm, temporarily disable custom flows affecting Gift Transactions or Payment Txns and re-test.

Recommended Actions:

1. Review Flows and Automations:
   • Check any custom Flows, Process Builders, or triggers updating Gift Transaction IDs.
   • Look for cases where an extra character or symbol is being appended to the record ID.
2. Test by Disabling Flows:
   • Temporarily disable relevant flows and reprocess the transaction to confirm the source.
3. Validate Field Values:
   • Ensure that all Gift Transaction IDs being passed are exactly 18 characters.
   • Remove any stray braces or formatting characters.
4. Reprocess Transactions:
   • Once corrected, reset the affected Payment Txn Status to NPC Processing Start and re-run NPC Processing.

If the payment txn record moves to Error status from NPC Processing Start state, please refer to the error logs. If there is any error log with the subject like “Fundraising API Response Error createGiftCommitment / createGiftTransaction” and response body as per the sample screenshot below:

Then please refer to the payment txn(s) moved to Error status and check the Frequency field of the payment txn. This error message is returned by Salesforce fundraising business process API when the frequency is incorrect or junk value.

Overview

You may see a Campaign on the Recurring Payment, but not on the resulting Gift Commitment. This behaviour is expected.

Payments2Us sends the Campaign to Nonprofit Cloud during the recurring donation process.
Nonprofit Cloud does not store the Campaign on the Gift Commitment record.
Instead, the Campaign is added to related Gift Schedules and Gift Transactions.

Can this be changed?

Not through Payments2Us settings. This behaviour is controlled by Nonprofit Cloud.

What if I need the Campaign on the Gift Commitment?

You can use your own Salesforce automation to copy the Campaign from the Gift Schedule to the Gift Commitment if required for reporting or internal processes.

Summary

• Campaign appears on Recurring Payment.
• Nonprofit Cloud places it on Gift Schedules and Gift Transactions.
• It does not populate Gift Commitment.
• Use automation if you need it stored there.

In Nonprofit cloud, when a Gift commitment is created, it does not create an initial gift transaction. This is because in fundraising setting you don't have “Create Recurring Schedule Transaction” checked.

In Setup > Feature Settings > Fundraising > Fundraising settings

Check the box “Create Recurring Schedule Transaction”

If this “Create Recurring Schedule Transaction” checkbox is unchecked then the fundraising business process API is not creating the initial gift transaction record.