efun.id.api

OnePayPaymentCallbackUrlRequest

The following routes are available for this service:
POST	/api/v1/onepay/payment-callback-url

**OnePayPaymentCallbackUrlRequest** Parameters:
Name	Parameter	Data Type	Required
vpc_MerchTxnRef	body	string	Yes
vpc_OrderInfo	body	string	Yes
vpc_CardNum	body	string	No

**OnePayLogResponse** Parameters:
Name	Parameter	Data Type	Required
UserName	form	string	Yes
OrderId	form	string	Yes
Price	form	long	No
PayCode	form	string	Yes
PayMsg	form	string	Yes
PayChannel	form	string	Yes
PayDate	form	DateTime	No

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 /api/v1/onepay/payment-callback-url HTTP/1.1 
Host: efun-id-api-sandbox.efun.vn 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<OnePayPaymentCallbackUrlRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/efun.id.api.ServiceModel">
  <vpc_CardNum>String</vpc_CardNum>
  <vpc_MerchTxnRef>String</vpc_MerchTxnRef>
  <vpc_OrderInfo>String</vpc_OrderInfo>
</OnePayPaymentCallbackUrlRequest>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<OnePayLogResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/efun.id.data.Models">
  <OrderId>String</OrderId>
  <PayChannel>String</PayChannel>
  <PayCode>String</PayCode>
  <PayDate>0001-01-01T00:00:00</PayDate>
  <PayMsg>String</PayMsg>
  <Price>0</Price>
  <UserName>String</UserName>
</OnePayLogResponse>