A unique identifier for the order.
The client is responsible for ensuring uniqueness across all transactions the client initiates with this service.
Paid order total amount
Error scenario e.g. no prior AlipayGetPayment request is found.
Funds have been transfered from the customers account. Safe to confirm order
and ship at this point.
Payment is pending at Alipay for the buyer to confirm funds. Webstore can display
'thank you' page when this status is returned after maximum reattempts are reached.
Payment has been rejected. Order should be cancelled
when this status is returned. Webstore should provide alternate payment options.
Request to Alipay has timed out
This xsd:any element indicates that future optional elements may show up in this location of the XML document in the
responses returned from the service.
The purpose of this xsd:any element is to define a more robust service interface that allows for new, optional elements to be added
to the service's responses without the service clients' code throwing exceptions.
The client code for this service call should be written to not break if new optional XML elements show up in this part
of the service response. Modern XML marshalling frameworks often process xsd:any elements properly out-of-the-box
(for example, in Java, JAXB and JibX XML marshalling frameworks both honor xsd:any elements and don't throw exceptions
if new optional elements appear within the xsd:any section of the XML document).
Developers' unit tests of their service client code should include a test case where this reply message
contains one or more new elements in this location of the XML document.
If new optional elements are added to this interface, a new schema will be created, communications will be sent out,
and you will have the option to modify your service client code to process and use the new elements.
If there is no need/desire to process the new optional elements, your service client should continue to run
uninterrupted as long as it is built to honor this xsd:any element.