This article contains sample case creation logic for integrating the Verifi third-party resolution network with Smart Dispute for Issuers.

Sample Case: CREATE (POST)

Request:

POST https://api.cdrn.com/issuers/cases HTTP/1.1

Request Headers:

• Content-Type: application/xml
• Authorization: Basic rYiYzRaaZ9/QYpiQFZADqpkgJfM=
• x-verifi-api-version: 1.0
• x-verifi-issuer: 112233
• X-verifi-signature: V47F2tYLS29MmHPhiR8FyiCny9zO5De3kVSF0RYQHmo=
• X-verifi-timestamp: 2012-03-01T23:09:11Z

Request Body:

<?xml version="1.0" encoding="utf-8"?>

<case xmlns="http://api.issuer.cdrn.com/domain">

<type>DISPUTE</type>

<acquirerReferenceNumber>24692161070000622606414</acquirerReferenceNumber>

<referenceTransactionDate>2012-01-17</referenceTransactionDate>

<referenceTransactionAmount>39.99</referenceTransactionAmount>

<referenceTransactionCurrency>USD</referenceTransactionCurrency>

<number>32838-001</number>

<date>2012-03-01</date>

<amount>39.99</amount>

<currency>USD</currency>

<authorizationCode>387373</authorizationCode>

<reasonCode>75</reasonCode>

<paymentType>VI</paymentType>

<accountNumber>423234xxxxxx3773</accountNumber>

<accountExpirationDate>1502</accountExpirationDate>

<bin>423234</bin>

<lastFour>3773</lastFour>

<networkDescriptor>AAA*HOSTING</networkDescriptor>

<uniqueMerchantIdentifier>8883239090</uniqueMerchantIdentifier>

<generationTimestamp>2012-03-01T10:20:30+00:00</generationTimestamp>

</case>

Response:

HTTP/1.1 202 Accepted

location: https://api.cdrn.com/issuers/cases/12345

x-verifi-call-id: 228384348537

Sample Case: READ (GET)

Request:

GET https://api.cdrn.com/issuers/cases/12345 HTTP/1.1

Request Headers:

• Content-Type: application/xml
• Authorization: Basic rYiYzRaaZ9/QYpiQFZADqpkgJfM=
• x-verifi-api-version: 1.0
• x-verifi-issuer: 112233
• X-verifi-signature: V47F2tYLS29MmHPhiR8FyiCny9zO5De3kVSF0RYQHmo=
• X-verifi-timestamp: 2012-03-01T23:09:11Z

Request Body:

None

Response:

HTTP/1.1 200

x-verifi-call-id: 228384348548

<?xml version="1.0" encoding="utf-8"?>

<case id="12345" xmlns="http://api.issuer.cdrn.com/domain">

<type>DISPUTE</type>

<status>PROCESSING</status>

<acquirerReferenceNumber>24692161070000622606414</acquirerReferenceNumber>

<referenceTransactionDate>2012-01-17</referenceTransactionDate>

<referenceTransactionAmount>25.0</referenceTransactionAmount>

<referenceTransactionCurrency>USD</referenceTransactionCurrency>

<number>32838-001</number>

<date>2012-03-01</date>

<amount>39.99</amount>

<currency>USD</currency>

<authorizationCode>912754</authorizationCode>

<reasonCode>75</reasonCode>

<paymentType>VI</paymentType>

<accountNumber>423234xxxxxx3773</accountNumber>

<accountExpirationDate>0815</accountExpirationDate>

<bin>423234</bin>

<lastFour>3773</lastFour>

<networkDescriptor>AAA*HOSTING</networkDescriptor>

<uniqueMerchantIdentifier>8883239090</uniqueMerchantIdentifier>

<generationTimestamp>2013-07-17T10:24:46+00:00</generationTimestamp>

</case>

Sample Verifi case scenario

Smart Dispute for Issuers contains a sample Verifi case scenario. The scenario consists of the following rules. You can review and modify these rules as necessary.

• Flow rule: CallVerifiDisputeResolutionProcess

  The flow determines the Verifi case status, routing the dispute case processing appropriately.

  Once submitted, the dispute case is processed using the chargeback process.

  • Assessment assignment for a back officer to perform the dispute case using the chargeback process
  • Monitor credit transaction flow to validate the eligibility of auto-closing the dispute case upon finding the right merchant’s credit match transaction
• Flow rule: MonitorCreditTransaction

• SLA Rule: AutoMatchMerchantCrTxSLA

  The SLA rule is configured on the Monitor Credit Transaction assignment to:

  • Wait for specified days
  • Query for credit transaction on Goal, Deadline, and Past deadline dates
    On the Post deadline date, the dispute case is routed to the Exceptions workbasket for a back officer to process the flow.
  • Match the credit transaction performed by the merchant to the card holder using the activity rule.

• Activity Rule: MonitorCreditTransactionSLA

  The activity rule queries the Credit transaction table to find one matching result (step 8), ensuring that the correct transaction is used, based on the filter criteria that is applied using the data transform rule.

• Data transform rule: SetMerchantCrTxnFilterCriteria

  The data transform rule is used to apply filter criteria to query the Credit transaction table to match the credit transaction. The rule needs to be customized based on the use case during implementation.

  The filter criteria includes the following parameters that are used to find matching credit:

  • Transaction date
  • Posted amount
  • Posted currency
  • Merchant number
  • Account number
  • Card number
  • Transaction type

• Report definition Rule: GetMerchantCreditedTransactions

  The report definition rule is used to query the Credit transaction table to match the credit transaction using the above filter criteria. The rule's filter needs customization based on the use case during implementation.

Rules referenced in enabling the simulation feature

• Dynamic system settings: EnableSimulations
• Activity rule: Rule-Connect-.getSimulationActivity
• When rule: @baseclass.IsSimulationEnabled

The following activity rules are configured as simulation activities at Verifi Rest connecter rules:

• Simulate_CreateVerifiCase
• Simulate_ReadSingleVerifiCase
• Simulate_UpdateVerifiCase