PaymentConfig

interface PaymentConfig { cardInputConfig?: CardInputConfig; spreedly?: CardInputConfig; expressCheckout?: { enabled: boolean; methods: { paypal?: boolean; apple_pay?: boolean; google_pay?: boolean; link?: boolean; applePay?: boolean; googlePay?: boolean }; methodOrder?: ('apple_pay' | 'paypal' | 'google_pay' | 'link')[]; requireValidation?: boolean; requiredFields?: string[] }; }

Source: global.ts:1703

Payment setup for checkout — the card-input configuration plus which express methods (PayPal, Apple Pay, Google Pay) are enabled and how they behave.


Properties

cardInputConfig: CardInputConfig

spreedly: CardInputConfig

expressCheckout: { enabled: boolean; methods: { paypal?: boolean; apple_pay?: boolean; google_pay?: boolean; link?: boolean; applePay?: boolean; googlePay?: boolean }; methodOrder?: ('apple_pay' | 'paypal' | 'google_pay' | 'link')[]; requireValidation?: boolean; requiredFields?: string[] }

Properties

  • enabled (boolean)
  • methods ({ paypal?: boolean; apple_pay?: boolean; google_pay?: boolean; link?: boolean; applePay?: boolean; googlePay?: boolean }) — Which express buttons to offer, when the campaign does not say.Write the method names with underscores (apple_pay, google_pay), the same as methodOrder beside them and as every other place the SDK names a payment method. applePay/googlePay are the older camelCase spellings and still work; a method turned on under either key is turned on.
  • methodOrder (("apple_pay" | "paypal" | "google_pay" | "link")[], optional)
  • requireValidation (boolean, optional)
  • requiredFields (string[], optional)