eBay Resolution Case Management APIVersion 1.3.0

issuePartialRefund



Note: The Resolution Case Management API is no longer recommended. Instead, current users of the Resolution Case Management API should make plans to migrate to, and use the Return, Inquiry, and Case Management operations of the Post-Order API. New users interested is programmatically managing and resolving Item Not Received (INR) and Return/SNAD (Significantly Not as Described) cases, should also make plans to integrate with the Post-Order API. Since the Resolution Case Management API was first released, there have been many changes made to post-order flows, and Resolution Case Management API does not support all features and logic of the new flows. This API will be deprecated in the near future.

This call allows a seller to issue a partial refund to a buyer to help resolve an eBay Buyer Protection Significantly Not As Described case. The partial refund amount must have approval from the buyer before issuePartialRefund is used. The offerPartialRefund call can be used to propose a partial refund amount to the buyer. The issuePartialRefund call can only be successfully used if the payment method is PayPal.

Note: Partial refunds are no longer an option to settle an eBay Money Back Guarantee case. To issue a full refund to settle a Return case, use the POST /post-order/v2/casemanagement/{caseId}/issue_refund call of the Post-Order API. For Return requests that have not yet been escalated to a Return case, a partial refund is a possibility. A partial refund is offered to the buyer using the POST /post-order/v2/return/{returnId}/decide call of the Post-Order API, and if the partial refund amount is agreed to by the buyer, the seller would then use the POST /post-order/v2/return/{returnId}/issue_refund call of the Post-Order API to issue the partial refund.

Request Details

In the issuePartialRefund request, the seller must provide the case ID and the case type (always EBP_SNAD for this call) for the case upon which a partial refund will be issued. If the caseId.id and caseId.type values don't match, the request is processed (if caseId.id is valid) but a warning message is returned.

If not already known, the case ID for an eBay Buyer Protection case can be retrieved with a call to getUserCases. If you make this call, use the EBP_SNAD case type filter to restrict results to Significantly Not As Described cases. To get more detailed information on an eBay Buyer Protection case, you will want to call getEBPCaseDetail, using the same case ID in the request.

The amount of the refund and the currency used are required. The currency type is passed in as a currencyCode attribute of amount. In order for the call to be successful, the amount value must match the partial refund amount accepted by the buyer, and the currencyCode attribute value must match the currency type used in the original transaction.

There is an optional comments field that allows the seller to provide any relevant comments to the buyer.

Working with the Response

The response for issuePartialRefund includes the standard fields for a successful call, which are timestamp and version. If they occur, errors and/or warnings will be returned in an errorMessage container.



Input

See also Samples.

The box below lists all fields that could be included in the call request. To learn more about an individual field or its type, click its name in the box (or scroll down to find it in the table below the box).

<?xml version="1.0" encoding="utf-8"?>
<issuePartialRefundRequest xmlns="http://www.ebay.com/marketplace/resolution/v1/services">
  <!-- Call-specific Input Fields -->
  <amount> Money (decimal) </amount>
  <caseId> CaseIdType
    <id> string </id>
    <type> CaseType </type>
  </caseId>
  <comments> string </comments>
</issuePartialRefundRequest>
Argument Type Occurrence Meaning
amount Money (decimal) Required The seller enters the amount of the partial refund that is being offered to the buyer. This amount is in the currency used by the listing site. This amount must be identical to the amount offered through the offerPartialRefund call.
caseId CaseIdType Required This container is used to identify a specific eBay Buyer Protection case opened by a buyer in the eBay Resolution Center.
caseId.id string Required Unique identifier of the case. The caseId.id value is required in the request of every call except getVersion. The caseId.id value for a case is always returned in the caseSummary container of the getUserCases and getEBPCaseDetail calls.
Max length: 38.
caseId.type CaseType Required eBay case type. Case types include eBay Buyer Protection and PayPal Buyer Protection cases (opened through the Resolution Center), older disputes created through other sites, and Unpaid Item or Cancel Transaction disputes created through the Resolution Center or with the AddDispute call of the Trading API.

Applicable values:

EBP_SNAD
A Significantly Not As Described case opened by a buyer in the Resolution Center.

(Not all values in CaseType apply to this field.)
comments string Optional This optional field allows the seller to add a comment regarding the partial refund. For example, the seller might add a comment such as this in the field: "Here is your $10 partial refund that we both agreed upon." This comment is intended to be read by the buyer.
Max length: 1000.



Output

See also Samples.

