Making the react native app stripe to live mode - react-native

I am working on react native app and the app is using the test mode stripe and I am also making the test stripe to live,
I have a simple question, Is there anything I have to change while making the stripe to live mode,
I changed the switch to live in the stripe dashboard.
I changed the key and secret in app and server.
Do I also have to change something else?
And what are these and why and how are they used and where can I find these in the dashboard.
merchantIdentifier: 'merchant.com.stripe.react.native',
urlScheme: 'stripe-example',

The testmode toggle in the Stripe dashboard has no impact on what mode your integration is operating in, it only changes what data you're viewing in the dashboard. When the toggle is on, the Stripe dashboard will display the testmode data for your account, and when it is off you will see livemode data.
The secret and publishable key that you provide dictate what mode your integration will operate in, and are likely the only values that you need to change. source
The merchantIdentifier is not a value that you find, but rather is one that you set when you're registering for an Apple Merchant ID. It is an optional parameter that you can omit if you're not planning to accept Apple Pay payments. source
urlScheme is an optional parameter that is only needed if you're planning to manually handle the 3DS authentication flow rather than rely on the pre-built functionality that Stripe provides. source

Related

Are there any info or links that clearly covers paypal integration in react native?

I would like to setup a paypal payment method exactly the same as Airbnb. The payment will be recurring on a monthly basis.
If one user is directly paying another user for a fixed amount that recurs automatically every month between just their accounts (very different from AirBnB's setup), that can be done with a Subscribe button. The easiest integration will be to create a classic HTML-only Subscribe button via https://www.paypal.com/buttons , uncheck the option in Step 2 to save the button at PayPal, and once the code is generated click the link to remove code protection. This will give you a button with variables you can adjust, per HTML Variable for Payments Standard, including the business destination in particular.
Newer PayPal Subscriptions can be used instead, but are more complex to set up, as each user will need to have the appropriate recurring Plan created for them via an API call, and you will need their Client ID and Secret to do that from your server.
Since you are using React Native, it is important to note that all PayPal flows require a web interface that includes an address bar, such as Safari View Controller or Chrome Custom Tab. A WKWebView or similar cannot be used.

In-App Payment, is it possible to save a list of user's credit card in Android App

I'm trying to build up an android platform that takes in user credit card info and charge it on use without inserting the credit card details after saving one. But I don't seem to actually see any possible work ways in the "In-App Payment" SDK and I think I see it under Square's java SDK. But as researched in github, their official reply is that I'm unable to use java SDK in android app.
So I'm trying to figure out has anyone done this before or face the same issue?
In-App Payments SDK is solely meant for generating a card nonce on your mobile application. All other API endpoints must be done on a server or service due to security reasons (you don't want to store your personal access token within your application). Once you have that nonce, you need a server or service running that your mobile application will talk to. Ie the most basic is passing the nonce to the Charge endpoint to charge a customer.
On that same note, we have another endpoint called CreateCustomerCard, which you can pass the nonce as well as customer_id to in order to save the card to this particular customer's profile. So, at the very least you'll need to create a customer in order to have their id.
For info around saving cards on file, see this post: Hot to generate card nonce for repeated transactions without making users to enter card details?

Building a shopify private or public app

I am trying to make a plan to update my client's shopify stores by building Shopify app or using external library. Basically, I want to provide my clients with some convenience by automating the inventory update, order process and extra stuff.
For now, I have only two scenarios.
Whenever my wholesale inventory changes, i want to update my client's shopify product list to be updated (quantity, price and product description) accordingly.
Whenever my client(shopify store owner) receives an order from his/her customer, i want the order information to be automatically transferred to my server.
If possible, I want my clients to be able to integrate with my application without any tech knowledge. I have looked into the Shopify app (public/private) and some external API(java), because I am a java developer.
I checked Shopify Java library which requires api key and password to be able to access shopify owner's store for product/order access, but I am not sure how user-friendly this approach is in terms of Shopify owner's side.
For Shopify public app, I am not familiar with it, so I am not sure how much I can do with it.
Could somebody provide some details about pros/cons about these approaches?
Thanks.
All you need to know is that with Shopify, you can connect to their shop using standard HTTPS. Even better, it's all GraphQL now. As for credentials, Shopify is fully modern and offers you two methods of getting credentials.
Your merchant client can create credentials with permissions right inside their Shopify Admin -> Apps. They give you the keys, you're in business
You get them (or you) to simply click install your App running at some HTTPS address, and you use oAuth to get the credentials.
Either way, makes no difference to the actual code you write to interact with their shop and deal with inventory, sales etc. You do not need to make your App public in the sense of App store, so you can use your partner dashboard to create an App and oAuth install, or like I said, use the private App way.

Can I control the list of chargeable connections in the IPP inside an Intuit App Center App?

I am developing an Intuit App Center app using the V3 SDK written in vb.net.
Is it possible to get/control the list of connected users that is listed in the Reports section of the Manage My Apps area in the Intuit Partner Platform? Specifically, the area where you view your connections and are able to disconnect users so you don't get charged for that connection.
I would like to be able to control that list from within my application for billing purposes. I have heard that it is possible to manipulate the list programmatically but I'm unsure how to do it.
This should definitely be do-able, but there's not a specific API for it.
There are really 3 components to tracking this information:
Have they EVER connected - you'll know this already because if they connected they will have gone through the OAuth process on your website and you'll have a token for them.
Are they connected NOW - you can test this by making an OAuth request to any of Intuit's services - if you get back a successful response, you know they are currently connected, vs. if you get back a 401 error you know the token is expired/no longer good.
Disconnecting them - you can choose to explicitly disconnect a user (and thus no longer get charged for their usage) by using the disconnect API call.
There is no billing API available.
You need to check it from the appcenter.
Ref - https://developer.intuit.com/docs/0025_quickbooksapi/0010_getting_started/0050_managing_your_app/connection_report
Thanks

How do I test a new app that has not been published against the shipping api?

I have been given access to the new shipping api, when creating an app in partner section and subsequent editing of it details I can set it as a shipping app.
I can then add a shipping rate provider in the test shop (same partner account) but can only see USPS, Canada post, Fedex etc..and can not see the app. I imagine this is because the test app has not been published. But I do not want to publish the test app, and a requirement to publish an app before it can be added as a shipping provider would sort of hinder developement and testing ;-)
I have tried visiting http://your-store.myshopify.com/admin/api/auth?api_key=YOUR_API_KEY
but I can't see how that will add my test app as a shipping rate provider in the shipping preferences of the test app.
In fact I gave up on using http://your-store.myshopify.com/admin/api/auth?api_key=YOUR_API_KEY and moved over to user Oauth2 (I couldn't seem to get legacy auth examples working.)
I can register the app via OAuth2 however the option for this shipping app does not appear in the "Carrier calculated shipping rates"
Now I am really stumped.
Make sure that the app you created has checked the “this is a shipping app” box.
Visit http://YOUR-STORE.myshopify.com/admin/api/auth?api_key=YOUR_API_KEY
Visit https://YOUR-STORE.myshopify.com/admin/shipping and the shipping service your app exposes should be available as a carrier-calculated shipping rate. (Hit that button at the top of the page if you haven’t added any yet.)
Ok Edwards answer is correct as far as registering an app is concerned.
However if the app provides the shipping api it will "NOT" appear in carrier-calculated shipping rates config for shipping.
After you succesfully register the app you then have to make a POST call to carrier_services.json. e.g. in python
response = connection.post("%s/carrier_services.json" % shopify_session.site,headers)
Once you do this the new shipping api will be called during the checkout process.
Also note at the moment if you make any changes to the shipping configuration in preferences you will need make another POST to carrier_services.json to re-enable the shipping api. It seems any changes to the shipping details currently unhooks the app from being called.
This is early days and no doubt things will change.