sherrardb
sherrardb
`GET https://api.stripe.com/v1/customers/cus_GtHh3VC7Hhwgkc` for a non-existent customer produces: ``` { "error": { "code": "resource_missing", "doc_url": "https://stripe.com/docs/error-codes/resource-missing", "message": "No such customer: cus_GtHh3VC7Hhwgkc", "param": "id", "type": "invalid_request_error" } } ``` but the stringified...
the [API docs](https://stripe.com/docs/api/payment_intents/list#list_payment_intents-created) indicate `created` as a hashref, so we should be using `HashRef[Int] :$created?,`
similar to the test currently local.t ``` my $false = bless( do{\(my $o = 0)}, 'JSON::PP::Boolean' ); my $DATA = { 'client_ip' => '138.197.111.110', 'object' => 'token', 'type' => 'card',...
in some methods we `_post()` passed arguments directly: https://github.com/lukec/stripe-perl/blob/646861d829729d6d2c649ae1b426618d50f84914/lib/Net/Stripe.pm#L481-L492 but in doing so, we are unable to take advantage of any magic that happens during objectification: https://github.com/lukec/stripe-perl/blob/646861d829729d6d2c649ae1b426618d50f84914/lib/Net/Stripe/Resource.pm#L22-L26 and therefore have...
``` ~$ perl -Mstrict -Mwarnings -mNet::Stripe -e 'my $stripe = Net::Stripe->new(api_key => $ENV{STRIPE_API_KEY}); my $source = $stripe->create_source( type=> "card", token=> "tok_visa", metadata => { somecardmetadata => "testing, testing, 1-2-3", nested=>...
it is passed https://github.com/lukec/stripe-perl/blob/079e182a206cfe8ac2b0959ef5bc5359c96c168a/lib/Net/Stripe.pm#L1459-L1473 but not encoded, AFAICT https://github.com/lukec/stripe-perl/blob/079e182a206cfe8ac2b0959ef5bc5359c96c168a/lib/Net/Stripe.pm#L1677-L1714 and it looks like `date` may have been changed to [`due_date`](https://stripe.com/docs/api/invoices/list#list_invoices-due_date)
per an IRC chat with stripe engineers: > That's an old endpoint that we don't recommend anymore. Instead you'd retrieve the Customer directly and expand the list of sources on...
my current reading of the [docs](https://stripe.com/docs/api/charges/object#charge_object-payment_method_details) and the response from `post_charge()` is that it is more robust to interrogate the `payment_method_details` than any individual `card` or `source` returned. just wanted...
i have found these to be very useful during development. ``` $Carp::Verbose = 1; $Type::Tiny::DD = 999_999; ``` and can mean the difference between ``` Unknown named parameter: card at...
in perusing some of the other SDKs, specifically looking for how they test various `Source` types, i discovered various test tokens, like `src_123`, which don't seem to work against the...