#R34P3R

1 messages · Page 1 of 1 (latest)

umbral topazBOT
winter summit
#

Hi there, you can search the payment_method ID in log, and click on the request that created the payment_method

remote geode
#

How can I programmatically via API do this?

#

I want to get a list of all manually (keyed in) payment methods

winter summit
#

Then check the details panel on the right, if the Origin is https://dashboard.stripe.com/ then it means this payment_method is created in Dashboard.

#

I don't think there's a way to do it programmatically through API

remote geode
#

How do I invite the user @near shell into this thread?

winter summit
#

You've already added this user in.

remote geode
#

He said he can't type.

umbral topazBOT
remote geode
#

Is there a way to see all manually keyed in cards/payment methods on the dashboard in one easy list?

acoustic plover
#

👋 Taking over this thread, catching up now

#

Is there a way to see all manually keyed in cards/payment methods on the dashboard in one easy list?
I'm afraid checking the payment methods one by one dashboard is the only way to identify the creation source

remote geode
#

That's really painful.

#

We were thinking we could use the API to iterate over all the receipts and math out which ones were charged 3.4% instead of 2.9% and thus deduce which were manually keyed.

Does that sound like it'd work, or would there be any hidden gotchas?

acoustic plover
#

I'm afraid I don't know the fee difference between the payment method created in Dashboard or the one input by the customer. I don't recommend using the fees to identify the creation source of the payment methods

near shell
#

I just had to agree to terms.

remote geode
#

In November 2022 Stripe started charging 3.4% for dashboard/manual cards vs 2.9% for cards taken in by customers thru a "normal" check out process (this of course is just the standard rate card)

acoustic plover
#

Although it might be possible, I don't recommend using the fee to identify the creation source of the payment methods as the pricing might change.

remote geode
#

Obviously, some kind of more direct way to figure out which cards were manually keyed would be preferable. Or even some kind of csv/tsv export.

#

Yea I agree with you, it wouldn't really be automated, but more like a one time thing to clean up some of our data.

#

And we could double check each of those methods before doing anything with them.

acoustic plover
#

In this case, you could have a try with using the fees to identify the creation source and verify against the Dashboard to confirm the payment method is indeed created by the Dashboard

#

Currently, the only way get the creation source of a payment method is via Dashboard

remote geode
#

Will the cards also have the Origin creation source?

#

(ie Cards vs PM's)

acoustic plover
remote geode
#

Thanks for the help, much appreciated !