Skip to main content
Published: June 19 2015, 9:41:00 AMUpdated: November 28 2020, 9:50:52 PM

Q. We got 'Required input field(s) "chargeType"/"immediatePayment" for this operation are missing or invalid' error in addUsage response. Are we doing something wrong?

A. One possible cause of the error is that the user specified in the addUsage request is in the Suspended status. Moving the user to Active status will fix the problem.


Q. Why addUsage returns "subscription is not billable"  error in Sandbox?

A. addUsage and other billing related API calls are not supported in Sandbox environment since the billing system is not implemented in Sandbox.   You will need to test the functionality in Production.


Q. addUsage API returns 'The value <planID> for Input field planId is invalid' for the request as below.  The planId specified is a valid planId for my Open eBay Apps application. What is the problem?

<?xml version="1.0" encoding="utf-8"?>
<addUsageRequest xmlns="">
    <chargeAmount currencyId="USD">14.85</chargeAmount>
    <memo>\Module: $4.95<memo>

A. When make addUsage call, the planId and subscriptionId  specified in the request must be associated with the subscriber to your application as shown in User Management tool as below:Image

 Take this subscriber as an example, if you specify any value other than 5000000151 for <planId> tag, addUsage will  return '.. planId is invalid' error . 

   If your subscriber intends to use another billing plan, the user needs to first unsubscribe from the current plan and re-subscribe to your application by selecting the new plan of interest.  After that, you can make addUsage request using that new planId for the subscriber.


Q.  Why my addUsage call failed with the 'Transaction failure. Reason : billing declined' error as below, what is the problem?

 <?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope xmlns:soapenv="">
    <addUsageResponse xmlns="">
          <message>Transaction failure. Reason : billing declined, 205.</message>

A.  The error  message may be caused by one of the following:

  •    The subscriber specified in your addUsage canceled their preapproval agreement on PayPal
  •    externalChargeId, the transaction reference number, being passed in the addUsage request  is not unique

 To resolve the issue,  you need to

  1. reach out to your subscriber to find out whether they want to continue using the app.  If so then they need to sign a new preapproval agreement.

 2. Do not re-use externalChargeId. Once the subscriber has signed a new preapproval agreement,  generate an unique identifier for externalChargeId tag and send it to eBay with addUsage call.


How well did this answer your question?
Answers others found helpful