Code has been copied.

Webhook list

List of webhooks provided by Eximbay

Chargeback

Chargeback notifications and resolutions can be received via email or webhook. Integration preparation details can be reviewed here.

The Chargeback Webhook will send the chargeback transaction every hour.
If the merchant's Webhook URL receives the request successfully, it should output {"rescode": "0000", "resmsg": "Success"}.
If the Webhook URL cannot be reached successfully, or if the rescode is not "0000", the request will be re-sent up to a maximum of three times.

Header

    
    Http Method : POST
    Content-type : application/json;charset=utf-8
Event parameter

type string

CHARGEBACK

data object* The status of the chargeback object has been updated.

mid string

A unique merchant ID generated by Eximbay to identify the merchant.

order_id string

This is a unique identifier used to classify a merchant's order. This value cannot be reused for failed orders.

transaction_id string

This is a unique Eximbay transaction ID used to classify a merchant.

currency string

Payment Currency Unit. For detailed information, please refer to the currency code.

amount string

Total Payment Amount. The amount must be greater than 0 and , cannot be used.

payment_method string

Payment Method Code: Defines the designated payment method that will redirect to the payment page. Please refer to the payment method code for details.

auth_code string

Authorization number

* A simplified payment transaction does not generate an authorization number.

transaction_date string

The returned authorization date is formatted as YYYYMMDDHHMMSS.

pay_to string

Billing merchant's name

param1 string

A preparatory parameter available for merchants if needed. The parameter length is limited to 255 characters.

param2 string

A preparatory parameter available for merchants if needed.

param3 string

A preparatory parameter available for merchants if needed.

payer_authentication_flag string

Status value for identifying a 3DS transaction.

refund_flag string

Status value for identifying a refundable transaction

chargeback_status string

The chargeback status at the time the chargeback was received. The status will include 'REPORT' (notification) and 'RESOLVE' (Rebuttal).

chargeback_reason string

The reason for filing the chargeback

chargeback_report_date string

The chargeback notification date is formatted as YYYYMMDDHHMMSS.

chargeback_deadline string

The chargeback Rebuttal filing expiration date is formatted as YYYYMMDDHHMMSS.

chargeback_resolve_date string

The chargeback rebuttal has been successfully processed date is formatted as YYYYMMDDHHMMSS.

chargeback_deduct_date string

The chargeback deduction has been successfully processed date is formatted as YYYYMMDDHHMMSS. 

{
    "type": "CHARGEBACK",
    "data": 
    {
        "mid": "11E11A11DD",
        "order_id": "20241108113100",
        "transaction_id": "11E11A11DDW000000000000",
        "currency": "USD",
        "amount": "3.00",
        "payment_method": "P101",
        "auth_code": "710001",
        "transaction_date": "20241108113722",
        "pay_to": "EXIMBAY.COM",
        "param1": "",
        "param2": "",
        "param3": "TEST",
        "payer_authentication_flag": "N",
        "refund_flag": "N",
        "chargeback_status": "DEDUCTION",
        "chargeback_reason": "deduct 테스트",
        "chargeback_report_date": "20250320",
        "chargeback_deadline": "20250410",
        "chargeback_resolve_date": "",
        "chargeback_deduct_date": "20250401"
    }
}

Payout service

This is available for merchants using the payout service.
After the sub-merchant's verification process and payout are completed, the information can be received via Webhook.

Integration preparation details can be reviewed here.

PAYOUT_SUBMALL_REVIEW_COMPLETE

POST/Registered Webhook Endpoint URL

After the verification process, if the sub-merchant's status is SUBMALL_REVIEW_COMPLETE or SUBMALL_REVIEW_REJECT a Webhook will be transmitted.
Event parameter

type string

Webhook type

data object* Details of the Webhook: The data object varies for each Webhook.

submall_id string

This is a unique ID used to classify a registered sub_merchant.

submall_status string

Sub_merchant's service status. Please refer to the service status code.

submall_review_status string

Sub_merchant's service status. Please refer to the service status code.

submall_review_modified_date datetime

Date of verification status update 

{
    "type": "PAYOUT_SUBMALL_REVIEW_COMPLETE",
    "data": {
        "submall_id": "00000000-0000-0000-0000-000000000000",
        "submall_status": "OK",
        "submall_review_status": "SUBMALL_REVIEW_COMPLETE",
        "submall_review_modified_date": "2025-02-12"
    }
}

PAYOUT_REMITTANCE_COMPLETE

POST/Registered Webhook Endpoint URL

When the payout status is 'COMPLETE' or 'FAILED,' a Webhook will be transmitted.
Event parameter

type string

Webhook type

data object* Details of the Webhook: The data object varies for each Webhook.

payout_id string

Payout request ID

status string

Payout process status

remit_time string

Payout schedule (yyyy-MM-dd hh:mm:ss) 

{
    "type": "PAYOUT_REMITTANCE_COMPLETE",
    "data": [
        {
            "payout_id": "00000000-0000-0000-0000-000000000000",
            "status": "COMPLETE",
            "remit_time": "2025-01-13 01:45:32"
        },
        {
            "payout_id": "00000000-0000-0000-0000-000000000000",
            "status": "COMPLETE",
            "remit_time": "2025-01-13 01:45:35"
        }
    ]
}