Review Transactions

Chargeback

Chargeback applies only for credit card transactions and it can be accepted or disputed by the user until the due date. After the chargeback due date passes, the chargeback is accepted by default.

Accept Chargeback

Use this endpoint to accept a specific chargeback for a credit card transaction.

Method: PATCH

Endpoint: {{env}}/api/TransactionChargeback/{{TransactionChargebackId}}/accept

Response

{
  "statusCode": 200,
  "message": "PATCH Request successful.",
  "isError": false,
  "result": "Request completed"
}

INFO

• The TransactionChargebackId information can be retrieved through the Get a specific transaction endpoint.

• If chargeback is not accepted or disputed until the due date, the chargeback will be automatically accepted.

• A chargeback cannot be accepted if it is already accepted or disputed or is past due date.

Dispute Chargeback

Use this endpoint to dispute a specific chargeback for a credit card transaction.

Method: PATCH

Endpoint: {{env}}/api/TransactionChargeback/{{TransactionChargebackId}}/dispute

Response

{
  "statusCode": 200,
  "message": "PATCH Request successful.",
  "isError": false,
  "result": "Request completed"
}

INFO

• The TransactionChargebackId information can be retrieved through the Get a specific transaction endpoint.

• A chargeback cannot be disputed if it is already accepted or disputed or is past due date.

Interac Fraud

Use the following API endpoint to take action on a Interac transaction "Under Review".

Method: PUT

Endpoint: {{env}}/api/transaction/takeaction/{transaction_id}

Payload

{
   "TransactionInReviewActionChosen": "ConfirmedLegitimate"
}

Note

• Upon investigation if the transaction is a fraud or scam, then the transaction is cancelled.

• Upon investigation if the transaction is legitimate, then transaction is completed.

What can trigger an Interac Fraud alert?

• Interac does not share the reason for flagging a transaction for fraud.

• Here are some situations that may trigger a transaction to be in-review for fraud:

  • When the same person attempts multiple transactions on the same day

  • When the email used belongs to a domain that is recently registered

  • When the person attempts to complete the payment using a suspicious browser fingerprint (IP address, browser, device, time-zone)

  • When the person attempts to deposit with multiple bank accounts

Possible Actions

Zūm Rails offers 4 main actions for transactions in review:

Type	Description
ConfirmedLegitimate	Confirm the transaction is legitimate.
PresumedLegitimate	Presume the transaction is legitimate.
ConfirmedFraud	Confirm the transaction is fraud.
Scam	Confirm the transactions is scam.