Billing Agreements

PayPal has a system called BILLING AGREEMENTS which permits a merchant to withdraw moneys from your accounts without your authorization and without your knowledge. I understand that once you have made a payment to a merchant, he has the capability to get an authorization to withdraw funds without your consent, and you don't have to explicitly agree to this arrangement or even be aware of it. I don't know how the merchant manages this, but incredibly he does.
I am truly astonished that a solid organization such as PayPal is willing to be a party to such devious practices. I cannot believe PayPal aren't aware of the use that criminals make of Billing Agreements. PayPal are in fact complicit in the criminal activity of extortionists based in Africa, Russia and elsewhere. Paypal may not be criminals themselves, but they are criminal facilitators.

You will require two service contract document types. The first (say contract type SC) which uses milestone billing and the other (say ZC) which uses periodic billing.
The second one should be generated as a follow up action of the first at the end of the first year.
Ensure that the milestone billing allows you to bill 25% in the first installment. You can ofcourse block this one. The second one should allow you to bill 75%. This will not be blocked.
If the customer does not terminate the contract during the first quarter you bill the customer for the second billing item.
Once this contract has ended you can create another contract which will use the periodic billing which is simple quarterly billing which is what I think u require.
Next, the item category is an area you might have to think on. You may be able to create the same contract type if u can create the same material with a different item category so that in the same document type u can create first an item with milestone billing and the second with periodic.
Most probably this will meet your requirement. Please vet this with the FI/CO guys to check how it reflects their G/L accounts.
Let me know if u need any more tips.
thanx

Similar Messages

*HELP* Paypal and iTunes problems! Billing agreement does not work!

Hello
I hope someone here can help me as this is driving me insane
I want to use PP for iTunes and have set up numerous billing agreements through PP, but iTunes does not seem to recognize them. I go through the whole thing of signing into my account repeatedly and it will send me to PP where I over and over set up the agreement, but when it is supposed to send me back to iTunes it just sends me to a page on PP where it states that my session has timed out.
I chatted live with someone from iTunes yesterday who suggested as I use Mozilla firefox that I should use IE instead when doing this. SO I took everything off and started over again and nada/___sbsstatic___/migration-images/migration-img-not-avail.png
I also have a firewall on my pc through AVG and was wondering if this had something to do with it.
I cannot find the live chat section again to save my life/___sbsstatic___/migration-images/migration-img-not-avail.png
Please please I hope someone can help/___sbsstatic___/migration-images/migration-img-not-avail.png I have wasted enough time trying to figure this ridiculous thing out/___sbsstatic___/migration-images/migration-img-not-avail.png
Thanks for reading and for any assistance you may provide
Have a great day/___sbsstatic___/migration-images/migration-img-not-avail.png

Try Andrei Cerbu's post here
I had the same problem last night, and this just worked for me.

Billing Agreement ID

Can anyone advise where I can find my Billing Agreement ID? I need it to activate my new website account at Fatcow.Thanks, Gunid

Well, turns out it wasn't the popup blocker, but it was trying to relaunch the iTunes store from out of my browser window. I have Firefox set to not allow that kinda shenanigans, so of course it wasn't working. Thanks for the heads-up. It's awful when the answer is right in front of your nose and you can't even see it.
resolved

Project Billing - Agreement (Advance required)

Hi Folks,
Did anyone use the "Advance Required" (receipt to be applied) feature on the agreement form?
I could successfully apply the receipt and find the project. But, per the window help, after generating draft invoice, the advance on the funding inquiry screen should be decreased which is not happening for me.
Did anyone face similar kind of issue?

Well, this is something new with R12. So most of us Oracle customers don't have any experience with this new feature, so you are like a pioneer, blazing a trail into the great unknown. Let me ask this question - have you interfaced the invoice to Receivables yet? The impression I get is that the Autoinvoice process in Oracle Receivables will reduce the balance on the advance. The documentation does seem unclear on when exactly you will see the advance balance on the funding summary reduced. Since this is a new feature, you do have to consider the possibiity that you have run across an Oracle bug (someone has to be the first one to find a bug, after all). So my thought is that you should open up a service request with Oracle Support on this item. By working with support, you have the ability to have them view your setups and your real live data, which we on this forum do not have the ability to see. It could be possible that you have a setup issue, though I think it may be more likely that you either have not completed the process to the right point, or that you miight have run across a bug.
John Dickey

Can't buy song due to billing error

My credit card was recently renewed and could not purchase songs. Routed to Billing History and eventually to renewing my "Billing Agreement" between my cc company and itunes, which I did after updating the cc information (of course), prompted with two messages about there being a problem. Tried to purchase a song with same symptoms.
Updated cc informtion on cc company site, updated Billing Agreement info with itunes on the same site. Opened itunes, tried to buys song again. Receive same symptoms.
Anybody know what to try next?
Running on WinXP.
Thanks
C

Try making sure everything in your billing address is correct. You can check this info via the follow website:
https://myinfo.apple.com/

Project Billing Question

Hi All,
I have couple of Project billing questions. Hope you can help
1)A wrong customer was attached to project billing agreement, funding and base line also completed for the customer.
Now we realized that its wrong customer and want to change it to correct customer.
What are the options we have here?
Can we delete or end date the billing agreement?
will the funding be release from the wrong customner after deleting or end dating the billing agreement?
2) Wrong customer attached to a project..agreements,funding,baselining are NOT done.
How can we delete this customer and add the correct customer?
The option to change the customer is grayed out.
Appreciate if you can help.
Thanks

Hi
On your first question you said the agreement was created for wrong customer. Since you already baselined the funding, I assume you have that customer linked to the project.
You can go the Agreement form and enter a negative funding line allocated to the same project. The total allocated amount will be zero. The agreement is now not allocated and free to be allocated to another project. If it is a wrong agreement you may update the agreement amount to zero. Now create a new agreement for the right customer.
The open issue is with the project. You have a wrong customer associated with that project. However, system will not allow you to remove the customer - project record. Solution depends on the way the project was setup. Did you enable customer at top task? if so, end date the top task and create an alternative top task with the right customer.
If the project has been set with a single customer you better close the project and start a new one.
However, if you need an alternative solution, I can suggest a custom method. Go to Help > ..> Examine and change the existing customer of the project to zero contribution.
Now you will be able to add the right customer to the project and have 100% contribution on it.
Dina

