Is there any way to download a list of transactions in your Google Pay account via their API?
There seems to be very little documentation for Google Pay, and the only docs I can find just explain how to use the Web/Javascript based API to request and process a payment. There doesn't seem to be any functionality in the API for requesting historical payment records in the account. Is that feature just not supported?
Related
I am currently looking into the W3C Payment Request API as part of a project for a new e-commerce checkout flow (mostly for supporting faster check-out using Apple Pay and Google Pay).
From looking at the API specification's change history, it looks like this change instituted earlier this year removes support for requesting the buyer's address with a payment request. The documentation of our payment service provider still shows this option, and it seems to work for now. That being said, I don't want to rely on a feature that browsers might start dropping soon because it's no longer in the standard, breaking our checkout flow.
Does anyone know if there is a recommended new way to handle this via the API, or if it is advisable to move the collection of the buyer's billing and shipping addresses back to a form on our page even when using the payment request API?
As far as the Payment Request API is concerned, I think there three primary options:
Apple Pay
Google Pay
basic-card
As you may have seen, basic-card is being deprecated (https://blog.chromium.org/2021/10/sunsetting-basic-card-payment-method-in.html) so you probably want to avoid this option.
Both Apple Pay and Google Pay provide access to billing and shipping address, and can be accessed as payment methods in the Payment Request API, and both provide their own alternate APIs (Apple Pay JS API and Google Pay Online API).
I don't know about Apple Pay, but the advice for Google Pay is to use Google Pay Online API (which makes use of the Payment Request API when available). Google Pay provides a consistent API for browsers that do and don't support the Payment Request API.
Does anyone know if there is a recommended new way to handle this via the API, or if it is advisable to move the collection of the buyer's billing and shipping addresses back to a form on our page even when using the payment request API?
The guidance for Google Pay is to place the Google Pay button above manual entry fields and to collect shipping information from Google Pay so that users can users don't start filling in the form before realizing there was a faster checkout option available.
So prioritize the digital checkout options for users that choose to use it, and make use of billing/shipping information from the digital wallet APIs. Make manual form fields available (suggest that form fields also make correct use of autofill attributes) for users who don't have access to or choose not to use the other payment options.
Demo site available with this in action: https://paydemo.withgoogle.com
FYI, if you're looking to integrate Google Pay into your site and are using a JavaScript framework, consider using the framework specific components from Google Pay for easier integration: https://github.com/google-pay/google-pay-button
I will like to know if its possible to retrieve a list of the most followed users (say top 20 users) on twitter through twitter's api. I cant see how to achieve that through any of the endpoints. How do web apps like this https://socialblade.com/twitter/ get that kind of data?
Any insights on this will be helpful.
There is no API for this. You would need to take an opinionated view of the high-volume celebrity accounts, and then watch the accounts by polling the user endpoints regularly. You could also use the commercial streaming APIs to watch the most Tweeted accounts and check the user objects on a regular basis.
(note that this is the same answer you were provided on the Twitter developer forums)
Is it possible to pull transaction records from an existing account in Yodlee MoneyCenter?
I am trying to figure out if there is a public API for this.
Yodlee Moneycenter(now Yodlee Labs) is a platform which provides you much more than account aggregation features to use for free.
In case if you are looking for APIs to build something similar you can get access to the Yodlee APIs, which has been exposed to the developer community(though you have to pay for it).
Please visit developer.yodlee.com for more information about this.
I have managed to successfully create billing plans and agreements by using PayPal PHP SDK via REST API for the Web Service of company I work. However I could not find any document about how I should check the agreement payments made automatically.
I guess the webhooks are for this work but also I can retrieve the payment transactions via SDK.
There are the cons of both.
Con of using webhooks is that the website really should work all the time and there is no way to understand if I have missed a request. This is something I can not guarantee for all moment.
Con of using REST API, I should check for all the transactions of all agrements to sync with my DB.
Is there a better solution that I possibly miss or are those the only possible solutions.
What would be the best practice for checking received or missed plan payment?
The conversation on https://github.com/paypal/PayPal-Python-SDK/issues/69 would be relevant to you. Short answer is that while support for billing agreements in webhooks is underway, using IPN would be the best interim solution if you want to be push notified, else transactions of all agreements would need to be fetched.
Our company's system sends hundreds of small payments ($5 to $100 usually) per week to people via the API's offered by paypal and dwolla. Does google wallet's API offer an equivalent capability?
Looks like it's not supported in the API Reference :(
https://developers.google.com/wallet/objects/reference/v1/
Although there is no equivalent API, you may consider the Google Wallet Send Money feature:
http://www.google.com/wallet/send-money/
More info about features and restrictions here:
http://www.google.com/wallet/faq.html#tab=faq-send