I've tried to reach paypal suport so many times, with no success, so maybe you guys can help with this.
The problem: I'm working on a project that have a paypal account setted up, with 5 apps registered there. The paypal account is an old account that receives many recurring payments and we don't have a way to know in witch app the payments are comming, so I was asked to solve the problem trying to create just one paypal app but withou losing any subscription.
The question: How can I delete the apps on paypal dashboard and create a new one without lose any payments?
Thank you so much.
Deleting an app will either cancel the subscriptions, or it won't, but either way you won't be accomplishing your goal of "to know in which app the payments are coming", since nothing you do will move existing subscriptions to a new app, other than having the user cancel and subscribe again.
So, for your stated goal of "to know in which app the payments are coming", the best you can do is settle on which single app to use going forward, and always use that app for new subscriptions. There exists no way to keep old subscriptions active and have them take place in a different app.
And anyway, assuming you leave your apps active, each app can have its own webhook event listeners.
Related
Does anybody know, if there is a way to access the transactions made from (Google/Apple)Pay on the device?
I think of a way where the user first needs to grant the access to a specific card on his wallet to the app, before the sync is then started.
I am looking for a way to somehow verificate billings, which are initiated by our app, without handling the payment process itself. So I just want to "observe" it.
Thanks alot for any advice in the correct direction
I've been researching several different API gateway solutions to process payments, or to access bank account records, but that's all not really what the users will feel comfortable with.
Is there any way to implement a Webhook for automatic update of subscriptions on server side, in nodejs for example, for situations such as: the user renewed or canceled his subscription?
Currently I save the subscription data in my Database after purchase and use the Google Developers API to verify that it has been renewed or canceled when necessary.
However, for some Administrator routines I need to check all subscriptions at once and this includes calling the Google API for each one. This process is slow and can take a long time.
I could create a method that checks and updates all subscriptions according to the Google API response, and leave this process running through a Cronjob every day at night. I believe it will work, but a server-side Webhook would be the ideal solution.
Something which automatically notifies my server as soon as there is a change to a subscription so that I can update it in my DB immediately.
Found the answer. We can use Google Cloud Platform (GCP) to subscribe to topics and receive real-time notifications when a subscription change.
All steps are described in detail in their documentation: https://developer.android.com/google/play/billing/getting-ready#configure-rtdn
Not sure if the title makes sense, I will say this question is very similar to the one I posted yesterday but no response on seen here. I have a user sign up and select a plan, once they are set to said plan there is a trial day limit set using the stripe dashboard. I am not creating the subscriptions via the API. Once the day 30 days are up, how can I tell? Only way I can think of telling is checking if their account is older than 30 days and doesn't have a stripe token/last 4 numbers of their CC. There has to be a better way that is more secure and prevents them from canceling their card and still being able to use the service. I know there is no code in this post and should be, but the only code I think is relevant is in the linked post you should check out.
I should add, where should I put this code in my routes? And I am using node.js, express, swig, and stripe.
What you are looking for is Stripe Events. When an action happens on your account, Stripe issues an "event". You should set up a webhook in your dashboard, and an endpoint on your site or app to capture Stripe Events and process the data that is sent.
Stripe issues two perfect events for what you need: customer.subscription.trial_will_end which fires three days before the trial ends , and customer.subscription.updated which fires in multiple cases, including when the status is changed from trialing to active.
Read through the Stripe docs here to learn more.
I have an approved Instagram client (i.e. my app was reviewed an is live) and I wanted to add a new feature to the application. I've heard some applications were getting their clients revoked and I want to know, can I proactively submit my new features for approval before pushing them into production? Does anyone have any experience with this?
I just want to avoid the plug being pulled because my customers pay for my application and use it daily. I'd like to avoid any service interruption. My thought was to email someone on the Instagram API team but, I can't find an email.
What I'm going to do is create a new client and submit a new video with the new features demoed in sandbox, I think this is the best thing to do but I wanted to post here first to find out if anyone has some experience to share that might help me out. Thanks!
I been working on a app where the common user can subscribe to different plans, which give different perks.
I been trying to do this by using Stripe's payment component from xamarin component store
But for me, it seems like this component only give you the option to request a payment, but not subscript to a plan.
this leave me think, the only way i can make this happen, is to make the whole "payment and subscriptions to the plan" code on native IOS and Android, which i after bind up against my PCL
So to conclude what i'm looking for is a more simple way to create this functionality,
Thanks for your time,
So the Xamarin extension should really only be used to collect the credit card details and "tokenize" the card. The actual handling of the charge is done by your backend server (as described in the documentation for the extension under "Sending the token to your server"). Once you pass the otken to your backend, you can actually do anything you like with it-- including attach it to a Customer Record by setting the source-attribute when calling the Create a Customer API Endpoint. Once you've created the Customer record, you can then create a Subscription using your Plans.