Review my billing information everytime I sign in

Created an Apple ID, log into the Apple website just fine. Try logging into the iTunes store, and I'll get an iTunes pop up that says, "This Apple ID has not yet been used with the iTunes Store. Please review your account information." Well, I've reviewed my account information maybe five times now. It's asking me to review my billing information. After I complete the form, it tells me, "You have successfully created a Billing Agreement." I'll try and log into the iTunes Store and it'll tell me again, "Please review your account information."

It's happening to me too... I go through the process and use PayPal. I sign-in to Paypal and it says that the pre-pay agreement has been approved. I click on return to iTunes and it takes me to an itmss file that I need to download.. It's like nothing ever happens... Any ideas?

Appstore - Payment Information Review - Billing ID Failure

Unsuccessful loop with Paypal and Appstore
Everytime I try using Paypal.com to send Appstore a "Billing ID", it tells me there was a problem. Appstore suggests using a different browser, but I have tried using both Safari and Google Chrome. Appstore is not able to successfully communicate with either.
After logging into Paypal.com manually, I found that Appstore created a billing agreement everytime the process was run. Now I have multiple "Preapproved Payments" in my Paypal account. What is my Appstore's problem? Why does Appstore deny me a "Billing ID" input field to manually confirm my approval?

We are users just like yourself you need to be in touch with the Mac App Store for support. In the App Store click Support which is located in Quick Links and follow the prompts for troubleshooting. If you still can't figure it out then call AppleCare or visit your local Apple Store for help.

Trouble setting up iTunes account with Paypal

I've been having a really hard time setting an iTunes account. I don't want to use credit cards at all and according to the iTunes customer support, I don't need a credit card:
"A credit card is not required. However, if you do not wish to add a credit card, you must add a debit card or add and confirm a bank account before you can send money with your PayPal account."
I've had my Paypal account for a while now and I have my bank account confirmed and tied with Paypal. My problem occurs when I try to make an iTunes account. I select Paypal from the payment choices and choose to validate it. I'm taken to a login screen for Paypal where I log into my account and accept the billing agreement. Afterward, I'm brought to a screen where I have to input credit card information. I have a bank account confirmed with my Paypal account, so why would I need a credit card? Please, can somebody help me out here?
I sent Apple's customer service an email about a week ago and I'll I got back was a confirmatio of the email I sent.

I've e mailed support about this exact problem, (6 times) still no answer. My PayPal account shows iTunes as pre approved, but the bottom line iTunes *****.you know there has to be way more of us out there, the obviously don't care.To bad iTunes has to ruin the iPod. sorry, but it seems ikewasted time. Try Paypal support.
signed, i Tuneless

How do I associate PayPal with my apple account

Hi, I used to be able to use Paypal to pay for iPhone apps in the app store. Recently, when I try to buy or download a free app, I get an error message that says Paypal is not supported on my iPhone. I also have the Paypal app downloaded on my phone to use it for non-app store personal transactions I can use Paypal successfully for other transactions such as Amazon, etc. If it matters, the change occurred on my iPhone because I disputed a Paypal transaction for the Apple Store, and when the situation was being resolved i received a message (email maybe? I forget) asking me if I wanted to stop using that vendor. I misunderstood the question, and I chose "Yes," but did not realize it would mean Paypal was removed from my iPhone. How do I get my iPhone to support PayPal again? Thanks.

Menel, thank you, you got me headed on the road to fix this. To solve the "Paypal is not supported on this iPhone" problem, do Not go to apple.com, it will not help you. To fix the "Paypal not supported" problem: Open iTunes on a computer (Not on your iPhone) > Store > View my account (and notice the email address next to it, is it correct?, it doesn't matter, go to the next step) > Enter your iTunes password > Payment type,click "edit" > (now look at the email address associated with the Paypal icon, is it correct?, it doesn't matter, go on to the next step) > click the Paypal icon (it will take you to Paypal website) > log into Paypal > click Agree and Continue > make sure it says "You have successfully created a billing agreement." Now go to your iPhone and download an app to make sure everything works correctly again. Yeah!!
If you have more than one Paypal account, and you want to use a different Paypal account than the one associated with the email address that appears as you go through these steps, when you get to the step > Payment type, click "edit" > (now look at the email address associated with the Paypal icon, is it correct?), IF YOU WANT A DIFFERENT PAYPAL ACCOUNT > click "To choose a different account click here" (It will take you to the Paypal website) > change the email address listed to the address that is associated with the Paypal account you prefer to use, then log into Paypal using the password for that updated account address > click Agree and Continue > make sure it says "You have successfully created a billing agreement." Now go to your iPhone and download an app to make sure everything works properly again.

How Do I Complain to the Highest-Level re. iTunes Debacle?

