To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
HTTP + XML
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /transferTicket/payTopupWith3DSecure HTTP/1.1
Host: stubbur-app.azurewebsites.net
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<PayTopupWith3DSecureRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<AmountMinor>0</AmountMinor>
<BorgunCardToken>String</BorgunCardToken>
<BorgunMpiToken>String</BorgunMpiToken>
<Currency>String</Currency>
<PaymentPhoneNumber>String</PaymentPhoneNumber>
<SessionToken>String</SessionToken>
</PayTopupWith3DSecureRequest>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<PayTopupWith3DSecureResult xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TicketUserServices.ServiceModel">
<AmountIsk>0</AmountIsk>
<AuthCode>String</AuthCode>
<Code>String</Code>
<LastFourDigits>String</LastFourDigits>
<Message>String</Message>
<NewTicketTokenId>String</NewTicketTokenId>
<Ok>false</Ok>
<PaymentReference>String</PaymentReference>
<Status>String</Status>
<StatusCode>0</StatusCode>
<TransferLogId>0</TransferLogId>
</PayTopupWith3DSecureResult>