The box below lists all fields that might be returned in the response. To learn more about an individual field or its type, click its name in the box (or scroll down to find it in the table below the box).

<?xml version="1.0" encoding="utf-8"?>
<issuePartialRefundResponse xmlns="http://www.ebay.com/marketplace/resolution/v1/services">
  <!-- (No call-specific Output fields) -->

  <!-- Standard Output Fields -->
  <ack> AckValue </ack>
  <errorMessage> ErrorMessage
    <error> ErrorData
      <category> ErrorCategory </category>
      <domain> string </domain>
      <errorId> long </errorId>
      <exceptionId> token </exceptionId>
      <message> string </message>
      <parameter name="string"> ErrorParameter (string) </parameter>
      <!-- ... more parameter values allowed here ... -->
      <severity> ErrorSeverity </severity>
      <subdomain> string </subdomain>
    </error>
    <!-- ... more error nodes allowed here ... -->
  </errorMessage>
  <timestamp> dateTime </timestamp>
  <version> string </version>
</issuePartialRefundResponse>
Return Value Type Occurrence Meaning
(No call-specific fields)
Standard Output Fields  
ack AckValue Always

Applicable values:

Failure
eBay encountered a fatal error during the processing of the request, causing the request to fail. When a serious application-level error occurs, the error is returned instead of the business data.
PartialFailure
eBay successfully processed the request, but one or more non-fatal errors occurred during the processing. Inspect the message details and resolve any problems before resubmitting the request.
Success
eBay successfully processed the request and the business data is returned in the response. Note that it is possible for a response to return Success, but still not contain the expected data in the result.
Warning
The request that triggered the error was processed successfully but with one or more warnings.

Code so that your app gracefully handles any future changes to this list.
errorMessage ErrorMessage Conditionally Information for an error or warning that occurred when eBay processed the request. This field is not returned if the ack value is Success.
errorMessage.error ErrorData Conditionally,
repeatable: [0..*]
Details about a single error.
errorMessage.error.category ErrorCategory Conditionally There are three categories of errors: request errors, application errors, and system errors.

Applicable values:

Application
An error occurred due to a problem with the request, with the most likely source being the application sending the request. For example, the request is missing a required data element or it contains an invalid field. The problem must be corrected before the request can be resent. Inspect the error message to find the cause of the problem. If the problem is due to an application error, modify the application and resend the request. If the error is due to invalid data, the source of the data must be corrected before you resend the resend request to eBay.
Request
An error occurred due to a problem with the request, with the most likely source being missing or invalid data in the request. The problem must be corrected before the request can be retried. Inspect the error message to find the cause of the problem. If the problem is a result of end-user data, alert the end-user to the problem and provide the means for them to correct the problem. Once the problem is resolved, resend the request to eBay.
System
Indicates that an error has occurred on the eBay system side. For example, a database or server could be down. Inspect the error message to find the cause of the problem. If the problem is on the eBay side, an application can retry the request a reasonable number of times (eBay recommends twice). If the error persists, contact Developer Technical Support. Once the problem has been resolved, the request may be resent in its original form.

Code so that your app gracefully handles any future changes to this list.
errorMessage.error.domain string Conditionally Name of the domain in which the error occurred.
errorMessage.error.errorId long Conditionally A unique code that identifies the particular error condition that occurred. Your application can use error codes as identifiers in your customized error-handling algorithms.
errorMessage.error.exceptionId token Conditionally Unique identifier for an exception associated with an error.
errorMessage.error.message string Conditionally A detailed description of the condition that caused the error.
errorMessage.error.parameter ErrorParameter (string) Conditionally,
repeatable: [0..*]
Various warning and error messages return one or more variables that contain contextual information about the error. This is often the field or value that triggered the error.
errorMessage.error.parameter
  [ attribute name ]
string Conditionally Various warning and error messages return one or more variables that contain contextual information about the error. This is often the field or value that triggered the error.
errorMessage.error.severity ErrorSeverity Conditionally Indicates whether the reported problem is fatal (an error) or is less- severe (a warning). Review the error message details for information on the cause.

If the request fails and the application is the source of the error (for example, a required element is missing), update the application before you retry the request. If the problem is due to incorrect user data, alert the end-user to the problem and provide the means for them to correct the data. Once the problem in the application or data is resolved, re-send the request to eBay.

If the source of the problem is on eBay's side, you can retry the request a reasonable number of times (eBay recommends you try the request twice). If the error persists, contact Developer Technical Support. Once the problem has been resolved, you can resend the request in its original form.

