Accertify plugin

Kill Bill fraud plugin using Accertify.

Release builds are available on Maven Central with coordinates org.kill-bill.billing.plugin.java:accertify-plugin.

Kill Bill compatibility

Requirements

The plugin needs a database. The latest version of the schema can be found here.

Configuration

The following properties are required:

• org.killbill.billing.plugin.accertify.url: your Accertify url
• org.killbill.billing.plugin.accertify.username: your username
• org.killbill.billing.plugin.accertify.password: your password

The following properties are optional:

• org.killbill.billing.plugin.accertify.plugins: names of the payment plugins for which automatic rejection is enabled (separated by comma)
• org.killbill.billing.plugin.accertify.proxyHost: proxy host
• org.killbill.billing.plugin.accertify.proxyPort: proxy port
• org.killbill.billing.plugin.accertify.strictSSL: if false, unverified certificates are trusted

These properties can be specified globally via System Properties or on a per tenant basis:

curl -v \
     -X POST \
     -u admin:password \
     -H 'X-Killbill-ApiKey: bob' \
     -H 'X-Killbill-ApiSecret: lazar' \
     -H 'X-Killbill-CreatedBy: admin' \
     -H 'Content-Type: text/plain' \
     -d 'org.killbill.billing.plugin.accertify.url=XXX
org.killbill.billing.plugin.accertify.username=YYY
org.killbill.billing.plugin.accertify.password=ZZZ' \
     http://127.0.0.1:8080/1.0/kb/tenants/uploadPluginConfig/killbill-accertify

Usage

Accertify

Because your organization will have its own XML schema configured in Accertify, you need to pass relevant data for Accertify via plugin properties. Any property starting with accertify_ will be passed through, with the following naming convention:

• Single keys like accertify_ipAddress are passed as top elements in the <transaction> request element
• Composed keys like accertify_collectionTransaction->billingFirstName are passed as children elements
• Use brackets to create list elements: orderDetails->orderDetail[0]->shippingName

For example, the properties

• accertify_ipAddress=127.0.0.1
• accertify_collectionTransaction->billingFirstName=John
• accertify_orderDetails->orderDetail[0]->shippingName=John Doe

will produce the following XML:

<transactions>
  <transaction>
    <ipAddress>127.0.0.1</ipAddress>
    <collectionTransaction>
      <billingFirstName>John</billingFirstName>
    </collectionTransaction>
    <orderDetails>
      <orderDetail>
        <shippingName>John Doe</shippingName>
      </orderDetail>
    </orderDetails>
  </transaction>
</transactions>

By default, the plugin simply calls Accertify and stores the response. Automatic rejection of the payments needs to be enabled on a per payment plugin basis.

For example, if the plugins killbill-cybersource, killbill-paypal-express and killbill-bitpay are installed and you want to reject only payments going to CyberSource and PayPal, specify:

org.killbill.billing.plugin.accertify.plugins=killbill-cybersource,killbill-paypal-express

Any payment for these plugins for which the assessment is REJECT will be aborted.

Kill Bill

To enable the plugin on a per payment basis, use the controlPluginName query parameter:

curl -v \
     -X POST \
     -u admin:password \
     -H 'X-Killbill-ApiKey: bob' \
     -H 'X-Killbill-ApiSecret: lazar' \
     -H 'X-Killbill-CreatedBy: admin' \
     -H 'Content-Type: application/json' \
     --data-binary '{"transactionType":"AUTHORIZE","amount":"10","currency":"USD"}' \
     "http://127.0.0.1:8080/1.0/kb/accounts/2a55045a-ce1d-4344-942d-b825536328f9/payments?controlPluginName=killbill-accertify"