Google Checkout Bi-weekly billing conflict

  • Profile Image
    Asked on February 18, 2013 at 10:21 PM

    There seems to be an issue with the Google Checkout payment integration, specifically with bi-weekly billing. I set up a bi-weekly payment option on a form using the Google Checkout payment integration feature. When I tested the functionality and selected the bi-weekly option, it became monthly billing on the google wallet payment page. I have attached a file with screenshots from the jotform and the payment page showing the conflict. Does this mean that Google Checkout simply does not support bi-weekly billing and automatically converts it to monthly? if so, why is the bi-weekly option given on the Jotform payment integration wizard for Google Checkout? I've noticed that with other payment gateways (e.g. Stripe) that don't support bi-weekly billing, only the options that are supported by the gateway are given as options in the payment integration wizard.

  • Profile Image
    Answered on February 19, 2013 at 01:16 AM

    Thank you for using Jotform. Currently Google does not support biweekly to U.S merchants. Please refer to the link below

    If you need further assistance, please let us know.

  • Profile Image
    Answered on March 05, 2013 at 12:39 AM

    That link refers to the payout schedule for merchants. The issue is with the recurring payment frequency for customers. When I establish the bi-weekly payment option on my form using Google Checkout payment integration, it becomes a monthly payment schedule on the checkout page when that option is selected and submitted. Google Checkout's documentation shows that they support bi weekly (SEMI_MONTHLY) billing: 

    Required. The period attribute specifies how frequently you will charge the customer for the subscription. Valid values for this attribute are DAILY, WEEKLY, SEMI_MONTHLY, MONTHLY, EVERY_TWO_MONTHS, QUARTERLY, and YEARLY.

  • Profile Image
    Answered on March 05, 2013 at 01:26 AM

    Thanks for a very detailed explanation. I have forwarded this to our development team so they can check it further. You will be updated on this thread once a solution is implemented. Thanks!

  • Profile Image
    Answered on March 05, 2013 at 02:38 PM


    This problem should now be fixed. Sorry for the inconvenience.