How the swipe transaction's preferred application date function works.
When creating or updating a swipe transaction, you can provide a preferred application date to control when the transaction is applied to an associated line of credit account within LoanPro. Preferred application dates are not required, but they can be helpful when reconciling transactions or aligning with business cut-off times.
Preferred application dates are only supported in Bring Your Own Issuer (BYOI) integrations.
How preferred dates work
Preferred application dates can be provided when creating a swipe transaction and when updating a swipe transaction via a swipe event. A preferred application date is provided by adding the "preferred-date"
payload parameter:
{
"swipe-id": "e39ed072-3ebd-4e21-bd18-4adf9f8jf5e3",
"card-uuid": "54e7a88f-5c8b-464b-abc5-fe9f20d7o204",
"amount": 24.97,
"merchant-name": "CVS",
"merchant-descriptor": "CVS/PHARMACY #111237",
"preferred-date": "2025-07-17"
}
When a preferred application date is provided, the date is always stored and passed to LoanPro where a series of validations occur:
- Preferred date must be after the current billing period start date
- Preferred date must be after the account's open date
- Preferred date must be after the original apply date (when updating existing transactions)
If the date provided does not pass all validations, LoanPro will adjust the preferred date to create the transaction. When an adjustment is required, the platform provides a system comment that returns the submitted preferred date, the newly adjusted date selected by the system, and which validation was not met. In some scenarios, the system comment will also specify whether the applyDate
, settledDate
, or both were affected.
Preferred date application scenarios
Here are some examples of preferred date scenarios and their outcomes:
Preferred date is prior to current billing period start date
- Preferred date:
06/15/2025
- Current billing period start date:
07/01/2025
- Transaction apply date:
07/01/2025
Result: Transaction is applied on the billing period start date
{
"preferredDate": {
"applyDate": "Preferred date was supplied as 2025-06-15, but was set as 2025-07-01 due to: Cannot be prior to billing cycle start date."
}
}
Preferred date is prior to line of credit account open date
Note: This scenario only applies when the line of credit account is not activated. If the account is activated, the swipe transaction will be applied on the current billing period start date.
- Preferred date:
03/07/2025
- Account open date:
03/19/2025
- Transaction apply date:
03/19/2025
Result: Transaction is applied on the account open date
{
"preferredDate": {
"applyDate": "Preferred date was supplied as 2025-03-07, but was set as 2025-03-19 due to: Cannot be prior to Open Date."
}
}
Preferred date is prior to the existing transaction's apply date
Note: This scenario only applies updating an existing swipe transaction.
- Preferred date:
07/05/2025
- Existing transaction apply date:
07/03/2025
- Transaction apply date:
07/03/2025
Result: Transaction is applied on the existing apply date
{
"preferredDate": {
"applyDate": "Preferred date was supplied as 2025-06-29, but was set as 2025-07-03 due to: Cannot be prior to billing cycle start date.",
"settledDate": "Preferred date was supplied as 2025-07-05, but was set as 2025-07-03 due to: Cannot be prior to apply date."
}
}
Preferred date is in the future
- Preferred date:
07/23/2025
- Transaction apply date:
07/23/2025
Result: Transaction is applied on the preferred date
Preferred date is in the current billing period but prior to the current date
- Preferred date:
07/04/2025
- Current date:
07/07/2025
- Current billing period start date:
07/01/2025
- Transaction apply date:
07/24/2025
Result: Transaction is applied on the preferred date
No preferred date is provided
- Current date:
07/07/2025
- Transaction apply date:
07/07/2025
Result: Transaction is applied on the current date