I've had the single-worst customer service experience I've ever had with an online retailer when I tried to buy 3 iTunes email gift certificates on Xmas Day, and I want to send the story of this nightmare to someone who might actually care or do something about it.
I'll post the story that I sent to the Level 2 support supervisor below, but she ended up doing nothing to fix my problems & then refunded my purchase instead of trying to fix the problem. I want to complain about her & the service in general...who do I go to?
Here's the note I sent the supervisor on 12/29:
Here's the deal: On Christmas day, I wanted to purchase three $20 email gift certificates from iTunes. They were for three separate people, but all were being sent to the same email address:t
At first I tried to pay via PayPal, but that did not work; I did everything properly...got sent to PayPal's site, authorized the payment, and PayPal says "You have successfully created a billing agreement". But then when you hit the "Return to iTunes Store" button, a "Launch Application" window pops up that says "This link needs to be open with an application" Then the white part of the box says "iTunes, there's a "Choose an Application:Select" button. At the bottom of this box, there's a checkmark box that says "Remember my choice for itmss links".
I choose 'iTunes' in the 'select' box, and then it opens a new iTunes page. But when I check the 'Account' options, it shows "No Credit Card Selected"...it did not recognize my selection of PayPal, it did not recognize PayPal's APPROVAL of my selection to use them for my iTunes purchases.
This exact thing happened back in November, I worked with many iTunes techs, and I thought it was resolved...but apparently it wasn't.
Anyhow, back to Christmas day...I went ahead and bought two of the certificates using my debit card. They went well, but then when I went to purchase the third card, a box popped up & said "You cannot make any more iTunes purchases. Please check back later". That's right, you were telling me NOT TO BUY ANYTHING ELSE, even though the debit card was fine. So I changed the credit card info to another card, and I was able to purchase the final certificate.
But I noticed I didn't get any receipts in my email...I figure it was a busy day, it'll just take a while. About 6 hours later, when talking to the recipients' father, I told them I sent the certificates, but they checked, and nothing had arrived. I came home, & opened the transactions & hit "Report a Problem", then went to bed.
The next day, Monday, I noticed that the receipts finally arrived in my inbox. So I figured this meant that the cards were sent to the recipients as well. I was so certain of this that I didn't check with the recipients until Tuesday, and they said they had not received anything.
Now it's Wednesday, and I get the follow-up email from Raffi in your customer service department, and he sent me some 'canned' crap about " This can happen if the recipient's email address was typed incorrectly, or if the Gift Certificate email was deleted or filtered as junk email." I'm not a moron; I entered that email address correctly over a dozen times, and the recipients aren't morons; they know how to check the spam filter, and they're LONG TIME Apple customers who deal w/iTunes all the time.
He also told me how to 'Resend' the certificates using the 'resend' button when you pull up the transactions in iTunes 'Account' info. But when I tried to resend them, I got a message that says "Your request is temporarily unable to proceed. Please try again later". That message STILL comes up, over 24 hours later.
After that happened yesterday, I went ballistic & contacted Apple via the phone, which escalated to you. The supervisor I talked to said there was a 'block' placed on my account preventing PayPal payments...but that didn't really address the other issues. The issues are:
Why am I prevented from buying things with PayPal.
Why was I prevented from buying the 3rd certificate on Xmas day?
Why am I unable to resend the certificates...it appears I'm 'blocked' on this, too.
Why haven't these certificates been delivered?
I'm REALLY furious over all this. I thought Apple was supposed to be the best (we're new customers, buying our first product in November, an iPod Touch)...but I've had nothing but problems. Not from the product, but from trying to SPEND MONEY WITH YOU!!!
I want answers. I want YOU to send official, Apple-branded email gift certificates to the recipients. I do NOT want to send them an email from me with the redemption codes, which show up in the transactions when you pull them up in 'Purchase History' in the 'Account' screen in iTunes.
Here are the receipt & order numbers for the transactions:

Sorry to hear about all of your problems but this is a user-to-user discussion area and not Apple employees.
You might want to contact someone here:
http://www.apple.com/contact

Where can I send a complaint email (not to the worthless BB online reps)?

I want to complain directly to someone in charge, not the worthless Best Buy online customer support.
A couple of weeks ago, I called my local Best Buy and inquired about the Galaxy Note 4 promo, specifically the Verizon version. I explained on the phone that I wanted to buy the Verizon Note 4 at full retail price (so as to not lose my unlimited data). I was assured that I could buy it full retail and take advantage of the $200 trade in promo.
The next day I went in to preorder it, and was at first told that I couldn't preorder at full price. After getting a manager, I was able to place my preorder, and again asked about the promo, again being told it would work at full retail.
A few days later, I read online that people were stating you couldn't qualify for the promo at full retail, so once again I called and asked, and was again told it would work.
A week ago, I went back with my trade in device to make sure it would be acceptable for the promo (it was), and I asked again. The store associate wasn't sure, so he called the mobile manager who told him that yes, I could use the $200 trade in promo if I was buying at full retail.
That's 4 different times I asked, and four different times I was assured it was OK. Then, on the day it released, I started reading online from people who were told they didn't qualify for the promo unless they entered a new contract or extended a current one, and that full retail phones didn't qualify. So I called again, and lo and behold, I was told that you couldn't do it and never could. I was told that all Best Buy promotions required a contract renewal or extension and always had. The mobile manager even told me that the terms and conditions stated that a contract renewal was required, and argued with me when I told him they didn't. I actually had to read them to him right off your website, after which he went to the site and read them himself. After admitting they didn't state that, he told me I was out of luck and that I wouldn't be getting the $200 trade in unless I renewed my contract. He was somewhaty rude about it at first, but got better as the call went on.
I am livid! Besides the fact that I was told over and over again that a contract wasn't required, NONE of the Best Buy terms printed anywhere (online or in the store) stated this was a requirement right up to the day the preorder period ended and the promo was taken down.
I want the email of someone at corporate HQ. I will never buy anything from this fraud of a company again, and I will disuade anyone I can from purchasing from Best Buy on any and every online forum I can find.

Good afternoon tedkord,
Welcome to the forum! I’m sure you were very excited to get your hands on the Samsung Galaxy Note 4 after its release. It is disheartening to hear that your experience with the $200 gift card trade-in promotion may have gone so awry due to some misinformation.
It is true that a 2-year agreement or installment billing agreement is required to qualify for this promotion. Our associates and agents should have all of the necessary information available to provide our customers with accurate and transparent information. It certainly seems like this may not have occurred during your interactions. I apologize if this is not what you were advised when you inquired on multiple occasions in regards to your desire to purchase the phone at full retail price.
I am sorry if this was not the news you were hoping for when you reached out to us on the forum. I hope that in the future you will give us the opportunity to provide you with a better experience, and that this particular experience has not influenced your future shopping destination.
If you should have any questions, please let me know.
Respectfully,
Tasha|Social Media Specialist | Best Buy® Corporate
Private Message

ITunes isn't being detected by web browsers

