Knowledge Base / API
עברית

Ask AI

✦ AI answer

Thinking…

Sources

    Preventing Duplicate Transactions When Charging Tokens

     For developers working with token charging 

    We recommend passing an additional parameter to prevent duplicate transactions 

    The parameter name is
    ExternalUniqTranId

    Pass the transaction's unique identifier from your system. If we receive the same identifier again, the system will return a duplicate transaction error and will not charge the transaction.

    A string of up to 25 characters. (We recommend using an incrementing sequential number.)

    According to the article: Step 3 - Charging a token / placing a hold / charging credit card details through a direct interface (Do Transaction)

    Note*
    - For developers working with threads, we recommend waiting a few seconds to receive a response before sending the request again. This prevents requests from being sent rapidly in parallel before the server has finished processing the first one. The usual response time is 1 second, but it may take up to 7 seconds in the event of delays in the transaction with the credit card companies.

     

    The unique identifier remains valid until the system returns a response indicating that a valid response code has been received from the credit card companies.
    These response codes include codes for >> charge (code 0), J2 verification (code 701), and J5 authorization (code 700).

     

     

    What does the “duplicate transaction” error mean?

    An attempt was made to charge a token without passing a unique reference parameter. Check this with the developer.
     
     
     
     


     

    Was this article helpful?