Firebase付款网关? [英] Firebase payment gateways?

查看:191
本文介绍了Firebase付款网关?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

目前,我正在评估Firebase是否适合我正在制作的应用。我发现的唯一潜在问题就是付款 - 现有的选项是什么?

解决方案

Firebase是一个实时数据存储,专注于快速,可扩展的解决方案,用于同时在数百至数百万客户端之间共享数据。它不在内部提供任何支付处理解决方案。



第三方服务,如 Stripe 将与Firebase轻松集成,像 Zapier 这样的工具可以帮助从Stripe在完成交易后返回Firebase。

一般来说,这个过程看起来像这样:

$ ol

  • 用户在您的网站上启动交易

  • 客户端代码将其发送到Stripe以输入他们的CC信息
  • 客户端代码获取代表

  • 服务器进程在事务被验证时通过分条通知

  • 服务器使用标记
  • 提交支付授权
  • 条带将事务收据发送到服务器进程或Zapier,该服务器进程或Zapier将存储在Firebase中

    这种方法的一个缺点是你没有存储任何信用卡或敏感数据,因此不符合PCI合规性和严格的银行/电子商务法规。

    I'm currently evaluating whether Firebase will be suitable for an app I am making. The only potential sticking point I have found is taking payments - what are the options currently available?

    解决方案

    Firebase is a real-time data store, focused on lightning-fast, scalable solutions for sharing data between hundreds to millions of clients simultaneously. It does not offer any payment processing solutions internally.

    A third party service like Stripe will integrate quite easily with Firebase, and tools like Zapier can help with pushing data from Stripe back into Firebase upon completion of transactions.

    Generally, the process looks something like this:

    1. User initiates transaction on your site
    2. Client code sends them to Stripe to enter their CC info
    3. Client code obtains a token representing the secure transaction
    4. A server process is notified by stripe when the transaction is validated
    5. The sever submits the payment authorization with the token
    6. Stripe sends a transaction receipt to the server process or Zapier, which would be stored back in Firebase

    An advantage of this approach is that your are not storing any credit card or sensitive data and therefore are not subject to PCI compliance and stringent bank/e-commerce regulations.

    这篇关于Firebase付款网关?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

  • 查看全文
    登录 关闭
    扫码关注1秒登录
    发送“验证码”获取 | 15天全站免登陆