go-pay/gopay

微信、支付宝、抖音、通联支付、拉卡拉、PayPal、Apple 的Go版本SDK。【极简、易用的聚合支付SDK】

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 22 minutes ago
Added to GitGenius on September 11th, 2026
Created on January 8th, 2019
Open Issues & Pull Requests: 41 (+0)
GitHub issues: Enabled
Number of forks: 937
Total Stargazers: 5,752 (+0)
Total Subscribers: 48 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

GoPay is a Go SDK that aggregates payment processing for multiple Chinese and international payment platforms including WeChat Pay, Alipay, Douyin Pay, QQ Pay, Allinpay, Lakala, PayPal, and Apple Pay.

The tool solves the problem of integrating multiple disparate payment provider APIs by offering a unified interface across them. Rather than building separate integrations for each payment platform, developers use GoPay's consistent client patterns and method signatures to interact with different providers. The SDK handles the protocol-specific details of each platform, including request signing, response parsing, and webhook verification.

Developers should choose this tool if they are building applications that need to accept payments from multiple Chinese payment platforms or international providers. It suits projects serving the Chinese market particularly well, given its comprehensive support for local payment methods like Alipay, WeChat Pay, and Douyin Pay. The tool provides separate documentation and client implementations for each payment method, with version-specific support where platforms have released updated APIs—for example, both V2 and V3 implementations for WeChat Pay and Alipay. Test files and example code are included for each supported payment provider to guide integration.

The project maintains a substantial base of adopters who report issues from real-world usage rather than the core team driving the issue agenda. Maintainers typically respond to new issues and pull requests within a few days. Development work is dominated by enhancement requests, indicating active evolution of the SDK's capabilities.