Plexy
Pay API
Gate APIDashboard
Pay API
Gate APIDashboard
  1. Payment Methods
  • Overview
  • Authorization
  • Webhooks
  • API Errors
  • Test Scenarios
  • Ecommerce Plugins
  • API
    • Payments
      • Overview
      • Payment Links
        • Create Payment Link
        • List Payment Links
        • Retrieve Payment Link by Order Reference
        • Cancel Payment Link
        • Retrieve Payment Link
        • Update Payment Link Expiration
        • Retrieve Payment Links Statistics
      • Reccurent Payments
        • Create Merchant-Initiated Payment
      • Direct Payments
        • Get Keys
        • Create Host-to-Host Payment
      • Transaction Management
        • Find Transaction's History by ID
        • Find Transaction by Payment Link ID
        • Find Transaction by ID
        • Find Transaction by Order reference
      • Payment Management
        • Cancel Payment
        • Capture Payment
        • Process Refund
      • Split Requests
        • Create
        • List
        • Update
        • Get By Id
        • Delete
      • Settlement Payment Order
        • Create
        • Get by id
        • List
    • Payouts
      • Retrieve Payout Transactions
      • Process Payout
      • Save Card for Payouts
    • Customers
      • Get Customer's Card Tokens
      • List Customers
      • Create Customer
      • Get Customer by ID
      • Get Customer's Transactions
    • Merchants
      • Payment Beneficiary
        • Create
        • Update
        • Gey By Id
        • List
        • Transfer from beneficiary balance to merchant balance
        • Create manual settlement for beneficiary
      • Retrieve Merchant's Details
    • Wallet
      • Authorize
      • Сapture
      • Refund
      • Cancel
    • Payment Methods
      • Google Pay™ Integration
  • Client SDK
    • Server flow
      • Session server flow
    • Web
      • Web Drop-in
      • Web iFrame
    • Flutter
      • Flutter Drop-in
  • Schemas
    • Schemas
      • response.TransactionList
      • entity.SplitRequest
      • entity.PaymentBeneficiary
      • request.CreatePaymentBeneficiary
      • entity.SettlementPaymentOrder
      • entity.PayoutRequest
      • entity.PayoutRequestRowData
      • entity.UserProfile Copy
      • entity.Store
      • request.AssignStoreToUser
      • request.RemoveStoreFromUser
      • entity.AccountExternalSystem
      • response.AssignStoreToUser
      • request.CreateStore
      • response.Store
      • response.UserList
      • request.WalletAuthorizeRequest
      • entity.ShortWalletTransaction
      • response.WalletAuthorizeResponse
      • request.WalletCapture
      • response.RemoveStoreFromUser
      • command.HandleThreeDResult
      • domain.Report
      • entity.CardSaveSessionCustomer
      • entity.Permission
      • entity.UserProfile
      • entity.UserRole
      • errors.Message
      • errors.Source
      • errors.Type
      • git_plexypay_com_ecom_back_api_internal_domain_view.Page-domain_Report
      • git_plexypay_com_ecom_back_api_internal_domain_view.Page-entity_UserProfile
      • git_plexypay_com_ecom_back_api_internal_platform_errors.Code
      • models.CSVApiRequest
      • models.CreateBussinessDetails
      • models.KeyResponse
      • models.OnboardingRequest
      • models.Transaction
      • paymentcore.Address
      • paymentcore.CustomerDetails
      • request.AuthorizePayment
      • request.BrowserDetails
      • request.CardData
      • request.ChangeUserRole
      • request.ContinueThreeDS
      • request.CreateCardSaveSession
      • request.CreateInviteSession
      • request.CreatePaymentLink
      • request.CreatePaymentLinkMetadata
      • request.HandlePayout
      • request.MerchantInitiatedPayment
      • request.PasswordRequest
      • request.Recurring
      • request.RefundPayment
      • request.SaveCard
      • request.SaveOneCustomer
      • request.TwoStepAuthorizePayment
      • request.UpdateMerchantSettingsRequest
      • request.UpdatePaymentLink
      • response.AcquirerResponseThreeDSecure
      • response.AuthorizeAndCapturePayment
      • response.AuthorizePayment
      • response.CancelPaymentResponse
      • response.CapturePaymentResponse
      • response.ContinueThreeDS
      • response.Currency
      • response.Customer
      • response.CustomerTransaction
      • response.CustomerTransactions
      • response.Customers
      • response.Error
      • response.Merchant
      • response.MerchantInitiatedPayment
      • response.MerchantSettings
      • response.PaymentLink
      • response.PaymentLinkInfo
      • response.PaymentLinkMetadata
      • response.PaymentLinksInfo
      • response.PaymentLinksStatistics
      • response.PaymentLinksStatisticsItem
      • response.Payout
      • response.Permission
      • response.RefundPaymentResponse
      • response.Report
      • response.SavedCard
      • response.Session
      • response.Settlement
      • response.SettlementTransaction
      • response.Store
      • response.Stores
      • response.Transaction
      • response.TransactionDetails
      • response.TransactionEvents
      • response.TransactionHistoryEvent
      • response.TransactionHistoryEventData
      • response.TransactionResponse
      • response.TransactionWebhookDetails
      • response.Transactions
      • response.UpdateMerchantSettingsResponse
      • response.UserProfile
      • value.PaymentMethod
    • receipt
    • Error
    • DecimalAmount
    • ProductType
    • ProductCategory
    • Product
    • Order
    • AgentBalance
    • AgentDeposit
    • TopupRequest
    • CreateOrderRequest
  1. Payment Methods