Hi.
I have iTunes 9.1.1.12 and I'm on a Dell Inspiron E1505 with Windows 7, 32-bit. When I try to associate my Apple ID with iTunes Store and add PayPal as my payment method, I get the "You have successfully created a Billing Agreement." message, but when I click the button to continue to iTunes Store...
Firefox 3.6.3 gives: "Firefox doesn't know how to open this address, because the protocol (itmss) isn't associated with any program."
Google Chrome 4.1.249.1064 unknown (45376) stays on the: "One Moment Please. Connecting to the iTunes Store.
Loading..." page.
Internet Explorer 8 does the same as Google Chrome.
To do that, I had to set each web browser as the default web browser.
iTunes doesn't recognize that I added PayPal as my payment method, and so I still get the error message: "This Apple ID has not yet been used with the iTunes Store. Please review your account information."
When I try to download an app...
Firefox gives: "Firefox doesn't know how to open this address, because the protocol (itms) isn't associated with any program."
Google Chrome gives: "Opening the iTunes Store. If iTunes doesn’t open, click the iTunes application icon in your Dock or on your Windows desktop."
Opening iTunes doesn't have the download come up, or whatever is supposed to happen.
Internet Explorer gives: "To download Facebook’s Facebook, you need to have iTunes."
This is all happening on iTunes that I have reinstalled already. Now there is an iTunes shortcut in C:\ProgramData\Microsoft\Windows\Start Menu\Programs\iTunes. When I open it, it leads to "Please wait while Windows configures iTunes." I've waited and let it do its thing, but that hasn't solved anything.
I do know I have iTunes installed since I can open it fine through C:\Program Files\iTunes.
Any help is appreciated!

Hello annette-paul,
Thanks for using Apple Support Communities.
For more information, take a look at:
iOS: Device not recognized in iTunes for Windows
http://support.apple.com/kb/ts1538
1. Update iTunes
2. Check the USB cable
3. Verify that Apple Mobile Device Support is installed
4. Restart the Apple Mobile Device Service
5. Verify that the Apple Mobile Device USB Driver is installed
6. Check for third-party software conflicts
Have a nice day,
Mario

Issues in WSDL Import

Hi all,
I'm trying to import a WSDL file into XI and I get this error
Unable to convert imported document to WSDL
Reason: Tag definitions cannot have an attribute version from namespace urn:ebay:api:PayPalAPI
Check the selected category
Kindly provide inputs
Thanks
Geetha
My WSDL strcuture looks like this.
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions ns:version="2.4" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns="urn:ebay:api:PayPalAPI" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:cc="urn:ebay:apis:CoreComponentTypes" targetNamespace="urn:ebay:api:PayPalAPI">
<wsdl:types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ebay:api:PayPalAPI" elementFormDefault="qualified" attributeFormDefault="unqualified">
<import namespace="urn:ebay:apis:CoreComponentTypes" schemaLocation="CoreComponentTypes.xsd" />
<import namespace="urn:ebay:apis:eBLBaseComponents" schemaLocation="eBLBaseComponents.xsd" />

<xs:element name="RequesterCredentials" type="ebl:CustomSecurityHeaderType" />

