I want to make an app with payment api i haven't experience the payment gateway apis.
Should i use Apple pay or any other open source api.
if other api then which could be the best suited for the enterprise application.
Thanks in advance.
Apple Pay handles the payment experience part on iOS apps, meaning you would have to integrate it with a payment platform (that supports Apple Pay) to complete the checkout solution and make it work for processing payments.
I'd recommend you to check with either Braintree or Stripe, both are pretty developer friendly for integration.
Related
I'm currently using Next.js for my front-end framework. I've been considering on using another javascript framework for my back-end, however it occured that me that existing CMS solutions like BigCommerce and Shopify exists.
I'm aware they have their own API reserved for developers, but from what I can see these are API usually made to develop tools and themes for other users on the platform itself. Is it possible that I can somehow leverage the power of these ecommerce CMS on my Next.js website? I don't know how these work because I've always seen them as softwares for non tech-specialists to build e-commerce without having the need to code. To know that an API for software exists is quite extraordinary
There's a lot that goes into building an e-commerce website, mainly the things that I am looking for is inventory management and supply chain management. Building these on top of a fullstack e-commerce website would take me too much time and goes beyond the constraint of the project. Do these API let you leverage their technology? But most importantly, do you have to pay a subscription fee to use their API as well as other features such as inventory management?
I am particularly interested in BigCommerce, because the Next.js commerce starter kit comes with BigCommerce integration out of the box (I'm not sure why they chose BigCommerce, as opposed to other CMS such as Shopify). Answers directly referring to BigCommerce are greatly appreciated.
The benefits and drawbacks of using an eCommerce CMS API can be pretty subjective. I have a large amount of experience with BigCommerce, and I can clarify with you that the BigCommerce API is used for much more than just building tools or themes for other BigCommerce users. I mostly see it used for custom integrations and extending the platform functionality.
Combining the API with your own back-end services can really give you unlimited possibilities in terms of functionality with the platform, especially where the platform may fall short in its native functionality. For example, if you feel like the store-credit system is lackluster natively - guess what? There are plenty of APIs that give you the potential to make your own store credit system and integration that suits your needs better.
To answer these questions:
Do these API let you leverage their technology?
The BigCommerce API has quite a bit of freedom in terms of which technologies you get to leverage. Pretty much every aspect of the platform has an API that can be used for your own needs.
Do you have to pay a subscription fee to use their API as well as other features such as inventory management?
There isn't any sort of subscription fee to use the BigCommerce API, and inventory management comes natively in the platform, as well as an API to manage your product inventory. There is also a large community of developers that have built apps for the platform that offer more advanced inventory management as well.
Whether or not you want to use the native BigCommerce functionality instead of a NextJS headless storefront all depends on your personal preference and goals. Using the built-in BigCommerce storefront is more simplistic and requires less development experience (if any at all), whereas if you wanted a headless storefront with BigCommerce using NextJS, this would ultimately give you more control, but would also require more coding/development knowledge.
Since some time aqbanking supports paypal for hbci but I do not find any examples or documentation about that.
Does anyone can give me a legit example how to integrate paypal to download the current balance and also the last transactions like for any other bank supporting hbci?
If your version of AqBanking supports Paypal, it will appear in the list of protocols for a new user alongside HBCI, EBICS, OFX and offline. Many distributions, however, do not include support for Paypal.
Is there any way currently to do a parallel payment in paypal with the rest api? I am building a mobile application and can only use the rest api system however there is no documentation on how you can use parallel payments with REST.
You can do everything else so it seems to me like the developers got to that feature and just gave up :P.
This feature is a huge part of our website and if we cannot use it on the mobile app it will mean we have to redo how we handle transactions on the site so that both areas are consistent.
If this feature is not available since rest was supposed to be the refresh of all their API's to support newer tech is it coming? Does anyone know and if you do any information on a timeline would be helpful.
REST API does not support parallel payments at this time, it's in the product road map but not yet in the released APIs.
An alternative for your use case is to integrate the webview embedded Express Checkout flow into your APP, it provides the most identical experience to payers since the new UI was released.
I'm making a utility application for a photographer. He is going to (obviously) be taking pictures, but wants to charge people at an event for a handful of digital images emailed or shared on social media. In this situation i would have to use Paypal or Square SDKs and not in app purchasing because he is going to compose the transaction and not the customer buying the pictures. Sort of like a mini POS system. He can't pay himself with another's credentials - so it would have to be a 3rd party solution. right? Is this against Apple's guidelines?
Am I over thinking this?
If the intent is to support in-person / face to face (swipe) credit card or keyed in credit card payments, check out the PayPal Here SDKs for iOS and Android which are now available on the PayPal Developer site:
https://developer.paypal.com/webapps/developer/docs/integration/mobile/pph-sdk-overview/
There is also a version for Windows 8.1+ in Beta, available upon request. You can email DL-PayPal-Here-SDK#ebay.com for help with any of these.
We are about to develop new mobile application that requires the end user to fill his payment information, which will be redirected to a third party’s portal to pay for a certain services through the application ( using Web Services )
user send billing information using web services , Is this legal for apple ?
It's OK to integrate 3rd party credit card payment systems in your app (for example PayPal, Amazon payments, etc. or your own system) as long as you do not sell services, extensions, etc. to your app. As you say you're going to sell physical goods, it is OK for Apple. Amazon app does the same thing. Btw it is even explicitly prohibited to use in-app payments to sell physical goods.
EDIT: more answer to the detailed questions in the comment
IMHO (see disclaimer):
Shipping fees of physical goods and signup fees for your physical service are NOT services or extensions - in the sense that Apple uses it, it applies only to some additional features to your application, for example a new level in a game or a new map in a mapping app
to be legally store, transmit, process credit card information, you will have to be compliant to the Payment Card Industry Data Security Standard. Here Apple has nothing to do, but both Visa and Mastercard (and maybe also other card issuers) require that you implement these practices if you wish to process credit card data of their cards
this last requirement might be tricky so I really suggest you to look for some ready solution instead of implementing your own. See also the first answer to this question: Use In App Purchase For Real Goods
DISCLAIMER: I am not a legal authority or somebody from Apple so I can give you just hints but not a legal advice - will have to ask a lawyer for an "official" answer :)