Endpoint : Nack

Endpoint : Nack

Nack

The NACK transaction is used to indicate to PayFacto host to perform a reversal of a previously approved transaction. \\
The NACK transaction must be sent within 3 minutes otherwise the automatic reversal process will take place on PayFacto host.
The NACK result can be “True” or “false”.

Request

FieldMandatory?
CompanyNumberY
MerchantNumberY
TransactionNumberY
Response
FieldMandatory?
returnCodeY

    • Related Articles

    • PayFacto API - v1.0 - POST /v1/recur/nack

      POST /v1/recur/nack Recurring — Nack Declines a CVV or AVS verification result from a recurring session and triggers deletion of the associated token. Use this endpoint when your application determines that the CVV or AVS result from a prior ...

    • Endpoint : Recurring - Nack

      This transaction used to decline the CVV or AVS result and have the token deleted. Request Field Mandatory? CompanyNumber Y MerchantNumber Y ID Y Response Field Mandatory? returnCode Y

    • Endpoint : Redirect - Get Response

      Upon a successful redirection to the merchant success or failure URL, you must used this transaction to get the result of the payment transaction. You must issue a ACK or NACK to accept or refuse the transaction. Timing See the ACK transaction ...

    • PayFacto API - v1.0 - POST /v1/standaloneCompletion

      POST /v1/standaloneCompletion Standalone Completion Sends a Pre-Authorization Completion to any properly configured Semi-Integrated terminal. The target terminal can be the one where the original Pre-Authorization was performed, or any other terminal ...

    • PayFacto API - v1.0 - POST /v1/redirect/CreatePreAuthSession

      POST /v1/redirect/CreatePreAuthSession Redirect — Create Preauth Session Creates a secure session on the PayFacto network for a hosted pre-authorization flow. Returns a secureID valid for 15 minutes that is embedded in the browser redirect URL to ...