- Collect the information about the transactions.
- Create either a
MigrationTransactionobject (for use withTransaction.migrate), or aTransactionobject (for aTransaction.scorerequest).
Transaction.score requests), see the Reporting Real-Time Transaction Information for Fraud Screening section.
After you send data to Vindicia, Vindicia returns a Return object with returnCode and returnString to inform you if the communication with the Vindicia server completed successfully. (Codes for the Return object are modeled after the standard HTTP return codes.) If the call succeeds, you receive a code of 200 and the string OK. returnCode and returnString may be used to interpret errors. See The Return Object in the Vindicia Subscribe SOAP API Reference Guide, for more information.
Be certain to act upon the Return value.
Reporting Real-Time Transactions for Fraud Screening
To report the transaction information in real time and receive a chargeback probability score, call thescore() method on the Transaction object. (Be certain to pass only a single Transaction object to the score() call.) This call not only reports your transaction details to Vindicia but also returns to you a chargeback probability score (also called a risk score).
For the score() call to succeed, your transaction must contain at least the following attributes. If you do not specify any one of them, the call returns a score of -1, which means “no opinion.”
- IP address
- Payment method: Billing address: City
- Payment method: Billing address: State (“district”)
null. If the state is not known or does not exist, set this attribute to Unknown.
- Payment method: Billing address: Country
- Payment method: Billing address: Zip code
None.
- Credit card BIN (the first six digits of the credit-card number)
score() call returns a Return object that describes the success or failure of the call, the chargeback probability (score), and an array of reason codes (scoreCodes) that explain the risk score.
Based on the transaction information provided, the chargeback probability ranges from 0 to 100. A probability of 100 indicates that Subscribe is 100 percent certain that this transaction is fraudulent and will result in a chargeback. The score can also be -1, indicating no opinion from Vindicia; or -2, indicating an error condition. Based on the score, you can decide to either proceed with the transaction (by capturing it) or cancel it.
For more information on and the scoreCodes call, see The Transaction Object in the Vindicia Subscribe SOAP API Reference Guide.
Reporting Activity Information
To combat fraudulent chargebacks, Vindicia uses your records to build an evidentiary record of your customer’s activities, and challenge a chargeback case on your behalf. Usage data, which usually resides in the commerce server on your site, is not mandatory, but can be key in helping win chargeback disputes. Examples of usage data are logins and logouts, visits to certain Web pages, email or phone communications, and shipping confirmations. This data can help counter customer claims that they did not make a specific purchase. Vindicia strongly suggests that you maintain a record of usage data. If you sell digital goods, most of this information data is required by the issuer in case of chargeback disputes. Be sure to report all the events that are significant or relevant, including email or phone communications, and access to or downloads of for-pay content. TheActivity object contains data structures through which you can report the following types of customer activities:
- Logins to a site
- Logouts from a site
- Views, visits, or downloads of a Web resource (URI views)
- Phone contacts with a customer
- Email contacts with a customer
- Fulfillment of an order for physical goods
- Use of quantifiable objects that are meaningful to your business
- Cancellation of a service
- An arbitrary note that contains a maximum of 1,024 characters
Reporting Refund Information
If you process transactions and refunds through Subscribe, you need not report refunds separately to Vindicia. (Note that use of the forward slash character (/) in merchant identifiers is not allowed. See Merchant Identifiers for more information.) Report refunds to Vindicia for transactions processed outside Subscribe:Refund objects, as shown above. For more information, see The Refund Object in the Vindicia Subscribe SOAP API Reference Guide.
Parent topic:Data Reporting to Vindicia
