Duff OMelia's dashboard

A comment on the question "Some Implementation questions" in Spreedly:

None that we know of. :)

- Psyched about your gem – Duff OMelia, on November 20, 2009 17:18

Duff OMelia replied on November 19, 2009 21:36 to the question "Trouble updating subscribers via the API" in Spreedly:

I just looked at the logged actions on your site and there's nothing there to help with this issue.

Duff OMelia replied on November 19, 2009 21:26 to the question "Trouble updating subscribers via the API" in Spreedly:

We've got them here. Thanks for sending them. I don't see anything at first glance, but we need to spend some more time on it. We'll let you know through the email channel what we find probably sometime tomorrow.

If there's anything that's generally applicable to other folks, we'll post here too.

Duff OMelia replied on November 19, 2009 15:22 to the question "Customer ID for "listen for changes from spreedly"" in Spreedly:

It's the customer ID which you passed. Spreedly always talks in terms of *your* ID for your customer. So in your example, it would be 44763.

A comment on the question "Some Implementation questions" in Spreedly:

Sorry, which credentials / details? Just want to ensure I understand your question. – Duff OMelia, on November 19, 2009 14:42

A comment on the question "Some Implementation questions" in Spreedly:

Well, a subscription plan has a feature level. And the subscriber is potentially at a feature level at a point in time. So basically when the subscriber chooses a subscription plan, they get assigned that feature level so that in your app, you can ask a subscriber for their feature level and enable/disable parts of your app based on that feature level. Make sense? – Duff OMelia, on November 19, 2009 14:41

Duff OMelia replied on November 19, 2009 14:37 to the question "Please clarify subscription terminology" in Spreedly:

Active/Inactive: A subscriber is active if they have access to your site or service. (they've paid, been given a complimentary subscription, etc and their time hasn't run out yet)

Complimentary subscription : give a subscriber access to a feature level for a time. If they're already on a subscription and you'd like to give them a complimentary subscription at another feature level, you must first cancel them.

Complimentary time extension: just extend the time on the subscriber. Leave the feature level alone.

Free trial: Allow your customer access for a time free of charge. They're only allowed one free trial (unless you reset the flag with the API).

Lifetime complimentary subscription: Allow your customer lifetime access for free.

Auto Renewal stop: When a customer stops auto renew, we delete the credit card and won't auto renew when they're up for renewal. They'll go inactive when their time runs out.

Duff OMelia replied on November 19, 2009 14:13 to the idea "Site information should be able to be accessed programmatically" in Spreedly:

Thanks for the extra explanation. I don't believe we'd implement this feature for security reasons and I'm not sure how many folks will have enough Spreedly sites changing often enough to warrant it. I'll talk about it with the team though and update here we change our minds.

Duff OMelia replied on November 19, 2009 14:04 to the idea "Free subscription plans (not trials)" in Spreedly:

I'm wondering if a lifetime complimentary subscription would fit the bill?

Duff OMelia replied on November 19, 2009 14:01 to the question "Using the API, how do I upgrade/downgrade an existing subscriber to a different Subscription Plan?" in Spreedly:

I agree Barry. That's something that frustrates me as well and it's something that we're in the process of fixing. We'll update here when we've made some improvements.

Duff OMelia replied on November 19, 2009 13:55 to the question "More about how subscription upgrades are handled, please." in Spreedly:

Hi there,

I just added "make prorating optional" to our list of features to consider. I'm also wondering if there's a good way to make the prorating line item less confusing.

Duff OMelia replied on November 19, 2009 02:46 to the question "Trouble updating subscribers via the API" in Spreedly:

I'm confused at this point why you'd be getting a 401 when you're using the same authentication for a create subscriber as you would for an update subscriber. Is there any chance you might be willing to share what parameters you're passing and what the call looks like that you're trying to make? We're always willing to switch to support@spreedly.com email if that's something you're interested in.

I'm also wondering if this ruby library which is hitting our update subscriber api might be of assistance?

http://github.com/rlivsey/rspreedly/b...

I'm going to mull on the issue more tonight and check back in the morning. Not sure yet, but we'll get to the bottom of it!

Duff OMelia replied on November 19, 2009 02:37 to the question "Trouble updating subscribers via the API" in Spreedly:

OK... First up - the docs:

You're right that the main URL reference said POST rather than PUT which was a contradiction. We just fixed that.

You're right that it was confusing and inconsistent how in one place we were saying screen_name and in another screen-name. Underneath the covers, I believe Rails handles both, however we ought to remain consistent in the docs. We fixed the docs there.

I'll have more questions for you very soon.

Duff OMelia replied on November 19, 2009 02:01 to the question "Trouble updating subscribers via the API" in Spreedly:

Hi there,

Just wanted to let you know that I'm looking into the issue now.

Duff OMelia replied on November 18, 2009 14:12 to the question "Some Implementation questions" in Spreedly:

I hope I've answered all of your questions. Let me know if there's anything else I can help with.

Duff OMelia replied on November 18, 2009 14:04 to the question "Some Implementation questions" in Spreedly:

> Can you add an attribute to a subscriber for has_payment_info_stored? (would expect it a bool)

If the subscriber's "recurring" flag is set to true, then we've got payment information stored. Would this flag be sufficient?

Duff OMelia replied on November 18, 2009 14:02 to the question "Some Implementation questions" in Spreedly:

> Can a subscriber have multiple subscriptions? (if not, why not?)

I was hoping you would be willing to explain a bit more about what you'd like to do with multiple subscriptions to make sure I understand what type of functionality you were expecting.

Duff OMelia replied on November 18, 2009 14:00 to the question "Some Implementation questions" in Spreedly:

I'm hoping this page about feature levels might help explain better:

https://spreedly.com/manual/integrati...

Duff OMelia replied on November 18, 2009 13:58 to the question "Some Implementation questions" in Spreedly:

I thought perhaps I'd try to address each of your questions in a comment.

First up, the billing address payments api question. In this call:

https://spreedly.com/manual/integrati...

we need to update the docs for that call because you ought to be able to specify the following attributes on the credit_card:

* country
* address1
* city
* state
* zip
* phone_number

I've added a task for us to improve those docs. Sorry for the confusion! Please hit us up if it's not working as you'd expect.

Duff OMelia replied on November 18, 2009 12:11 to the idea "Accept Amazon Payments?" in Spreedly:

Yup. I'd consider PayPal express to be an offsite option. FPS is something we'd like to support, but it's a non-trivial implementation. Does Amazon offer another payment option besides FPS?

Long term, we'd like to give our customers the ability to use any gateway or payment system out there. Shorter term, we've been going after some low hanging fruit by implementing the gateways our customers request which are on the active merchant list: http://activemerchant.rubyforge.org/