When do DSP chargebacks occur, and if they initially don't process when do they re-attempt?

Laura Donmoyer · June 2012

We uploaded a DSP list for chargebacks last Friday, and when we ran the DSP failure report over the past few days, it found none. We found this a little odd that not a single charge failed, so we manually went into the recurring area yesterday, tracked all the people from our DSP upload, and found that about 30% of the names on the list had not yet charged - and had a date of June 16th on them for attempt. My thoughts are that these charges did not process for one reason or another upon initial attempt last week, and are now set to retry, but I don't know for sure, and cannot find ANY information in the Help modules that confirms this. How do we know this is the case, and how does the system pick the date it chooses for re-attempt? In our situation, how did the date of June 16 get assigned to these charges when the initial upload was performed on 6/8? Does the charge for a DSP upload get processed immediately upon upload, or is it held for a perdiod of time?

Any thoughts or confirmation on this would be quite helpful - we want to understand how the dates are chosen!

Kent Gilliam · June 2012

Laura,

You might want to contact support and ask them to take a look at what happened following your upload. I don't have the access level to see your activity logs but they can take a look and see why it showed no DSPs failed but then reset the date. It could have been that the processing went down for just a bit so tasks during this time were reset to a later date or it may be a configuration you have. But Support will be the only ones that can see the activity and determine what happened.

If you would, please post here what you find out so if others experience this in the future they can find your solution.

Thanks!

Kent

Brian Mucha · June 2012

Kent Gilliam:
Laura,

You might want to contact support and ask them to take a look at what happened following your upload. I don't have the access level to see your activity logs but they can take a look and see why it showed no DSPs failed but then reset the date. It could have been that the processing went down for just a bit so tasks during this time were reset to a later date or it may be a configuration you have. But Support will be the only ones that can see the activity and determine what happened.

If you would, please post here what you find out so if others experience this in the future they can find your solution.

Thanks!

Kent

I'm interested in the other part of her question. When are they SUPPOSED to process?

We use DSP too, and it seemed like pretty much immediately.

Let us know what support says!

Kent Gilliam · June 2012

Brian Mucha:
I'm interested in the other part of her question. When are they SUPPOSED to process?

We use DSP too, and it seemed like pretty much immediately.

Let us know what support says!

I always thought it was immediately as well. I haven't worked much with a client doing DSPs but from the times I have and from things I've read it was my understanding that they processed immediately. I'll see if I can get someone from our TeamRaiser team to chime in here.

Kent

Brian Mucha · June 2012

"My thoughts are that these charges did not process for one reason or another..."

Did you try the Report Writer > Delayed Self Pledge > Delayed Self Pledge Failures Report?

http://help.convio.net/site/PageServer?pagename=Admin_Delayed_Self_Pledge_Report

"...upon initial attempt last week, and are now set to retry..."

I don't think they will retry automatically, right?

"In our situation, how did the date of June 16 get assigned to these charges when the initial upload was performed on 6/8?"

This got my attention enough to subscribe to the thread. That's weird.

When do DSP chargebacks occur, and if they initially don't process when do they re-attempt?

Comments

Categories