# Server CallBack / URL Notification Credit Card

Faspay systems provide callback server / URL notification credit card that runs automatically, which serves to notify the results of transaction / transaction status. Any changes in the transaction status faspay server, then automatically the status of the last transaction will also be communicated to the merchant server consistently.

If the merchant's transaction status changes, for example: merchant went into administration portal faspay system to change the status of the credit card transaction Authorize status to the status of a transaction with the capture or sales status (success) into the Void / refund. Faspay server then automatically sends information (HTTPS POST) changes the status to the merchant server via the URL notification which gives a chance to the administration portal faspay

<div align="center"><img src="/files/-MM0Zr2nR9esos5C4pKf" alt="Flow Server Callback"></div>

Here is a response from faspay parameters that will be sent to the merchant server:

{% tabs %}
{% tab title="Request" %}

<table><thead><tr><th width="196">Parameter</th><th width="134">Data Type</th><th width="89" align="center">M/O/C</th><th>Description</th></tr></thead><tbody><tr><td>payment_method</td><td>Varchar(1)</td><td align="center">M</td><td>Indicates the payment mode used for this transaction.</td></tr><tr><td>merchantid</td><td>Varchar (30)</td><td align="center">M</td><td>Your Faspay e-Payment Merchant ID</td></tr><tr><td>merchant_tranid</td><td>Varchar(100)</td><td align="center">M</td><td>Merchant’s own assigned transaction id as passed in from the request.</td></tr><tr><td>err_code</td><td>Varchar(10)</td><td align="center">M</td><td>Error Code returns from Faspay e-Payment. If transaction is successful, this value will be 0. Any other value than 0 will indicate that the transaction is not successful.</td></tr><tr><td>err_desc</td><td>Varchar(250)</td><td align="center">M</td><td>Error description from Faspay e-Payment based on the ERR_CODE.</td></tr><tr><td>usr_code</td><td>Varchar(4)</td><td align="center">C</td><td>User Code returns from Faspay e-Payment. A user code will be used to indicate the appropriate action to be taken by shopper according to different bank response code obtained. In the case of pending status, this value is will an empty value</td></tr><tr><td>usr_msg</td><td>Varchar(200)</td><td align="center">C</td><td>User Message returns from Faspay e-Payment. A user message will be used to indicate the appropriate action to be taken by shopper according to different bank response code obtained. In the case of pending status, this value is will an empty value</td></tr><tr><td>txn_status</td><td>Varchar(3)</td><td align="center">M</td><td><p>Transaction status from Faspay e-Payment. Please refer to Appendix B for full list of transaction status. </p><p>A – Authorized </p><p>S – Sales </p><p>F – Not approved </p><p>E – Error </p><p>B – Blocked </p><p>RC – Reconfirm </p><p>N – Pending </p><p>I – Incomplete </p><p>This value must be stored and it’s the indication whether the transaction is successful, declined or error.</p></td></tr><tr><td>custname</td><td>Varchar(120)</td><td align="center">C</td><td>Shopper’s name. In the event of error, this field may be empty.</td></tr><tr><td>description</td><td>Varchar(100)</td><td align="center">O</td><td>Transaction description as passed in from the request.</td></tr><tr><td>eui</td><td>Varchar(3)</td><td align="center">M</td><td>End User Indicator (EUI) is use to help merchant determine the response to display on merchant return URL. Please refer to Appendix section for further details. SUC = Success RTY = Retry/Failed ALT = Alert NA = Not Applicable</td></tr><tr><td>currencycode</td><td>Varchar(3)</td><td align="center">M</td><td>Indicate the currency of this transaction. E.g. MYR, USD, SGD etc.</td></tr><tr><td>amount</td><td>Numeric(10)</td><td align="center">M</td><td>Transaction amount as passed in from the request.</td></tr><tr><td>signature</td><td>Varchar(40)</td><td align="center">M</td><td>Transaction signature of response for data integrity checking. Refer to Chapter 5 Transaction Signature for details.</td></tr><tr><td>transactionid</td><td>Integer</td><td align="center">M</td><td>Faspay e-Payment assigned transaction id if the transaction was stored. This value must be stored and used as reference value to retrieve the transaction from Faspay e-Payment. In the event that if the request parameters are invalid, the transaction is rejected and not stored, this value will be 0.</td></tr><tr><td>trandate</td><td>Varchar (19)</td><td align="center">C</td><td>Transaction date of when transaction is submitted to Faspay e-Payment. Date format in ‘DD-MM-YYYY hh:mm:ss’ e.g. 24-05-2006 08:24:23 In the event of error, this field may be empty.</td></tr><tr><td>transactiontype</td><td>Varchar(2)</td><td align="center">M</td><td>Return transaction type corresponding to the original request</td></tr></tbody></table>
{% endtab %}

{% tab title="Sample Request" %}

```php
Array
(
    [PAYMENT_METHOD] => 1
    [MERCHANTID] => sophia_store
    [MERCHANT_TRANID] => 20160609100148
    [ERR_CODE] => 0
    [ERR_DESC] => No error
    [USR_CODE] => 101
    [USR_MSG] => Transaction approved
    [TXN_STATUS] => S
    [CUSTNAME] => John Doe
    [DESCRIPTION] => Tiket VIP - Yellow Claw
    [CURRENCYCODE] => IDR
    [AMOUNT] => 10000.00
    [SIGNATURE] => 967344E96F2D448A84164EA316B0A1FFDC0B6921
    [EUI] => SUC
    [TRANSACTIONID] => 23061
    [TRANSACTIONTYPE] => 1
    [MPARAM1] => 
    [MPARAM2] => 
    [ACQUIRER_ID] => mandiri
    [TRANDATE] => 09-06-2016 10:02:23
    [IS_BLACKLISTED] => No
    [FRAUDRISKLEVEL] => 2
    [FRAUDRISKSCORE] => 48.79
    [POINT_USED] => 0
    [POINT_AMOUNT] => 0.00
    [PAYMENT_AMOUNT] => 0.00
    [POINT_BALANCE] => null
    [EXCEED_HIGH_RISK] => No
    [CARDTYPE] => V
    [CARD_NO_PARTIAL] => 413718xxxxxx3783
    [CARDNAME] => tes
    [is_on_us] => Yes
    [ACQUIRER_BANK] => 016
    [WHITELIST_CARD] => No
    [BANK_RES_CODE] => 00
    [BANK_RES_MSG] => APPROVED OR COMPLETED
    [AUTH_ID] => 657399
    [BANK_REFERENCE] => 12902
    [INSTALLMENT_CODE] => 
    [INSTALLMENT_TERM] => 0
    [INSTALLMENT_MONTHLY] => 0.00
    [INSTALLMENT_LAST] => 0.00
    [popupProceed] => Click here to proceed  
)
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.faspay.co.id/merchant-integration/api-reference-1/credit-card-transaction/additional-api-integration/server-callback-url-notification-credit-card.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
