On Tue, Jun 12, 2012 at 3:10 PM, kevin <kcr...@gmail.com> wrote:
> Etsy defines a receipt as "Represents proof of payment from a user to a
> shop for one or more transactions."
> That being said, why would was_paid ever be false? Can someone please
> explain the purpose of this field?
> --
> You received this message because you are subscribed to the Google Groups
> "Etsy API V2" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/etsy-api-v2/-/pigrbW3Z37QJ.
> To post to this group, send email to etsy-api-v2@googlegroups.com.
> To unsubscribe from this group, send email to
> etsy-api-v2+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/etsy-api-v2?hl=en.
Not everything is paid via paypal. . If a shop allows "other" payment, then
the shop owner has to manual mark an order as paid. Also, if an echeck
hasn't been cleared it's possible this would be false
From: etsy-api-v2@googlegroups.com [mailto:etsy-api-v2@googlegroups.com] On
Behalf Of kevin
Sent: Tuesday, June 12, 2012 3:10 PM
To: etsy-api-v2@googlegroups.com
Subject: was_paid... Why would this ever be false?
Etsy defines a receipt as "Represents proof of payment from a user to a
shop for one or more transactions."
That being said, why would was_paid ever be false? Can someone please
explain the purpose of this field?
-- You received this message because you are subscribed to the Google Groups
"Etsy API V2" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/etsy-api-v2/-/pigrbW3Z37QJ.
To post to this group, send email to etsy-api-v2@googlegroups.com.
To unsubscribe from this group, send email to
etsy-api-v2+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/etsy-api-v2?hl=en.
When a receipt is created was_paid is initially set to false. After the
associated transactions clear our fraud checking, credit card processing,
and other security measures was_paid is set to true.
This process typically happens rather quickly, but could take a while if a
transaction gets stuck in fraud check.
On Tue, Jun 12, 2012 at 3:10 PM, kevin <kcr...@gmail.com> wrote:
> Etsy defines a receipt as "Represents proof of payment from a user to a
> shop for one or more transactions."
> That being said, why would was_paid ever be false? Can someone please
> explain the purpose of this field?
> --
> You received this message because you are subscribed to the Google Groups
> "Etsy API V2" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/etsy-api-v2/-/pigrbW3Z37QJ.
> To post to this group, send email to etsy-api-v2@googlegroups.com.
> To unsubscribe from this group, send email to
> etsy-api-v2+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/etsy-api-v2?hl=en.
Thanks all for the responses. I'm using findAllShopReceipts to download a shops orders. It is becoming clear there may be some serious issues with my implementation. Let me explain my process: Step 1) download all orders created within 30 days (initial download) Step 2) import orders into our DB Step 3) wait 30 minutes Step 4) download all orders created after the most recent order downloaded
The main problem with this approach is if an order changes I will not pick it up again. This problem is exacerbated by the fact the order will change once it passes fraud check.
Any advice? I see the findAllShopReceiptsByStatus may be my best option. I'm not sure exactly how status works. Does an order have multiple statuses? For instance, an unshipped order should also be open and could possibly be unpaid. How does this work?
You are correct: an order can *meet* multiple status conditions. For
example if an order is unshipped it is also "open". An unpaid order is also
considered "open".
Any order that has a payment submitted but has not been marked as was_paid
will meet the "processing" status.
All other orders meet the "completed" status, meaning they are both paid
and shipped.
On Tue, Jun 12, 2012 at 6:05 PM, kevin <kcr...@gmail.com> wrote:
> Thanks all for the responses. I'm using findAllShopReceipts to download
> a shops orders. It is becoming clear there may be some serious issues with
> my implementation. Let me explain my process:
> Step 1) download all orders created within 30 days (initial download)
> Step 2) import orders into our DB
> Step 3) wait 30 minutes
> Step 4) download all orders created after the most recent order downloaded
> The main problem with this approach is if an order changes I will not pick
> it up again. This problem is exacerbated by the fact the order will change
> once it passes fraud check.
> Any advice? I see the findAllShopReceiptsByStatus may be my best option.
> I'm not sure exactly how status works. Does an order have multiple
> statuses? For instance, an unshipped order should also be open and could
> possibly be unpaid. How does this work?
> To post to this group, send email to etsy-api-v2@googlegroups.com.
> To unsubscribe from this group, send email to
> etsy-api-v2+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/etsy-api-v2?hl=en.
I want to download orders and keep their statuses up to date (primarily paid status). If I download a batch of orders and many of them are unpaid, the only way to determine if they are paid is to make an API call for each order. This will be a drag on both of us. I can cut down on some of the API calls by first requesting all unpaid order numbers and then only sending API requests on orders not returned by this call, but I worry if this might be error prone.
Do you have any recommendations on our app keeping etsy orders up to date?
I have a feature request: Through the API, allow me to download all orders for a shop based on change date. This would make my task so much simpler.
If I call findAllShopReceiptsByStatus and give it a status of unpaid, can I assume all orders that don't come back are paid? If an order fails fraud check, will it still come back as unpaid?
Same question for unshipped.
Also, is there a limit to the number of receipt_id's I can send for getReceipt?
I should point out that a lot of what I am saying applies only to "direct checkout". Etsy doesn't have any visibility into paypal, checks or money order transactions so in those cases it is largely up to the seller to determine when an order is marked as shipped and paid. More information on payment methods can be found here <http://www.etsy.com/help/article/189>.
On Wednesday, June 13, 2012 2:52:34 PM UTC-4, kevin wrote:
> If I call findAllShopReceiptsByStatus and give it a status of unpaid, can > I assume all orders that don't come back are paid?
If you call findAllShopReceiptsByStatus and pass in "unpaid" as the status, all other orders for that shop have "was_paid" set to true. In other words: "all"-"unpaid" = "paid".
> If an order fails fraud check, will it still come back as unpaid?
For direct checkout: If an order fails fraud check "was_paid" will remain false and the order will meet the "unpaid" condition.
> Same question for unshipped.
In direct checkout an order cannot be marked as shipped until "was_paid" is set to true. I'm not sure if that answers your question however.
> Also, is there a limit to the number of receipt_id's I can send for > getReceipt?
Thanks so much for your detailed responses. With regards to the was_paid attribute, can you confirm that the flow goes like this:
1. User buys an Item
2. Receipt is created, with was_paid=False
3a. If DIRECT CHECKOUT was used, was_paid gets set to True if the payment goes through, and stays False otherwise. 3b. If Direct Checkout was NOT used (user paid via PayPal, check, money order, or other), was_paid stays False until the seller explicitly marks the item as paid, at which point was_paid=True.
On Wednesday, 13 June 2012 17:01:27 UTC-4, Dan Miller wrote:
> Hi Kevin,
> I should point out that a lot of what I am saying applies only to "direct > checkout". Etsy doesn't have any visibility into paypal, checks or money > order transactions so in those cases it is largely up to the seller to > determine when an order is marked as shipped and paid. More information on > payment methods can be found here <http://www.etsy.com/help/article/189>.
> On Wednesday, June 13, 2012 2:52:34 PM UTC-4, kevin wrote:
>> If I call findAllShopReceiptsByStatus and give it a status of unpaid, can >> I assume all orders that don't come back are paid?
> If you call findAllShopReceiptsByStatus and pass in "unpaid" as the > status, all other orders for that shop have "was_paid" set to true. In > other words: "all"-"unpaid" = "paid".
>> If an order fails fraud check, will it still come back as unpaid?
> For direct checkout: If an order fails fraud check "was_paid" will remain > false and the order will meet the "unpaid" condition.
>> Same question for unshipped.
> In direct checkout an order cannot be marked as shipped until "was_paid" > is set to true. I'm not sure if that answers your question however.
>> Also, is there a limit to the number of receipt_id's I can send for >> getReceipt?
It has been my experience that a reciept doesn't come through the API when direct checkout has been used prior to payment going through. I've not seen an instance where was_paid is false when using paypal. I haven't tested with credit card yet...
On Tuesday, July 3, 2012 8:22:46 AM UTC-5, Dan wrote:
> Hi Dan,
> Thanks so much for your detailed responses. With regards to the was_paid > attribute, can you confirm that the flow goes like this:
> 1. User buys an Item
> 2. Receipt is created, with was_paid=False
> 3a. If DIRECT CHECKOUT was used, was_paid gets set to True if the payment > goes through, and stays False otherwise. > 3b. If Direct Checkout was NOT used (user paid via PayPal, check, money > order, or other), was_paid stays False until the seller explicitly marks > the item as paid, at which point was_paid=True.
> Thanks,
> Dan
> On Wednesday, 13 June 2012 17:01:27 UTC-4, Dan Miller wrote:
>> Hi Kevin,
>> I should point out that a lot of what I am saying applies only to "direct >> checkout". Etsy doesn't have any visibility into paypal, checks or money >> order transactions so in those cases it is largely up to the seller to >> determine when an order is marked as shipped and paid. More information on >> payment methods can be found here <http://www.etsy.com/help/article/189>.
>> On Wednesday, June 13, 2012 2:52:34 PM UTC-4, kevin wrote:
>>> If I call findAllShopReceiptsByStatus and give it a status of unpaid, >>> can I assume all orders that don't come back are paid?
>> If you call findAllShopReceiptsByStatus and pass in "unpaid" as the >> status, all other orders for that shop have "was_paid" set to true. In >> other words: "all"-"unpaid" = "paid".
>>> If an order fails fraud check, will it still come back as unpaid?
>> For direct checkout: If an order fails fraud check "was_paid" will remain >> false and the order will meet the "unpaid" condition.
>>> Same question for unshipped.
>> In direct checkout an order cannot be marked as shipped until "was_paid" >> is set to true. I'm not sure if that answers your question however.
>>> Also, is there a limit to the number of receipt_id's I can send for >>> getReceipt?
