Understanding the PushPay flow within ServiceReef

Understanding the Normal PushPay Flow in ServiceReef

In the world of online transactions, ensuring that donations and payments are processed smoothly is essential. For ServiceReef, most transactions—around 99% or more—follow a standard, straightforward process.

The Typical PushPay Flow

When a donor makes a payment through PushPay, ServiceReef expects to receive a successful transaction response immediately. In this scenario:

1. Transaction Occurs: A donor completes a payment through PushPay.
2. Instant Sync: ServiceReef receives a successful transaction response from PushPay instantaneously along with the final amount of the payment.
3. Transaction Recorded: The donation or payment is immediately reflected in ServiceReef, ensuring that the fundraising information is updated for the trip/participant.  

This process covers the vast majority of payments, providing a seamless experience for everyone involved. However, there are situations where transactions might not follow this perfect flow—these are typically scheduled recurring payments or transactions that fail. This is where ServiceReef’s nightly sync jobs come into play.

Handling Special Cases with Nightly Sync Jobs

ServiceReef has three main sync jobs designed to catch and correct transactions that don't follow the typical PushPay Flow:

1. Regular (Non-Recurring Payments) Sync

• Purpose: To handle one-time transactions that may not have been captured immediately due to errors or delays.
• Process: This sync checks for any updates to transactions since the last sync and ensures they are correctly marked as successful, failed, or refunded in ServiceReef based on the transaction status within PushPay.  Please note: any transaction that is failed/refunded within PushPay will not display for participants or admins within ServiceReef.

2. Recurring Sync

• Purpose: Specifically designed for recurring donations, which are scheduled in advance.
• Process: This sync runs nightly, looking for any recurring transactions that occurred based on the donor’s schedule. It ensures that these payments are processed correctly, adding new transactions to ServiceReef as needed.

3. Fix Incomplete Orders Sync

• Purpose: To complete any transactions that were started but not fully processed in ServiceReef, often due to a lack of immediate confirmation from PushPay.
• Process: This job searches for incomplete orders in ServiceReef and checks PushPay for corresponding transactions. If it finds a match, it completes the order in ServiceReef, ensuring that all donations are accurately recorded.

Conclusion

While most transactions with PushPay are processed smoothly and instantly, ServiceReef’s nightly sync jobs are there to catch and correct any that slip through the cracks. Whether it's handling one-time payments, managing recurring donations, or fixing incomplete orders, these sync jobs ensure that every transaction is accurately reflected, providing peace of mind for both organizations, participants, and donors.