As I know every time when user add the same card to ApplePay/GooglePay it’s create a new token. When I read payment data over nfc is it have any tag to identify user? It’ mean any constant data for any token which link to physical card? Thanks
There is Payment Account Reference for this purpose. There are some limitations of its availability and ability to link to original card, so it's really a complex topic that cannot be limited to card-terminal interface, but involve other systems as well.
I'd advise that you discuss this with payment schemes.
Related
I want to allow my users to pay food to my business users using Stripe Connect. I never used Stripe, but by reading the Stripe documentation, this seems feasible and relatively easy to implement.
According to this Google documentation page, the purchase or rental of physical goods via a given app is not subject to their fees.
Does this imply that I will not pay any fee to Google, even if I distribute my app via Google Play?
Given your use case, you should be able to use Stripe instead of Google Play's billing system and not be subject to Google extra fees. That being said, it would depend on how you implement your app. For example, if you were to sell tokens (that were only available in-app) that could be redeemed for food, that would probably still need to use Google's billing system. You should probably write in to Stripe Support (https://support.stripe.com/contact) to talk through what you want and be completely sure.
Help me please. How to integrate Apple Pay in Xamarin.Forms? The instruction that is on the Microsoft website does not provide a step-by-step algorithm for implementing this functionality.
Maybe there is a plugin that helps solve this problem? I tried to register at www.judopay.com, as indicated in the Microsoft manual, but no one answered my application.
There is no direct detail tutorial in Xamrarn , however Xamrin provide a Emporium sample and original document from Apple to explain that .
The sample app is comprised of several parts:
CatalogCollectionViewController - a collection view that displays a list of products (parsed from ProductsList.plist)
ProductTableViewController - a detail table view that summarizes a product, and allows the user to buy it using Apple Pay
ConfirmationViewController - a simple confirmation screen to be shown after a successful payment
Hope this sample will be helpful to create your first apple pay application .
In addition , the most important logic is Processing the Payment Token:
Once the user has authenticated to confirm purchase intent, you don’t need to handle their actual credit or debit card numbers. Instead, your app or website receives a payment object containing an encrypted payment token. This token encapsulates the information needed to complete a payment transaction, including the device-specific account number, the amount, and a unique, one-time-use cryptogram. The token can be decrypted by the merchant with the certificate private key or by the Payment Service Provider (PSP) on behalf of the merchant. Once decrypted, the token needs to be passed to the payment service provider for processing.
More info , you can refer to Apple doc here .
I'm working on a project that needs to be have the credit card payment integration, we want to use elavon.com API. One of the requirement states that we need to record the credit card information during order, manually approve/ reject each order & charge the card only when the order has been manually approved.
The question is can we do something like this with Elavon? & is it the right approach for this task, as I know there are many security risks with this.
I read about getting a token from the API and storing the token instead of storing the credit card information. Any direction/ guidance in this direction is highly appreciated.
I am going to use braintree with cutsomized UI which takes customer credit card information either scaning card or entering credit card information.
I am also going to provide user facility of adding and replacing of existing credit card.
Should I need go for PCI compliance in this case.
This seems like more of a design question. But when you are dealing with sensitive information like credit cards it is best to use whatever is at your disposal to maintain security. The app I made that utilized braintree's api has all of the fraud protection tools in place. If you implement PCI compliance make sure to read the section on PCI compliance
I work as a developer at Braintree. I recommend using Hosted Fields so that you have the flexibility to use a custom UI while maintaining the easiest level of PCI Compliance.
You can also see how to implement the functionality of creating users and adding/replacing payment methods in the Braintree Guides.
We are upgrading our SagePay protocol from v2.23 to 3.0 to support surcharge fees. In v3.0 transaction registration post there are CreateToken and StoreToken which was not in the earlier version. What is the reason for create and store tokens? I went through the document but couldn't find a clue.
The link provided in the above post links to advice by one of our Sage Pay Partners so take a look at it.
Token allows shoppers the option of storing their card details (as a token) to their account on the payment page during their first purchase instead of having to set it up manually afterwards. Single click purchases for repeat customers will become much simpler and quicker to set up.
To view the Token Guide go to here, scroll to the bottom of the screen and select the Download the Documents option within your preferred method of integration (server, server inframe, direct). Within the guide it explains creating and storing a token.
If this is a service you would like enabled on your Sage Pay account our New Business team are available 0900-1800 on 0845 111 4466. Prices for Token are available via here. If you have any other questions, our 24/7 Support team can assist to on 0845 111 4455.
Sage Pay Support.
I believe this is related to their token system, allowing you to store and send card details as a token.
If you don't use their token system you don't need to worry about it.
Sage Pay have destroyed their content recently so it's hard to find anything, here's a quick article on their token system - http://www.metakinetic.com/blog/2013/09/sage-pays-token-system-and-advancements-in-payment-gateways/