If a warning occurs, warning information is returned in addition to the business data. Normally, you do not need to resend the request (as the original request was successful). However, depending on the cause of the warning, you might need to contact the end user, or eBay, to effect a long term solution to the problem.

Applicable values:

Error
eBay encountered a fatal error during the processing of the request, causing the request to fail. When eBay encounters an error, it returns error data instead of the requested business data. Inspect the error details and resolve the problem before resubmitting the request.
Warning
The request was successfully processed, but eBay encountered a non-fatal error during the processing that could affect the data returned. For example, eBay might have changed the value of an input field. In this case, eBay returns a successful response, but it also returns a warning. For best results, requests should return without warnings. Inspect the warning details and resolve the problem before resubmitting the request.

Code so that your app gracefully handles any future changes to this list.
errorMessage.error.subdomain string Conditionally Name of the subdomain in which the error occurred.
timestamp dateTime Always This value represents the date and time when eBay processed the request. The time zone of this value is GMT and the format is the ISO 8601 date and time format (YYYY-MM-DDTHH:MM:SS.SSSZ). See Time Values in the eBay Web Services guide for information about this time format and converting to and from the GMT time zone.
version string Always The version of the response payload schema. Indicates the version of the schema that eBay used to process the request.



Samples

New to making API calls? Please see Making a Call.

Note: Some item IDs, user IDs, or other data in these samples might no longer be active on eBay. If necessary, you can substitute current eBay data in your requests.

Sample: Basic Call

This call is used by a seller to issue a partial refund to the buyer as a way to resolve a Significantly Not As Described case.

Description

This issuePartialRefund call sample issues a partial refund to the buyer as a way to resolve an open eBay Buyer Protection Significantly Not As Described case. The case ID, case type, and the amount of the partial refund are required input fields. The comments field is optional. This call can only be used if the payment method for the transaction is PayPal.

This call will fail if an invalid case ID is passed in. If the case ID does not match the case type that is passed in, a warning message will be returned in the request, but the call will succeed (if case ID is valid). This call will also fail if the buyer has not yet accepted the partial refund amount from the seller, or if the dollar amount or currency type passed into the amount field does not match what was offered and accepted by the buyer. The caller must be authenticated to make this call.

This call only returns the standard output fields to indicate a successful call.

Input

A US seller has offered a partial refund amount of $5.00 that was accepted by the buyer. The seller is now going to issue the buyer a $5.00 refund in US Dollars.

The case ID is 5********5. 'EBP_SNAD' is passed in as the caseId.type value. '5.0' is passed into the amount field, along with the currencyCode attribute value of 'USD'. The string, 'Here is your $5.00 partial refund.' is passed into the comments field, and this will appear as a comment to the buyer in the Resolution Center.

SOAP format. Also available is the XML equivalent.

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns="http://www.ebay.com/marketplace/resolution/v1/services">
   <soap:Header>
      <RequesterCredentials>
        <eBayAuthToken>A********3</eBayAuthToken>
      </RequesterCredentials>
   </soap:Header>
   <soap:Body>
      <issuePartialRefundRequest>
         <caseId>
            <id>5********5</id>
            <type>EBP_SNAD</type>
         </caseId>
         <amount currencyCode="USD">5.0</amount>
         <!--Optional:-->
         <comments>Here is your $5.00 partial refund.</comments>
      </issuePartialRefundRequest>
   </soap:Body>
</soap:Envelope>

Output

The seller's partial refund of $5.00 US Dollars is successful as indicated by the Success value in the ack field.

SOAP format. Also available is the XML equivalent.

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns="http://www.ebay.com/marketplace/resolution/v1/services">
   <soap:Header/>
   <soap:Body>
      <issuePartialRefundResponse>
         <ack>Success</ack>
         <version>1.3.0</version>
         <timestamp>2011-03-18T13:36:23.563Z</timestamp>
      </issuePartialRefundResponse>
   </soap:Body>
</soap:Envelope>

   Here is the same output in XML format. Note that this does not include standard values.

XML format. Also available is the SOAP equivalent.

<?xml version="1.0" encoding="utf-8"?>
<issuePartialRefundResponse xmlns="http://www.ebay.com/marketplace/resolution/v1/services">
   <ack>Success</ack>
   <version>1.3.0</version>
   <timestamp>2011-03-18T13:36:23.563Z</timestamp>
</issuePartialRefundResponse>



Change History

Change Date Description
1.3.0
2011-05-26
  • (added) New call