*** Kaetemi has quit IRC | 00:04 | |
*** oshani has quit IRC | 00:07 | |
*** oshani has joined #cc | 00:19 | |
*** MarkDude has quit IRC | 00:21 | |
*** Danny_B has quit IRC | 00:23 | |
*** ankitg has quit IRC | 00:37 | |
*** tvol has joined #cc | 00:44 | |
*** JED3 has quit IRC | 00:48 | |
*** mralex has quit IRC | 00:49 | |
*** Danny_B has joined #cc | 00:50 | |
*** everton137 has joined #cc | 02:05 | |
*** oshani has quit IRC | 02:33 | |
*** akila87 has joined #cc | 03:09 | |
*** igorlukanin has joined #cc | 03:16 | |
*** igorlukanin has quit IRC | 03:25 | |
*** nkinkade has quit IRC | 03:25 | |
*** MarkDude has joined #cc | 06:01 | |
*** akozak has quit IRC | 06:01 | |
*** akila87 has quit IRC | 07:01 | |
*** wormsxulla has quit IRC | 07:15 | |
*** wormsxulla has joined #cc | 07:32 | |
*** everton137 has quit IRC | 08:46 | |
*** mattl has quit IRC | 08:46 | |
*** everton137 has joined #cc | 08:47 | |
*** mattl has joined #cc | 08:47 | |
*** stas has quit IRC | 08:50 | |
*** akila87 has joined #cc | 09:01 | |
*** igorlukanin has joined #cc | 09:09 | |
*** akila87 has quit IRC | 09:36 | |
*** bassel has joined #cc | 11:30 | |
*** wormsxulla has quit IRC | 12:00 | |
*** bassel has quit IRC | 12:01 | |
*** pmiller has joined #cc | 12:04 | |
*** pmiller has left #cc | 12:05 | |
*** igorlukanin has quit IRC | 12:12 | |
*** wormsxulla has joined #cc | 12:27 | |
*** pmiller has joined #cc | 12:28 | |
*** pmiller has left #cc | 12:29 | |
*** everton137 has quit IRC | 12:55 | |
*** midoubleko has joined #cc | 12:57 | |
*** tvol has joined #cc | 13:21 | |
*** akila87 has joined #cc | 13:24 | |
*** nkinkade has joined #cc | 14:05 | |
*** Odemia has quit IRC | 14:41 | |
*** Odemia has joined #cc | 14:43 | |
*** nyergler has joined #cc | 14:50 | |
*** igorlukanin has joined #cc | 14:51 | |
*** bassel has joined #cc | 15:01 | |
nkinkade | nyergler: Can I take it that you are okay with the idea of sending out good-faith receipts and invites, and in the rare case that one should later get rejected or cancelled that we simply update the CiviCRM db and re: notify all callback URLs with some relevant data? | 15:35 |
---|---|---|
nyergler | nkinkade, yes, i'm ok with that | 15:36 |
nkinkade | Good. I'll work out the details with John. | 15:36 |
*** Kaetemi has joined #cc | 15:39 | |
*** anttil has quit IRC | 15:50 | |
*** JoiIto has joined #cc | 15:52 | |
*** anttil has joined #cc | 15:54 | |
*** JoiIto has quit IRC | 15:59 | |
*** JoiIto has joined #cc | 16:09 | |
*** jgay has joined #cc | 16:19 | |
*** bassel has quit IRC | 16:35 | |
*** akozak has joined #cc | 16:46 | |
*** mralex has joined #cc | 16:54 | |
*** oshani has joined #cc | 17:10 | |
*** JoiIto has quit IRC | 17:18 | |
*** JoiIto has joined #cc | 17:28 | |
*** michi__ has joined #cc | 17:28 | |
*** igorlukanin has quit IRC | 17:33 | |
*** akila87 has quit IRC | 17:35 | |
*** Justuk4z has joined #cc | 17:42 | |
*** Justuk4z has left #cc | 17:42 | |
*** michi__ has quit IRC | 17:55 | |
*** akozak has quit IRC | 18:04 | |
*** Justuk4z has joined #cc | 18:05 | |
*** Justuk4z has left #cc | 18:05 | |
*** Tine_Tine has joined #cc | 18:32 | |
*** Tine_Tine has left #cc | 18:33 | |
*** JED3 has joined #cc | 18:34 | |
*** nyergler has quit IRC | 19:03 | |
*** JoiIto1 has joined #cc | 19:17 | |
*** JoiIto has quit IRC | 19:21 | |
*** michi__ has joined #cc | 19:28 | |
*** JoiIto has joined #cc | 19:48 | |
*** JoiIto1 has quit IRC | 19:48 | |
*** JoiIto has quit IRC | 19:53 | |
*** michi__ has quit IRC | 20:03 | |
*** JoiIto has joined #cc | 20:12 | |
*** JoiIto has quit IRC | 20:18 | |
*** JoiIto has joined #cc | 20:21 | |
*** nyergler has joined #cc | 20:25 | |
paroneayea | JED3: nkinkade: nyergler: we doing the devcall today? | 20:25 |
nkinkade | I'm here. | 20:25 |
nyergler | paroneayea, yes, five min | 20:25 |
nyergler | remind me which line we use :) | 20:25 |
paroneayea | we used 2 last week I think | 20:26 |
nyergler | great, calling momentarily | 20:31 |
nyergler | nkinkade we're dialed into line 2 | 20:33 |
nkinkade | nyergler: I'm here. One sec. | 20:39 |
nkinkade | My audio went out. | 20:39 |
nyergler | nkinkade, i'll send an email to you and paroneayea re: the landing of sanity | 20:42 |
nkinkade | nyergler: Do you want me to dial back in. | 20:42 |
nkinkade | Something with Karmic and the sound prefs and alsamixer. | 20:42 |
nkinkade | ... and Skype. | 20:42 |
*** bassel has joined #cc | 21:00 | |
*** tvol has quit IRC | 21:03 | |
JED3 | nkinkade: ping | 21:08 |
nkinkade | JED3: Hi. | 21:16 |
JED3 | nkinkade: sorry i figured it out | 21:25 |
nkinkade | JED3: How do you want to handle failed payments and disabling an auth code or cancelling a CC.net account. | 21:27 |
nkinkade | ? | 21:27 |
nkinkade | I'm going to code it so that CiviCRM will notify /a/invite again and pass some data. | 21:27 |
JED3 | sigh, so we send before contrib_status_id is set to 1? | 21:27 |
nkinkade | JED3: We weren't before, but this new way has some benefits, especially with Google Checkout. | 21:29 |
nkinkade | The main stumbling block was receipts. I suppose I could only ping an endpoint when the status is final. | 21:29 |
nkinkade | However, that still doesn't handle the case where someone make a subscription payment for, say, $10/mo for 12 months, then cancels it after just 1 month. | 21:30 |
nkinkade | I don't know if we care about that, but technically that would mean anyone could have a CC.net membership for as little as $7. | 21:31 |
nkinkade | Not that anyone would take advantage of that, but it seems like as a general purpose thing, it would be best for this to handle that, even if the endpoint ignores it. | 21:31 |
JED3 | too bad we can't apply a "reshelfing" fee if one decides to cancel after a month heh | 21:34 |
nkinkade | JED3: In a sense we would be already ... whatever they paid before they cancelled. | 21:35 |
JED3 | and pay off the balance for their awesome CC.net profile first :) | 21:35 |
mralex | do you get notified when each monthly payment is made? | 21:35 |
nkinkade | mralex: Yeah. | 21:35 |
mralex | you could have a rolling timeout for the account, that'll expire if they don't keep up payments :) | 21:36 |
JED3 | nkinkade: i would say we just ignore this case, since it's pretty rare, when we see someone cancel we'll manually deactivate on cc.net | 21:36 |
nkinkade | JED3: Most likely nobody would see it happen. It would all happen silently via the IPN. | 21:37 |
JED3 | ohh okay, well i think it would be useful outside of the cc.net use case to have notifications for cancellations wouldn't it? | 21:38 |
nkinkade | JED3: The other thing is that by sending a receipt and invite as soon as Google sends us the order notification (but before it's charged) is that users will get the receipt and invite nearly immediately, as opposed to having to wait 5 or 10 minutes. | 21:38 |
nkinkade | But there is that small chance that the charge could fail. | 21:39 |
nkinkade | Like I say, mostly this was an issue for the receipt, not ping the CC.net endpoint. | 21:39 |
JED3 | ohh ok | 21:39 |
JED3 | well if you feel that a fail case is rare enough to afford the confusion of sending a receipt and an email saying "oops that actually didn't work" then i'd say just send the receipt + generate the invite code upon receiving a google order notification | 21:40 |
JED3 | nkinkade: ^^ | 21:41 |
nkinkade | But I figured we might as well ping the endpoints too. I'm open to not doing it that way for your endpoint but for receipts it makes the most sense, I think. | 21:41 |
nkinkade | I honestly don't know how likely or frequent a fail might be. I'm assuming it'll be relatively rare. | 21:41 |
nkinkade | If we were selling car radios then I'd say no way, but in our case I'd say most donors are prepared. | 21:42 |
nkinkade | But JED3 the only thing about doing it that way is that your endpoint needs to be prepared to undo what it had done. | 21:43 |
JED3 | nkinkade: okay, well i can build a view to do this | 21:44 |
nkinkade | JED3: Does it have to be a new view? | 21:45 |
JED3 | well you be able to ping cc.net when this happens? | 21:45 |
nkinkade | Ideally it would be the same one, else I'll have to maintain two arrays of callback URLs. | 21:45 |
nkinkade | One for success and one for failure. | 21:45 |
nkinkade | It would be ideal to just ping the same URL and the app at the end would look at the data and figure out what to do. | 21:45 |
nkinkade | Then that may make your view non-generic. | 21:46 |
nkinkade | Ugh. | 21:46 |
JED3 | nkinkade: okay, but how would i know what to do based on contrib data? | 21:46 |
JED3 | yeah | 21:46 |
JED3 | i honestly think its best to send receipts and codes once 100% sure it went through | 21:47 |
JED3 | once we're* | 21:47 |
nkinkade | JED3: You're right, but that still doesn't account for the person who starts a recurring contribution, gets the invite, then cancels. | 21:47 |
nkinkade | As an example. | 21:48 |
JED3 | nkinkade: true | 21:48 |
nkinkade | I don't know how important handling that is to anyone ... maybe nyergler has input. | 21:48 |
JED3 | i don't automation is needed there | 21:48 |
JED3 | think* | 21:49 |
JED3 | allison just told me she gets emails when someone cancels a recurring contrib | 21:49 |
nkinkade | JED3: She does? Ah, if so, then we can just have her notify you. | 21:49 |
JED3 | yeah | 21:49 |
nkinkade | And I'll only ping your view when the contribution is fully charged. | 21:50 |
nkinkade | JED3: But I'm still going to send your endpoint a notification, even if it chooses to ignore it ... just to make this more useful to any other user of this functionality ... though I doubt anyone will ever use it. :-) | 21:51 |
JED3 | nkinkade: you mean once they reach 75 bucks in their contributions? what did you mean there? | 21:51 |
nkinkade | JED3: No, I mean if someone cancels the contribution at any time. | 21:51 |
JED3 | ohh ok | 21:51 |
nkinkade | Your endpoint now would just ignore it because it would recognize that it had already created an auth code for that trxn_id. | 21:52 |
JED3 | ahh, as long as the code wasn't deleted beforehand which i dont see happening | 21:52 |
JED3 | nm, i can disable codes without deleting them | 21:53 |
nkinkade | nyergler: I just decided to store the custom_custom data from the payment processor in a CiviCRM custom data field. It could conceivable be useful to us later and will allow me to only send receipts after the payment is secured. I just can't accept my other solution. As long as you have no problem with this, no response is necessary. | 21:57 |
nkinkade | s/custom_custom/custom_data/ | 21:57 |
*** nyergler has quit IRC | 22:03 | |
*** Kaetemi has quit IRC | 22:06 | |
*** Kaetemi has joined #cc | 22:06 | |
*** bassel has quit IRC | 22:12 | |
*** nyergler has joined #cc | 22:49 | |
*** akozak has joined #cc | 22:56 | |
*** Danny_B has quit IRC | 22:58 | |
*** _Danny_B_ has joined #cc | 22:58 | |
*** oshani has quit IRC | 23:17 | |
*** JoiIto has quit IRC | 23:18 | |
*** akozak has quit IRC | 23:36 | |
*** jgay has quit IRC | 23:56 |
Generated by irclog2html.py 2.6 by Marius Gedminas - find it at mg.pov.lt!