🚀 Studio 2.1 Is Here! Smarter Insights with UTM Tracking & Analytics

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.

NonProfit Cloud

Topics on NonProfit Cloud

Why is a Gift Transaction created with an Unpaid status for future start dates?

Overview When a Gift Transaction (GT) is scheduled for a future start date in Pay ...

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?

Why am I getting the error Gift Transaction Id: data value too large?

Overview This article explains the cause and resolution for the Gift Transaction ...

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.

Gift Transaction Id: data value too large: [ID] (max length=18)

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.

 

  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.

 

 

Why the “Current Gift Commitment Schedule” field not automatically associated when Start Date is in the future?

Overview This Payments2Us NonProfit FAQ article explains why the Current Gift Com ...

Overview

This Payments2Us NonProfit FAQ article explains why the Current Gift Commitment Schedule lookup is not automatically populated when a Gift Commitment has a Start Date in the future. When the Start Date is in the past the schedule is populated automatically. The behaviour is due to how Payments2Us creates records via Salesforce’s Fundraising Business Process API and the fact that automatic population of this lookup is a recent Salesforce enhancement not yet handled by the current Payments2Us implementation.

 

Use Case / Scenario

  • A Gift Commitment is created with a Start Date in the future.
  • Payments2Us uses the Fundraising Business Process API to create Gift Commitment, Gift Commitment Schedule, and Gift Transaction records in Salesforce.
  • When the Start Date is in the past, Current Gift Commitment Schedule is auto-populated; when the Start Date is in the future, it remains blank.
  • The automatic association for future-dated commitments is a recent Salesforce change; Payments2Us plans to add native support for this behaviour in a future update.

    

How “Current Gift Commitment Schedule” works with Payments2Us

Payments2Us creates Gift Commitments using Salesforce’s Fundraising Business Process API, which also creates related Gift Commitment Schedule(s) and Gift Transactions. The Current Gift Commitment Schedule lookup identifies which schedule is active for the Gift Commitment. Because Salesforce recently added enhanced behaviour for this lookup, the current Payments2Us implementation does not yet automatically populate the lookup for future-dated commitments.

Payments2Us development team plans to include native support for this lookup in an upcoming update.

 

Relevant Questions this Article Covers

  • Why is the Current Gift Commitment Schedule not populated automatically when Start Date is in the future?
  • Why does it populate only when the Start Date is in the past?
  • Is this caused by Payments2Us or by Salesforce Fundraising API behaviour?
  • How can I populate this field for existing or new records?

 

 

Notes

This article reflects the current Payments2Us behaviour and the recommended interim actions. Once Payments2Us releases an update to support Salesforce's enhancement, the automatic association for future-dated Gift Commitments will be handled natively.

How does Payments2Us work with Nonprofit Cloud?

1. Introduction Payments2Us has always worked with Person Accounts and has been a ...

1. Introduction

Payments2Us has always worked with Person Accounts and has been able to run on Nonprofit Cloud from day one.

From version 9.11 onwards, Payments2Us has been enhanced not just work tightly with the Nonprofit Cloud specific objects and methods for managing Fundraising. We are now leveraging the power of the Nonprofit Cloud and enhancing it to enable the actual transacting of Donations via a number of methods including Credit Card, Direct Debits, PayPal, BPay, ApplePay, GooglePay, Cash, Cheque etc. etc.

2. Fundraising Business Process API

The way that Payments2Us seamlessly integrates with Nonprofit Cloud is through the Fundraising Business Process API.

This ensures that as new feature function are added by Salesforce.org, then Payments2Us can then leverage these new capabilities with minimal coding effort.

The graphic below show an overview of how the Fundraising Business Process API is integrated.

  • After a Payment is processed by Payments2Us, a receipt is sent out and the the Status is changed to NPC Processing Start
  • The Status of NPC Processing Start calls the Fundraising Business Process API
    • If the Payment Txn - Frequency is Once-off, then the Gift Transaction API is called and this then creates the PersonAccount/Account, Gift Transaction and related Objects.
    • If the Payment Txn -Frequency is NOT Once-off, then the Gift Commitment API is called and this then creates the PersonAccount/Account, Gift Transaction and related Objects.

3. Payments2Us and Nonprofit Cloud High Level Data Model

The data model below shows a very high level overview of how Standard Salesforce Objects, Payments2Us Objects and the Nonprofit Cloud all work together.

As of Payments2Us version 10.1, the following Nonprofit Clouds Objects are catered for:

  • Gift Commitment
  • Gift Commitment Schedule
  • Gift Transaction
  • Outreached Source Code
  • Gift Designation

As of Payments2Us version 10.1, the following key standard Salesforce Objects be used Nonprofit Clouds Objects are catered for:

  • PersonAccounts
  • Accounts/Contacts
  • Campaign
  • Other objects normally catered for by Payments2Us are also being used

As of Payments2Us version 10.1, the following Nonprofit Clouds Objects are NOT catered for:

  • Gift Soft Credit
  • Other objects not listed above as being included

In addition to the above, Payments2Us will copy like for like api field values form the Payment Txn Object to the Gift Transaction or Gift Commitment Objects

4. Payments2Us Support for Gift Designation

As part of version 10.1, we have introduced support for Gift Designation object as well. 

  • Gift Designation(AAkPay__Gift_Desgination__c) picklist field is introduced in “Payment Txn” and “Payment Item” object respectively.
  • You can go to this picklist field and add picklist values in it. Each picklist value should be the “exact” name of your gift designation. 


     
  • Once the Payment Txn moves to NPC Processing Start stage, our job will use the picklist value to get the gift designation Id and send it to fundraising API in order to link the respective gift designation(s).
  • You can add these picklist fields in the Splits Entry fieldset for Payment Txn and/or Payment Item.

     
  • If Gift Designation is populated for any of the payment item then value populated in the Payment Txn will be ignored.

5. Lookup Relations between NPC and P2Us objects

For internal purposes, text fields are used to store the newly created Gift Transaction, Gift Commitment, Gift Commitment Schedule, and Payment Instrument Id. However, to establish relationships between records, custom lookup fields can be created on the Payment Txn/Payment Item object.

Lookup Relationships on the Payment Txn Object

Ensure that the following lookup fields are correctly configured (API Names should be same):

  • Gift Transaction → API Name: Gift_Transaction__c
  • Gift Commitment → API Name: Gift_Commitment__c
  • Gift Commitment Schedule → API Name: Gift_Commitment_Schedule__c
  • Payment Instrument → API Name: Payment_Instrument__c

Lookup Relationship on the Payment Item Object

To establish a relationship between Gift Designation and Payment Item, configure the following lookup field (API Name should be same):

  • Gift Designation → API Name: Gift_Designation_Id__c

If the above mentioned lookup fields are present on payment txn and payment item object then these lookup will be automatically populated by Payments2Us.

Â