CC 存储、授权和捕获以及 PHP 的支付服务提供商

发布于 2025-01-18 15:54:04 字数 796 浏览 3 评论 0原文

我已经与许多不同的付款提供商进行了讨论,我已经厌倦了无尽的会议和讨论,最终,支持或他们的销售部门隐藏了他们的系统中的缺陷 /确认了其中一个下面的功能实际上是不可能的;而且,您必须寻找另一个提供商,将整个提供者与新提供商进行重新编程。

所以我想在这里询问。这里有人知道与PHP + MariadB后端兼容的任何付款服务提供商,以及具有以下所有功能的移动应用程序(通过REST API调用):

  • Secure。

  • 通过自定义表格提交给客户的信用卡;理想情况下,通过JS将数据发送到付款服务提供商,从它们的代币中获得数据,并将其存储在您的数据库中。这样,您自己的服务器不必符合PCI。

  • 每次客户X在您的后端进行身份验证请求后,每次单击网站上的特定按钮,请使用令牌来触发后端内的付款(带有安全的公共密钥身份验证等)

  • 每笔付款的客户X意识到必须首先获得授权(= validate card +验证客户有资金, +在卡上冻结),并在客户x收到预订服务后被捕获。

  • 授权和捕获机制必须通过获得的付款来为每笔付款工作。

  • 必须可能退款。

  • 必须为个人提供支付的服务提供商的KYC程序,不仅是公司(相信与否,有些提供商都只为款项提供公司资料的可能性。)

  • 接收支出的服务 即低货币开关费用。

  • 必须有可能的付款(例如市场 - 风格,向公司服务费用,公司付费,将佣金和转发为服务提供商)

I've already been in discussion with many many different payment providers and I'm getting tired of endless meetings and discussions, which in the end end up that the support or their sales department was hiding a flaw in their system / confirmed one of the features below that is actually not possible; and you have to look for another provider, reprogram the entire integration with a new provider, etc.

So I wanted to ask here; does anyone here know ANY payment service provider which is compatible with a PHP + MariaDB backend, and with mobile apps as well (via Rest API calls) that have all of the following features:

  • Secure.

  • Register a Credit Card for a customer via a custom form submission; ideally send data to payment service provider via js, receive an according token from them, and store that token within your DB. Like this, your own server does not have to be PCI compliant.

  • Every time a customer X clicks a specific button on your website, after authenticating the request on your backend, use your token to trigger an according payment within your backend (with secured public key authentication, etc.)

  • Every single payment the customer X realizes has to be only authorized first ( = validate card + verify that clients has the funds, + freeze them on the card), and captured after the customer X received the booked service, days later.

  • The authorize and capture mechanisms must work for every single payment with the obtained payment.

  • refunds of captured transactions must be possible.

  • The KYC procedure of service providers who receive payouts has to be possible for individuals, not only for companies (believe it or not, some providers only provide company profile possibilities for payouts..)

  • The Service provider must ideally be internationally active, i.e. with low currency switch fees.

  • Split Payments must be possible (e.g. marketplace - style, customer pays fee for service to company, company takes off commission and forwards rest to service provider)

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

旧人哭 2025-01-25 15:54:04

不确定 PHP + Maria DB 与您的查询有何关系。
您正在调用 RESTfull API,可以使用您想要的任何技术来调用它。

您的大多数要求都非常简单,许多提供商都可以满足您的要求。

你的问题中最具挑战性的部分更多的是国际市场部分。这主要取决于您提到的 KYC,并且很大程度上取决于商家所在的国家/地区以及您销售的商品类型。

市场卖家的 KYC、卖家的付款方式等受到严格监管,并且在多国模式下可能会很复杂。
在您的搜索中,我将深入探讨这个主题。

Not sure how the PHP + Maria DB has anything to do with your inquiry.
You are calling a RESTfull API, call it with any technology you want.

Most of Your requirements are pretty straightforward and can be answered by many providers.

The challenging part on your question is more on the international market place part. Which mostly depends on the KYC you mentioned, and highly depends on the country the merchant is in and type of goods you sell.

KYC for market place sellers, payout methods to sellers and so forth are heavily regulated and might be complex in multi country mode.
In your search I would explore this topic in depth.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文