Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

虎皮椒更新了pc端支付扫码接口 #179

Closed
1 task done
kaine380 opened this issue Mar 28, 2024 · 4 comments
Closed
1 task done

虎皮椒更新了pc端支付扫码接口 #179

kaine380 opened this issue Mar 28, 2024 · 4 comments
Labels
feature New feature or request

Comments

@kaine380
Copy link

⚠️ 确认 issue 是否已存在 ⚠️

  • 我已经搜索了现有的问题,没有找到相关 issue。

功能描述 📝

使用接口返回的二维码可以直接扫码,不必跳转到网页
https://www.xunhupay.com/324.html

示例 🌈

No response

动机 🔦

No response

@kaine380 kaine380 added the feature New feature or request label Mar 28, 2024
@kaine380
Copy link
Author

//hupiPay 单独处理,使用微信二维码
if data.PayWay == "hupi" { // 虎皮椒支付
	params := payment.HuPiPayReq{
		Version:      "1.1",
		TradeOrderId: orderNo,
		TotalFee:     fmt.Sprintf("%f", order.Amount),
		Title:        order.Subject,
		NotifyURL:    h.App.Config.HuPiPayConfig.NotifyURL,
		WapName:      "ChatAI",
	}
	r, err := h.huPiPayService.Pay(params)
	if err != nil {
		resp.ERROR(c, "error with generating payment qrcode: ")
		return
	} else {
		resp.SUCCESS(c, gin.H{"order_no": order.OrderNo, "image": r.UrlQrcode})
		fmt.Println(r.UrlQrcode)
		return
	}
}
写在payjs单独处理下面

@yangjian102621
Copy link
Owner

这个是故意设计成这样的。统一的交互体验,而且扫码需要有反馈扫码成功,官方提供的二维码没有这功能。

@kaine380
Copy link
Author

kaine380 commented Apr 1, 2024

这个是故意设计成这样的。统一的交互体验,而且扫码需要有反馈扫码成功,官方提供的二维码没有这功能。

除了没有扫描成功的提示,其他还行,可以提示支付成功,我这边的运营商屏蔽了虎皮椒的域名,开wifi扫不了码,这样直接扫支付码成功率高一点

@yangjian102621
Copy link
Owner

这个是故意设计成这样的。统一的交互体验,而且扫码需要有反馈扫码成功,官方提供的二维码没有这功能。

除了没有扫描成功的提示,其他还行,可以提示支付成功,我这边的运营商屏蔽了虎皮椒的域名,开wifi扫不了码,这样直接扫支付码成功率高一点

你直接扫码也是需要打开虎皮椒的域名的,应该没法避免的。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants