efun.id.api

<back to all web services

OnePayPaymentIpnUrlRequest

The following routes are available for this service:
GET/api/v1/onepay/payment-ipn-invoice
"use strict";
export class OnePayLogResponse {
    /** @param {{userName?:string,orderId?:string,price?:number,payCode?:string,payMsg?:string,payChannel?:string,payDate?:string}} [init] */
    constructor(init) { Object.assign(this, init) }
    /** @type {string} */
    userName;
    /** @type {string} */
    orderId;
    /** @type {number} */
    price;
    /** @type {string} */
    payCode;
    /** @type {string} */
    payMsg;
    /** @type {string} */
    payChannel;
    /** @type {string} */
    payDate;
}
export class OnePayPaymentIpnUrlRequest {
    /** @param {{vpc_MerchTxnRef?:string,vpc_OrderInfo?:string,vpc_CardNum?:string}} [init] */
    constructor(init) { Object.assign(this, init) }
    /** @type {string} */
    vpc_MerchTxnRef;
    /** @type {string} */
    vpc_OrderInfo;
    /** @type {?string} */
    vpc_CardNum;
}

JavaScript OnePayPaymentIpnUrlRequest DTOs

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

GET /api/v1/onepay/payment-ipn-invoice HTTP/1.1 
Host: efun-id-api-sandbox.efun.vn 
Accept: application/json

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

{"userName":"String","orderId":"String","price":0,"payCode":"String","payMsg":"String","payChannel":"String","payDate":"0001-01-01T00:00:00.0000000+07:06"}