Google Pay™ Integration

Overview#

Plexy supports Google Pay™ as a payment method across available integration approaches, allowing merchants to accept wallet-based payments with a fast, secure, and user-friendly checkout experience.
INFO
If you use Plexy SDKs for Google Pay, merchants must still complete Google's required onboarding, policy acceptance, and production registration steps before Google Pay can be enabled.
Google Pay Supported
Accept Google Pay payments via Plexy where supported by your chosen integration method.
Works with Multiple Integrations
Use Google Pay with Hosted Checkout or SDK integrations (and other supported flows depending on your setup).

Supported Payment Methods#

Google Pay is available under Digital Wallets:
Digital Wallets
Apple Pay
Google Pay

Integration Options for Google Pay#

Hosted Checkout
SDK Integration
Host-to-Host (H2H)

Hosted Checkout (Google Pay)#

With Hosted Checkout, Plexy hosts the payment page on a secure domain and can present Google Pay as an available payment option.
Key points:
Fastest way to enable Google Pay with minimal development
Optionally embed via iFrame
Plexy handles payment form rendering and sensitive payment processing scope
Google Pay Requirements for Hosted Checkout

3D Secure (3DS) for Google Pay PAN_ONLY Credentials#

What is 3D Secure (3DS) in this context?#

3D Secure (3DS) is an additional cardholder authentication step that may be required for certain card transactions to reduce fraud and meet regulatory or issuer requirements.
For Google Pay transactions, the need to apply 3DS may depend on the credential/authentication method used, including PAN_ONLY flows.

How to enable 3DS for PAN_ONLY (Plexy)#

3DS for Google Pay PAN_ONLY is enabled via store-level configuration in Plexy.
INFO
✅ Important: 3DS trigger conditions are enabled manually for each store separately.
They are configured through your integration manager (not via a public API parameter).
1
1) Identify the store(s)
Determine the specific store (merchant profile) where you want 3DS to apply for Google Pay PAN_ONLY transactions.
2
2) Request 3DS enablement
Contact your integration manager and request:
Enable 3DS for Google Pay PAN_ONLY
Specify the store identifier(s)
3
3) Configure 3DS trigger conditions
Your integration manager will configure the exact 3DS trigger conditions per store (e.g., always-on or conditional rules).
4
4) Test in Sandbox
After configuration, verify the behavior in Sandbox (frictionless and challenge scenarios if applicable to your setup).
5
5) Go Live
Once verified, the same store-level configuration can be applied/confirmed for Production.
3DS Trigger Conditions (Store-Level, Manual Setup)
3DS triggering rules are configured per store and can be adjusted by your integration manager.
Typical configuration approaches include (examples):
Always require 3DS for Google Pay PAN_ONLY transactions
Require 3DS only above a certain amount
Require 3DS based on risk/fraud signals
Require 3DS based on country/region/card criteria (where applicable)
To change these rules, contact your integration manager and specify the desired behavior per store.

Need Help?#

Developer Support
Contact our technical team at developers@plexy.money for Google Pay integration assistance.
Store-Level 3DS Configuration
For enabling and tuning 3DS trigger conditions per store, contact your integration manager.
Modified at 2026-03-12 13:05:20
Previous
Cancel
Next
Client SDK
Built with