{ "$schema": "http://json-schema.org/draft-07/schema#", "$id": "https://raw.githubusercontent.com/api-evangelist/verifone/refs/heads/main/json-schema/checkout-api-googlepaycardconfigrequest.json", "title": "GooglePayCardConfigRequest", "description": "GooglePayCardConfigRequest from Checkout API", "required": [ "payment_contract_id", "sca_compliance_level", "threed_secure" ], "type": "object", "properties": { "sca_compliance_level": { "type": "string", "description": "Strong Customer Authentication (SCA) compliance level, possible values
\n * NONE: No SCA required.
\n * WALLET: based on the assurance details, if those are false, Google Pay will indicate the PSP to trigger 3DS which in this case will be required. \n Details [here](https://developers.google.com/pay/api/web/reference/response-objects#assurance-details-specifications)
\n * FORCE_3DS: SCA will be triggered. Regarding the liability shift, please check\n [this page](https://developers.googleblog.com/en/google-pay-enabling-liability-shift-for-eligible-visa-device-token-transactions-globally/)", "enum": [ "NONE", "WALLET", "FORCE_3DS" ] }, "threed_secure": { "$ref": "#/components/schemas/ThreeDSData" }, "authorization_type": { "type": "string", "description": "Default: \"FINAL_AUTH\"
Other Possible Values: \"PRE_AUTH\"
Text: PRE_AUTH is used when a merchant wants to ensure shopper's funds availability at a later time.
Attention: If you are using PRE_AUTH function make sure capture_now is set as FALSE. Otherwise the PRE_AUTH will not work.
", "default": "FINAL_AUTH" }, "shopper_interaction": { "$ref": "#/components/schemas/shopper_interaction" }, "payment_contract_id": { "type": "string", "description": "This parameter can be found in the portal on the Payment Provider Contract attached to your organization or given to you by a Verifone employee. It is used to retrieve MID and other merchant configurations necessary for a card payment." }, "token_preference": { "$ref": "#/x-alt-definitions/token_preference" } } }