Accepting payments in Xamarin Forms?

Question

question

Stesvis-5434 asked · Mar 12 at 01:17 AM

Accepting payments in Xamarin Forms?

Hello,

I got to the point where i need to implement payments in my Xamarin Forms app.
The purpose of these payments will be to unlock certain advanced features.

Since I've never done this before, I am wondering:

First of all, should I handle this in the app, or use the backend as middleware?
If you do it in the app, what gateway is better to use, and especially, what implementation is more straight forward in a xamarin forms app?
If you do it in the backend, what would you suggest? Keep in mind it's a .net core 5 backend

Thanks for any advice.

dotnet-xamarinforms dotnet-standard dotnet-aspnetcore-mvc

· 1

10 |1000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DuaneArnold-0443 · Mar 12 at 06:17 AM

You don't give any basic business requirements so it's kind of hard to help you.

0 ·

Answer 1 · 2021-03-12T09:13:15.6Z

miwan2-msft answered · Mar 12 at 09:13 AM

Hi, @Stesvis-5434

The customer chooses the product or service they want to purchase and proceeds to the payment page. Most payment gateways offer you different options for your payment page.

Hosted payment page
A hosted payment page is an out-of-the-box payment page where customers are redirected when they are ready to checkout. The payment gateway securely receives the transaction data before it passes it to the acquirer. A hosted payment page reduces the PCI burden for online merchants if you don’t collect and/ or store the cardholder data on your server.

Server-to-server integration
A server to server integration is also known as a direct integration as it enables communication between two servers; the merchant’s server with the payment gateway’s server. By requesting the card details on the payment page, a direct transaction can be initiated. Customers can finalise a card payment without being redirected to the payment page of the payment gateway, resulting in faster checkout, more consistent user experience and more control over the look and feel of the payment page from the merchant’s perspective. A server-to-server integration is suitable if you collect and/ or store the payment data before sending them to the payment gateway for processing.

Client-side encryption
Client-side encryption, also known as encryption-at-source refers to encrypting sensitive on the client-side device before sending it to the merchant’s server. This enables the merchant to simplify your PCI compliance requirements. In a nutshell, it enables you to accept payments on your website while encrypting card data in your browser, using the payment gateway’s encryption library.

You could choose one mdoe for your business needs.

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Best Regards,
Michael Wang

·

10 |1000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

question