Urgent help! INCOMPLETE_SIGNUP, it's been lasting for a week!

[548...@qq.com]

HI there,

I've spent a couple of days trying to solve this thing out, but unfortunately I wasn't able to. What I've tried:

1. Filling in the billing information with a test credit card number. 

2. Create a test account, and fill in its billing information.

3. Create another MCC account and do the above again.

4. Change the test credit card number to my real one.

Nothing worked! now I have no idea how to proceed from here.

I'm quite sure that all information needed are entered correctly and I just got nothing changed except the INCOMPLETE_SIGNUP.

Dude, why are you making things so complicated? I've read most threads here about this, and all you had to say was about T&C not accepted, and nowhere you can see it and do it yourself.

Please, help me. This project is for customer and we should have gone much far away than just stuck here.

My MCC ID: 824-689-9971

Test account ID: 779-265-4485

Request and response are blow:

<?xml version="1.0" encoding="UTF-8"?>

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="https://adwords.google.com/api/adwords/cm/v201309">

  <SOAP-ENV:Header>

    <ns1:RequestHeader>

      <ns1:clientCustomerId>779-265-4485</ns1:clientCustomerId>

      <ns1:developerToken>xxxxxx</ns1:developerToken>

      <ns1:userAgent> (AwApi-PHP/4.6.1, Common-PHP/5.0.0, PHP/5.4.12)</ns1:userAgent>

    </ns1:RequestHeader>

  </SOAP-ENV:Header>

  <SOAP-ENV:Body>

    <ns1:get>

      <ns1:serviceSelector>

        <ns1:fields>Id</ns1:fields>

        <ns1:fields>Name</ns1:fields>

        <ns1:ordering>

          <ns1:field>Name</ns1:field>

          <ns1:sortOrder>ASCENDING</ns1:sortOrder>

        </ns1:ordering>

        <ns1:paging>

          <ns1:startIndex>0</ns1:startIndex>

          <ns1:numberResults>500</ns1:numberResults>

        </ns1:paging>

      </ns1:serviceSelector>

    </ns1:get>

  </SOAP-ENV:Body>

</SOAP-ENV:Envelope>

HTTP/1.1 500 Internal Server Error

Content-Type: text/xml; charset=UTF-8

Date: Fri, 18 Oct 2013 09:33:19 GMT

Expires: Fri, 18 Oct 2013 09:33:19 GMT

Cache-Control: private, max-age=0

X-Content-Type-Options: nosniff

X-Frame-Options: SAMEORIGIN

X-XSS-Protection: 1; mode=block

Server: GSE

Transfer-Encoding: chunked

<?xml version="1.0"?>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

  <soap:Header>

    <ResponseHeader xmlns="https://adwords.google.com/api/adwords/cm/v201309">

      <requestId>0004e9009fef17e80a42e50900007417</requestId>

      <serviceName>CampaignService</serviceName>

      <methodName>get</methodName>

      <operations>0</operations>

      <responseTime>91</responseTime>

    </ResponseHeader>

  </soap:Header>

  <soap:Body>

    <soap:Fault>

      <faultcode>soap:Server</faultcode>

      <faultstring>[QuotaCheckError.INCOMPLETE_SIGNUP @ ; trigger:'&lt;null&gt;']</faultstring>

      <detail>

        <ApiExceptionFault xmlns="https://adwords.google.com/api/adwords/cm/v201309">

          <message>[QuotaCheckError.INCOMPLETE_SIGNUP @ ; trigger:'&lt;null&gt;']</message>

          <ApplicationException.Type>ApiException</ApplicationException.Type>

          <errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="QuotaCheckError">

            <fieldPath/>

            <trigger>&lt;null&gt;</trigger>

            <errorString>QuotaCheckError.INCOMPLETE_SIGNUP</errorString>

            <ApiError.Type>QuotaCheckError</ApiError.Type>

            <reason>INCOMPLETE_SIGNUP</reason>

          </errors>

        </ApiExceptionFault>

      </detail>

    </soap:Fault>

  </soap:Body>

</soap:Envelope>

 

[David Torres (AdWords API Team)]

Hi,

I'm sorry you find the process to create test accounts complicated, recently we have made some change to it and you can now provision test accounts by yourself. Please read carefully this document https://developers.google.com/adwords/api/docs/test-accounts on the new process to create test accounts works.

I can tell you that your MCC 824-689-9971 is perfectly setup for use with test accounts, so you can use the developer token from this MCC. The problem is that your account 779-265-4485 is not a test account but rather a production account, therefore the error you are seeing. What you need to do is to follow the instructions outlined under the "Getting started" section in the guide. After you created your Test MCC account you can login in the frontend (you'll notice a red banner at the top stating is a test account) and from it create a regular child test account.

Don't hesitate to write back to the thread if you are still in doubt.

Best,

- David Torres - AdWords API Team

[b.ka...@mso-digital.de]

Same problem here, but i'm using a test account (red banner) with the pending developer token from the production account.

Setting billing information throws an error.

See https://groups.google.com/forum/#!topic/adwords-api/-K7DuDOAVEM