<xs:element name="RefundTransactionRequest" type="ns:RefundTransactionRequestType" />
<xs:element name="RefundTransactionResponse" type="ns:RefundTransactionResponseType" />
<xs:element name="RefundTransactionReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:RefundTransactionRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="RefundTransactionRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="TransactionID" type="ebl:TransactionId">
<annotation>
<documentation>
Unique identifier of the transaction you are refunding.
 
 
Required
 
 
Character length and limitations: 17 single-byte alphanumeric characters
</documentation>
</annotation>
</xs:element>
<xs:element name="RefundType" type="ebl:RefundType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Type of refund you are making
 
 
Required
</documentation>
</annotation>
</xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Refund amount.
 
 
Amount is
required
if RefundType is Partial.
 
 
NOTE: If RefundType is Full, do not set Amount.
</documentation>
</annotation>
</xs:element>
<xs:element name="Memo" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Custom memo about the refund.
 
 
Optional
 
 
Character length and limitations: 255 single-byte alphanumeric characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="RefundTransactionResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<sequence>
<element name="RefundTransactionID" type="ebl:TransactionId" minOccurs="0" maxOccurs="1" nillable="true">
<annotation>
<documentation>
Unique transaction ID of the refund.
 
 
Character length and limitations:17 single-byte characters
</documentation>
</annotation>
</element>
<element name="NetRefundAmount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>Amount subtracted from PayPal balance of original recipient of payment to make this refund</documentation>
</annotation>
</element>
<element name="FeeRefundAmount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>Transaction fee refunded to original recipient of payment</documentation>
</annotation>
</element>
<element name="GrossRefundAmount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>Amount of money refunded to original payer</documentation>
</annotation>
</element>
</sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="GetTransactionDetailsRequest" type="ns:GetTransactionDetailsRequestType" />
<xs:element name="GetTransactionDetailsResponse" type="ns:GetTransactionDetailsResponseType" />
<xs:element name="GetTransactionDetailsReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:GetTransactionDetailsRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="GetTransactionDetailsRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="TransactionID" type="ebl:TransactionId">
<annotation>
<documentation>
Unique identifier of a transaction.
 
 
Required
 
 
The details for some kinds of transactions cannot be retrieved with GetTransactionDetailsRequest. You cannot obtain details of bank transfer withdrawals, for example.
 
 
Character length and limitations: 17 single-byte alphanumeric characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="GetTransactionDetailsResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:PaymentTransactionDetails" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="BillUserRequest" type="ns:BillUserRequestType" />
<xs:element name="BillUserResponse" type="ns:BillUserResponseType" />
<xs:element name="BillUserReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:BillUserRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="BillUserRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element ref="ebl:MerchantPullPaymentDetails" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="BillUserResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:BillUserResponseDetails" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="TransactionSearchRequest" type="ns:TransactionSearchRequestType" />
<xs:element name="TransactionSearchResponse" type="ns:TransactionSearchResponseType" />
<xs:element name="TransactionSearchReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:TransactionSearchRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="TransactionSearchRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="StartDate" type="xs:dateTime" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
The earliest transaction date at which to start the search. No wildcards are allowed.
 
 
Required
</documentation>
</annotation>
</xs:element>
<xs:element name="EndDate" type="xs:dateTime" minOccurs="0">
<annotation>
<documentation>
The latest transaction date to be included in the search
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="Payer" type="ebl:EmailAddressType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by the buyers email address
 
 
Optional
 
 
Character length and limitations: 127 single-byte alphanumeric characters
</documentation>
</annotation>
</xs:element>
<xs:element name="Receiver" type="ebl:EmailAddressType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by the receivers email address. If the merchant account has only one email, this is the primary email. Can also be a non-primary email.
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="ReceiptID" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by the PayPal Account Optional receipt ID
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="TransactionID" type="ebl:TransactionId" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by the transaction ID.
 
 
Optional
 
 
The returned results are from the merchants transaction records.
 
 
Character length and limitations: 19 single-byte characters maximum
</documentation>
</annotation>
</xs:element>
<xs:element name="PayerName" type="ebl:PersonNameType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by the buyers name
 
 
Optional
 
 
Salutation: 20 single-byte character limit.
 
 
FirstName: 25 single-byte character limit.
 
 
MiddleName: 25 single-byte character limit.
 
 
LastName: 25 single-byte character limit.
 
 
Suffix: 12 single-byte character limit.
</documentation>
</annotation>
</xs:element>
<xs:element name="AuctionItemNumber" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by item number of the purchased goods.
 
 
Optional
 
 
To search for purchased items not related to auctions, set the AuctionItemNumber element to the value of the HTML item_number variable set in the shopping cart for the original transaction.
</documentation>
</annotation>
</xs:element>
<xs:element name="InvoiceID" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by invoice identification key, as set by you for the original transaction. InvoiceID searches the invoice records for items sold by the merchant, not the items purchased.
 
 
Optional
 
 
The value for InvoiceID must exactly match an invoice identification number. No wildcards are allowed.
 
 
Character length and limitations: 127 single-byte characters maximum
</documentation>
</annotation>
</xs:element>
<xs:element name="CardNumber" type="xs:string" minOccurs="0" maxOccurs="1" />
<xs:element name="TransactionClass" type="ebl:PaymentTransactionClassCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by classification of transaction. Some kinds of possible classes of transactions are not searchable with TransactionSearchRequest. You cannot search for bank transfer withdrawals, for example.
 
 
Optional
 
 
All: all transaction classifications.
 
 
Sent: only payments sent.
 
 
Received: only payments received.
 
 
MassPay: only mass payments.
 
 
MoneyRequest: only money requests.
 
 
FundsAdded: only funds added to balance.
 
 
FundsWithdrawn: only funds withdrawn from balance.
 
 
Referral: only transactions involving referrals.
 
 
Fee: only transactions involving fees.
 
 
Subscription: only transactions involving subscriptions.
 
 
Dividend: only transactions involving dividends.
 
 
Billpay: only transactions involving BillPay Transactions.
 
 
Refund: only transactions involving funds.
 
 
CurrencyConversions: only transactions involving currency conversions.
 
 
BalanceTransfer: only transactions involving balance transfers.
 
 
Reversal: only transactions involving BillPay reversals.
 
 
Shipping: only transactions involving UPS shipping fees.
 
 
BalanceAffecting: only transactions that affect the account balance.
 
 
ECheck: only transactions involving eCheck
</documentation>
</annotation>
</xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by transaction amount
 
 
Optional
 
 
You must set the currencyID attribute to one of the three-character currency codes for any of the supported PayPal currencies.
</documentation>
</annotation>
</xs:element>
<xs:element name="CurrencyCode" type="ebl:CurrencyCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by currency code
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="Status" type="ebl:PaymentTransactionStatusCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by transaction status
 
 
Optional
 
 
Pending: The payment is pending. The specific reason the payment is pending is returned by the GetTransactionDetails APIPendingReason element. For more information, see PendingReason.
 
 
Processing: The payment is being processed.
 
 
Success: The payment has been completed and the funds have been added successfully to your account balance.
 
 
Denied: You denied the payment. This happens only if the payment was previously pending.
 
 
Reversed: A payment was reversed due to a chargeback or other type of reversal. The funds have been removed from your account balance and returned to the buyer.
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="TransactionSearchResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:PaymentTransactions" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>Results of a Transaction Search.</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="MassPayRequest" type="ns:MassPayRequestType" />
<xs:element name="MassPayResponse" type="ns:MassPayResponseType" />
<xs:element name="MassPayReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:MassPayRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="MassPayRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="EmailSubject" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Subject line of the email sent to all recipients. This subject is not contained in the input file; you must create it with your application.
 
 
Optional
 
 
Character length and limitations: 255 single-byte alphanumeric characters
</documentation>
</annotation>
</xs:element>
<xs:element name="ReceiverType" type="ebl:ReceiverInfoCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Indicates how you identify the recipients of payments in all MassPayItems: either by EmailAddress (ReceiverEmail in MassPayItem), PhoneNumber (ReceiverPhone in MassPayItem), or by UserID (ReceiverID in MassPayItem).
 
 
Required.
You must specify one or the other of EmailAddress or UserID.
</documentation>
</annotation>
</xs:element>
<xs:element name="MassPayItem" type="ns:MassPayRequestItemType" minOccurs="1" maxOccurs="250">
<annotation>
<documentation>
Details of each payment. A single MassPayRequest can include up to 250 MassPayItems.
 
 
Required
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="MassPayResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType" />
</xs:complexContent>
</xs:complexType>
<xs:complexType name="MassPayRequestItemType">
<xs:annotation>
<xs:documentation>MassPayRequestItemType</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="ReceiverEmail" type="ebl:EmailAddressType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Email address of recipient.
 
 
Required
 
 
You must specify ReceiverEmail, ReceiverPhone, or ReceiverID, but all MassPayItems in a request must use the same field to specify recipients.
 
 
Character length and limitations: 127 single-byte characters maximum.
</documentation>
</annotation>
</xs:element>
<xs:element name="ReceiverPhone" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Phone number of recipient.
 
 
Required
 
 
You must specify ReceiverEmail, ReceiverPhone, or ReceiverID, but all MassPayItems in a request must use the same field to specify recipients.
 
 
</documentation>
</annotation>
</xs:element>
<xs:element name="ReceiverID" type="ebl:UserIDType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Unique PayPal customer account number. This value corresponds to the value of PayerID returned by GetTransactionDetails.
 
 
Required
 
 
You must specify ReceiverEmail, ReceiverPhone, or ReceiverID, but all MassPayItems in a request must use the same field to specify recipients.
 
 
Character length and limitations: 17 single-byte characters maximum.
</documentation>
</annotation>
</xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Payment amount. You must set the currencyID attribute to one of the three-character currency codes for any of the supported PayPal currencies.
 
 
Required
 
 
You cannot mix currencies in a single MassPayRequest. A single request must include items that are of the same currency.
</documentation>
</annotation>
</xs:element>
<xs:element name="UniqueId" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Transaction-specific identification number for tracking in an accounting system.
 
 
Optional
 
 
Character length and limitations: 30 single-byte characters. No whitespace allowed.
</documentation>
</annotation>
</xs:element>
<xs:element name="Note" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Custom note for each recipient.
 
 
Optional
 
 
Character length and limitations: 4,000 single-byte alphanumeric characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:element name="BAUpdateRequest" type="ns:BAUpdateRequestType" />
<xs:element name="BAUpdateResponse" type="ns:BAUpdateResponseType" />
<xs:element name="BillAgreementUpdateReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:BAUpdateRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="BAUpdateRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="MpID" type="ebl:MerchantPullIDType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Preapproved Payments billing agreement identification number. Corresponds to the FORM variable mp_id.
 
 
Required
 
 
Character limit: 19 single-byte alphanumeric characters. The format of a billing agreement identification number is the single-character prefix B, followed by a hyphen and an alphanumeric character string:
 
 
B-unique_alphanumeric_string
</documentation>
</annotation>
</xs:element>
<xs:element name="Custom" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Custom annotation field for your exclusive use
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="Desc" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Description of goods or services associated with the billing agreement
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="MpStatus" type="ebl:MerchantPullStatusCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
The current status of the billing agreement
 
 
Optional
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="BAUpdateResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:BAUpdateResponseDetails" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="AddressVerifyRequest" type="ns:AddressVerifyRequestType" />
<xs:element name="AddressVerifyResponse" type="ns:AddressVerifyResponseType" />
<xs:element name="AddressVerifyReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:AddressVerifyRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="AddressVerifyRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="Email" type="ebl:EmailAddressType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Email address of buyer to be verified.
 
 
Required
 
 
Maximum string length: 255 single-byte characters Input mask: ?@?.??
</documentation>
</annotation>
</xs:element>
<xs:element name="Street" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
First line of buyers billing or shipping street address to be verified.
 
 
Required
 
 
For verification, input value of street address must match the first three single-byte characters of the street address on file for the PayPal account.
 
 
Maximum string length: 35 single-byte characters Alphanumeric plus Whitespace and case of input value are ignored.
</documentation>
</annotation>
</xs:element>
<xs:element name="Zip" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Postal code to be verified.
 
 
Required
 
 
For verification input value of postal code must match the first five single-byte characters of the postal code on file for the PayPal account.
 
 
Maximum string length: 16 single-byte characters Whitespace and case of input value are ignored.
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="AddressVerifyResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="ConfirmationCode" type="ebl:AddressStatusCodeType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Confirmation of a match with one of the following tokens:
 
 
None: The input value of the Email object does not match any email address on file at PayPal.
 
 
Confirmed: If the value of the StreetMatch object is Matched PayPal responds that the entire postal address is confirmed.
 
 
Unconfirmed: PayPal responds that the postal address is unconfirmed
</documentation>
</annotation>
</xs:element>
<xs:element name="StreetMatch" type="ebl:MatchStatusCodeType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
PayPal has compared the postal address you want to verify with the postal address on file at PayPal.
 
 
None: The input value of the Email object does not match any email address on file at PayPal. In addition an error response is returned. No further comparison of other input values has been made.
 
 
Matched: The street address matches the street address on file at PayPal.
 
 
Unmatched: The street address does not match the street address on file at PayPal.
</documentation>
</annotation>
</xs:element>
<xs:element name="ZipMatch" type="ebl:MatchStatusCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
PayPal has compared the zip code you want to verify with the zip code on file for the email address.
 
 
None: The street address was unmatched. No further comparison of other input values has been made.
 
 
Matched: The zip code matches the zip code on file at PayPal.
 
 
Unmatched: The zip code does not match the zip code on file at PayPal.
</documentation>
</annotation>
</xs:element>
<xs:element name="CountryCode" type="ebl:CountryCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>Two-character country code (ISO 3166) on file for the PayPal email address.</documentation>
</annotation>
</xs:element>
<xs:element name="PayPalToken" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
The token prevents a buyer from using any street address other than the address on file at PayPal during additional purchases he might make from the merchant. It contains encrypted information about the users street address and email address. You can pass the value of the token with the Buy Now button HTML address_api_token variable so that PayPal prevents the buyer from using any street address or email address other than those verified by PayPal. The token is valid for 24 hours.
 
