> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/globepay.md). # GlobePay Configure GlobePay Alipay and WeChat Pay wallet payments with Hyperswitch. GlobePay brings Alipay and WeChat Pay wallet payments to Hyperswitch. Both routes support refunds and automatic capture, including sequential automatic capture. Mandate setup is not supported. ### Status and capabilities **Integration status:** sandbox **Category:** payment gateway **Webhook flows:** None declared in code | Payment method | Type | Mandates | Refunds | Capture methods | Countries | Currencies | | -------------- | ---------- | ------------- | --------- | ------------------------------- | --------- | ---------- | | wallet | Alipay | not supported | supported | automatic, sequential automatic | GBR | CNY, GBP | | wallet | WeChat Pay | not supported | supported | automatic, sequential automatic | GBR | CNY, GBP | ### Authentication Provide the **Partner Code** and **Credential Code** from [`globepay.connector_auth.BodyKey`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/connector_configs/toml/sandbox.toml#L3051-L3053); [`GlobepayAuthType::try_from()`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/globepay/transformers.rs#L139-L150) maps them. **Source verification key** is currently unused because webhooks are not implemented ([`globepay.connector_webhook_details`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/connector_configs/toml/sandbox.toml#L3054-L3055)). ### Before you start Create or sign in to your [GlobePay account](https://www.globepay.co/services/) and obtain the **Partner Code** and **Credential Code**. GlobePay appears in the control center list ([`connectorList`](https://github.com/juspay/hyperswitch-control-center/blob/ecca16a27cb6acb336569ea30714fa05d867c765/src/screens/Connectors/ConnectorUtils.res#L89-L205)). Then follow [Activate a connector on Hyperswitch](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md). ### Payment flow GlobePay is a QR flow. Send the QR wallet variants, `ali_pay_qr` or `we_chat_pay_qr`; the redirect variants of Alipay and WeChat Pay return a not-implemented error ([wallet handling](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/globepay/transformers.rs#L56-L95)). Authorize returns the QR image URL in `connector_metadata` as `image_data_url`, and the payment stays `requires_customer_action` until the customer scans it ([QR metadata](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/globepay/transformers.rs#L207-L231)). Only a payment sync moves it on: `PAYING` keeps it pending, `PAY_SUCCESS` marks it charged, and `CLOSED` or a failure marks it failed ([`GlobepayPaymentPsyncStatus`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/globepay/transformers.rs#L266-L281)). A refund sync maps `FINISHED` to success, `WAITING` and `SUCCESS` to pending, and `CHANGE` to failure ([`GlobepayRefundStatus`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/globepay/transformers.rs#L366-L382)). ### Webhooks GlobePay webhooks are not supported; use payment sync and refund sync for status. See [`IncomingWebhook for Globepay`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/globepay.rs#L548-L572), [`ConnectorIntegration`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/globepay.rs#L294-L365), and [`ConnectorIntegration`](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/globepay.rs#L474-L546). ### Source reference Authentication and webhook behavior on this page is tied to Hyperswitch `7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8`. See [GlobePay connector source](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/globepay.rs) and [GlobePay transformers](https://github.com/juspay/hyperswitch/blob/7a348f02a94edf7b2593e65ca6ffaf8d8f9ee6f8/crates/hyperswitch_connectors/src/connectors/globepay/transformers.rs). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/globepay.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.