Character length and limitations: 94 single-byte characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="EnterBoardingRequest" type="ns:EnterBoardingRequestType" />
<xs:element name="EnterBoardingResponse" type="ns:EnterBoardingResponseType" />
<xs:element name="EnterBoardingReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:EnterBoardingRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="EnterBoardingRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element ref="ebl:EnterBoardingRequestDetails" minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="EnterBoardingResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="Token" type="ebl:ExpressCheckoutTokenType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
A unique token that identifies this boarding session. Use this token with the GetBoarding Details API call.
 
 
Character length and limitations: 64 alphanumeric characters. The token has the following format:
 
 
OB-61characterString
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="GetBoardingDetailsRequest" type="ns:GetBoardingDetailsRequestType" />
<xs:element name="GetBoardingDetailsResponse" type="ns:GetBoardingDetailsResponseType" />
<xs:element name="GetBoardingDetailsReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:GetBoardingDetailsRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="GetBoardingDetailsRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="Token" type="ebl:ExpressCheckoutTokenType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
A unique token returned by the EnterBoarding API call that identifies this boarding session.
 
 
Required
 
 
Character length and limitations: 64 alphanumeric characters. The token has the following format:
 
 
OB-61characterString
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="GetBoardingDetailsResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:GetBoardingDetailsResponseDetails" minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="SetExpressCheckoutRequest" type="ns:SetExpressCheckoutRequestType" />
<xs:element name="SetExpressCheckoutResponse" type="ns:SetExpressCheckoutResponseType" />
<xs:element name="SetExpressCheckoutReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:SetExpressCheckoutRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="SetExpressCheckoutRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element ref="ebl:SetExpressCheckoutRequestDetails" minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="SetExpressCheckoutResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="Token" type="ebl:ExpressCheckoutTokenType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
A timestamped token by which you identify to PayPal that you are processing this payment with Express Checkout. The token expires after three hours. If you set Token in the SetExpressCheckoutRequest, the value of Token in the response is identical to the value in the request.
 
 
Character length and limitations: 20 single-byte characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="GetExpressCheckoutDetailsRequest" type="ns:GetExpressCheckoutDetailsRequestType" />
<xs:element name="GetExpressCheckoutDetailsResponse" type="ns:GetExpressCheckoutDetailsResponseType" />
<xs:element name="GetExpressCheckoutDetailsReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:GetExpressCheckoutDetailsRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="GetExpressCheckoutDetailsRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="Token" type="ebl:ExpressCheckoutTokenType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
A timestamped token, the value of which was returned by SetExpressCheckoutResponse.
 
 
Required
 
 
Character length and limitations: 20 single-byte characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="GetExpressCheckoutDetailsResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:GetExpressCheckoutDetailsResponseDetails" minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="DoExpressCheckoutPaymentRequest" type="ns:DoExpressCheckoutPaymentRequestType" />
<xs:element name="DoExpressCheckoutPaymentResponse" type="ns:DoExpressCheckoutPaymentResponseType" />
<xs:element name="DoExpressCheckoutPaymentReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:DoExpressCheckoutPaymentRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="DoExpressCheckoutPaymentRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element ref="ebl:DoExpressCheckoutPaymentRequestDetails" minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="DoExpressCheckoutPaymentResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:DoExpressCheckoutPaymentResponseDetails" minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="DoDirectPaymentRequest" type="ns:DoDirectPaymentRequestType" />
<xs:element name="DoDirectPaymentResponse" type="ns:DoDirectPaymentResponseType" />
<xs:element name="DoDirectPaymentReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:DoDirectPaymentRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="DoDirectPaymentRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element ref="ebl:DoDirectPaymentRequestDetails" minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="DoDirectPaymentResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>The amount of the payment as specified by you on DoDirectPaymentRequest.</documentation>
</annotation>
</xs:element>
<xs:element name="AVSCode" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Address Verification System response code. Character limit: One single-byte alphanumeric character
<table>
<tr>
<th>AVS Code</th>
<th>Meaning</th>
<th>Matched Details</th>
</tr>
<tr>
<td>A</td>
<td>Address</td>
<td>Address only (no ZIP)</td>
</tr>
<tr>
<td>B</td>
<td>International A</td>
<td>Address only (no ZIP)</td>
</tr>
<tr>
<td>C</td>
<td>International N</td>
<td>None</td>
</tr>
<tr>
<td>D</td>
<td>International X</td>
<td>Address and Postal Code</td>
</tr>
<tr>
<td>E</td>
<td>Not allowed for MOTO (Internet/Phone) transactions</td>
<td>Not applicable</td>
</tr>
<tr>
<td>F</td>
<td>UK-specific X</td>
<td>Address and Postal Code</td>
</tr>
<tr>
<td>G</td>
<td>Global Unavailable</td>
<td>Not applicable</td>
</tr>
<tr>
<td>I</td>
<td>International Unavailable</td>
<td>Not applicable</td>
</tr>
<tr>
<td>N</td>
<td>No</td>
<td>None</td>
</tr>
<tr>
<td>P</td>
<td>Postal (International Z)</td>
<td>Postal Code only (no Address)</td>
</tr>
<tr>
<td>R</td>
<td>Retry</td>
<td>Not applicable</td>
</tr>
<tr>
<td>S</td>
<td>Service not Supported</td>
<td>Not applicable</td>
</tr>
<tr>
<td>U</td>
<td>Unavailable</td>
<td>Not applicable</td>
</tr>
<tr>
<td>W</td>
<td>Whole ZIP</td>
<td>Nine-digit ZIP code (no Address)</td>
</tr>
<tr>
<td>X</td>
<td>Exact match</td>
<td>Address and nine-digit ZIP code</td>
</tr>
<tr>
<td>Y</td>
<td>Yes</td>
<td>Address and five-digit ZIP</td>
</tr>
<tr>
<td>Z</td>
<td>ZIP</td>
<td>Five-digit ZIP code (no Address)</td>
</tr>
<tr>
<td>All others</td>
<td>Error Not applicable</td>
<td />
</tr>
</table>
</documentation>
</annotation>
</xs:element>
<xs:element name="CVV2Code" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Result of the CVV2 check by PayPal.
<table>
<tr>
<th>CVV2 Code</th>
<th>Meaning</th>
<th>Matched Details</th>
</tr>
<tr>
<td>M</td>
<td>Match</td>
<td>CVV2</td>
</tr>
<tr>
<td>N</td>
<td>No match</td>
<td>None</td>
</tr>
<tr>
<td>P</td>
<td>Not Processed</td>
<td>Not applicable</td>
</tr>
<tr>
<td>S</td>
<td>Service not Supported</td>
<td>Not applicable</td>
</tr>
<tr>
<td>U</td>
<td>Unavailable</td>
<td>Not applicable</td>
</tr>
<tr>
<td>X</td>
<td>No response</td>
<td>Not applicable</td>
</tr>
<tr>
<td>All others</td>
<td>Error</td>
<td>Not applicable</td>
</tr>
</table>
</documentation>
</annotation>
</xs:element>
<xs:element name="TransactionID" type="ebl:TransactionId" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Transaction identification number.
 
 
Character length and limitations: 19 characters maximum.
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="DoCaptureRequest" type="ns:DoCaptureRequestType" />
<xs:element name="DoCaptureResponse" type="ns:DoCaptureResponseType" />
<xs:element name="DoCaptureReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:DoCaptureRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="DoCaptureRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="AuthorizationID" type="ebl:AuthorizationId" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
The authorization identification number of the payment you want to capture.
 
 
Required
 
 
Character length and limits: 19 single-byte characters maximum
</documentation>
</annotation>
</xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Amount to authorize. You must set the currencyID attribute to USD.
 
 
Required
 
 
Limitations: Must not exceed $10,000 USD in any currency. No currency symbol. Decimal separator must be a period (.), and the thousands separator must be a comma (,)
</documentation>
</annotation>
</xs:element>
<xs:element name="CompleteType" type="ebl:CompleteCodeType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Indicates if this capture is the last capture you intend to make. The default is Complete. If CompleteType is Complete, any remaining amount of the original reauthorized transaction is automatically voided.
 
 
Required
 
 
Character length and limits: 12 single-byte alphanumeric characters
</documentation>
</annotation>
</xs:element>
<xs:element name="Note" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
An informational note about this settlement that is displayed to the payer in email and in transaction history.
 
 
Optional
 
 
Character length and limits: 255 single-byte characters
</documentation>
</annotation>
</xs:element>
<xs:element name="InvoiceID" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Your invoice number or other identification number.
 
 
The InvoiceID value is recorded only if the authorization you are capturing is an order authorization, not a basic authorization.
 
 
Optional
 
 
Character length and limits: 127 single-byte alphanumeric characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="DoCaptureResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:DoCaptureResponseDetails" minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="DoReauthorizationRequest" type="ns:DoReauthorizationRequestType" />
<xs:element name="DoReauthorizationResponse" type="ns:DoReauthorizationResponseType" />
<xs:element name="DoReauthorizationReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:DoReauthorizationRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="DoReauthorizationRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="AuthorizationID" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
The value of a previously authorized transaction identification number returned by a PayPal product. You can obtain a buyers transaction number from the TransactionID element of the PayerInfo structure returned by GetTransactionDetailsResponse.
 
 
Required
 
 
Character length and limits: 19 single-byte characters maximum
</documentation>
</annotation>
</xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Amount to reauthorize.
 
 
Required
 
 
Limitations: Must not exceed $10,000 USD in any currency. No currency symbol. Decimal separator must be a period (.), and the thousands separator must be a comma (,).
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="DoReauthorizationResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="AuthorizationID" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
A new authorization identification number.
 
 
Character length and limits: 19 single-byte characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="DoVoidRequest" type="ns:DoVoidRequestType" />
<xs:element name="DoVoidResponse" type="ns:DoVoidResponseType" />
<xs:element name="DoVoidReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:DoVoidRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="DoVoidRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="AuthorizationID" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
The value of the original authorization identification number returned by a PayPal product.
 
 
If you are voiding a transaction that has been reauthorized, use the ID from the original authorization, and not the reauthorization.
 
 
Required
 
 
Character length and limits: 19 single-byte characters
</documentation>
</annotation>
</xs:element>
<xs:element name="Note" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
An informational note about this settlement that is displayed to the payer in email and in transaction history.
 
 
Optional
 
 
Character length and limits: 255 single-byte characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="DoVoidResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="AuthorizationID" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
The authorization identification number you specified in the request.
 
 
Character length and limits: 19 single-byte characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="DoAuthorizationRequest" type="ns:DoAuthorizationRequestType" />
<xs:element name="DoAuthorizationResponse" type="ns:DoAuthorizationResponseType" />
<xs:element name="DoAuthorizationReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:DoAuthorizationRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="DoAuthorizationRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="TransactionID" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
The value of the orders transaction identification number returned by a PayPal product.
 
 
Required
 
 
Character length and limits: 19 single-byte characters maximum
</documentation>
</annotation>
</xs:element>
<xs:element name="TransactionEntity" type="ebl:TransactionEntityType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Type of transaction to authorize. The only allowable value is
Order
which means that the transaction represents a customer order that can be fulfilled over 29 days.
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Amount to authorize.
&l

can you remove this from WSDL <wsdl:definitions> tag.
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:cc="urn:ebay:apis:CoreComponentTypes"
and add name="yourmessage interface" in <wsdl:definitions> tag.

I can't link my Paypal Account to my iTunes Stores Account

I am attempting to connect my billing preference in the iTunes Store to my Paypal account. The process takes me to Paypal and then at the end is supposed to return me to the iTunes Store. After clicking on "Return to iTunes Store" the page "Returning to the iTunes Store...Please Wait" loads and then stops/hangs.
This error message is in my taskbar: (using Internet Explorer as my default browser when I get this message)
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; MEGAUPLOAD 3.0; .NET CLR 3.5.30729; .NET CLR 3.0.30729; OfficeLivePatch.1.3; OfficeLiveConnector.1.5; .NET4.0C)
Timestamp: Sat, 18 Dec 2010 22:00:58 UTC
Message: The data area passed to a system call is too small.
Line: 6
Char: 104793
Code: 0
URI: https://buy.itunes.apple.com/htmlResources/CC7A/web-storefront-preview.jsz
This is using Internet Explorer as my default browser. I normally use FireFox, but Firefox blocks the return to the iTunes Store, as well.
I've contacted both Paypal (no problems there with my account or their system) and Apple Support (they can't seem to figure this out -- appears to be either an OS or Browser problem to them.) I've also posted this with the Microsoft Solutions forum but their suggestions haven't worked. Nothing seems to work. I'm hoping you can help me resolve this issue. An iTunes technician is working on it apparently. He contacted me on 12/23/10 but I haven't heard back from him.
"My name is Jonathan and I have been assigned your case. I want to thank you for your continued patience while I work on your issue involving setting up PayPal on your account.
I hope to have a resolution for you very soon, hopefully within in a couple of days, and will be certain to notify you as soon as more information is available.
The iTunes Store is dedicated to creating a pleasant music-shopping alternative for music lovers of all walks of life. Your experience is very important to Apple. Thank you for giving Apple the opportunity to improve its services. Have a great day."
The browser appears to be blocking the return to the iTunes Store so I can finalize the payment change to Paypal. I've turned off the Windows firewall and my anti-virus. Did not make any difference.

I'm having exactly the same error, but on a Mac using Safari as de default browser....
When it goes back to iTunes I can only see the original page where I launched the paypal website from.... nothing happens and if I click continue the whole process starts again. I guess by now I must have created 30+ billing agreements...

Billing Agreements

Similar Messages

Maybe you are looking for