Merchant Vendors¶

Recurring Retry¶

Each vendor deals with failed recurring donation payments differently. They all retry the charge multiple times on a different schedule as described here.

Braintree will accrue the missed payments and charge for all of them when the card is again accepted. This can lead to a nasty surprise for some of your most valuable donors if their payments fail for a few months and then succeed (for a total that includes the missed months). To avoid billing recurring donors for several months of missed payments at one time, use our custom retry system.

Note that this only applies to recurring credit card donations with Braintree. Recurring donations using ACH Direct Debit are handled by ActionKit directly, and failed payments are never retried. See the ACH Direct Debit Guide for more information.

Additional Information Supported¶

You can also include some additional information with requests to Braintree -- please note that some set up is required first in the Braintree gateway for several of these.

• Email: This will be transferred automatically.
• IP address: There's an instance-wide configuration option. Under Donations Send IP Address is set to False by default. NOTE: You must create the 'customer_ip' custom field in the Braintree gateway prior to enabling the option or ALL donations will fail.
• Custom fields: Inputs on braintree donation pages prefixed with 'braintree' will be submitted as custom fields. Again, the donation will error and fail if a custom field is submitted that has not first been created in the gateway.
• Device data: We've made changes to allow you to take advantage of Braintree's new fraud protection tools, beyond MaxMind. Most groups will not need this, but if you are encountering problems with fraud that you aren't able to reduce using MaxMind, this might be of use to you. You'll need to make some changes to your account settings so if you're interested in finding out more let us know.

For all of the above, because of how donations and recurring donations are structured, the data is attached to the transaction for a one-time donation, but to the customer for a recurring donation.

3D Secure 2.0¶

We now offer support for 3D Secure 2.0 to verify credit card owners who are making a donation on your Braintree donation pages.

To enable this option, create a custom page field called use_3d_secure. Add it to your Braintree donation page and set the value to 1.

Template changes to donate, recurring_update, and recurring_info pages. Please consult the template diffs to ensure your template has the correct code.

We can also configure your instance to require 3D Secure for all pages on a Braintree account. Please contact ActionKit support to do this. (Testing first is a must!)

Note that recurring updates will not use 3D Secure unless the account is configured to use it.

Accept.js¶

As of March 2019, ActionKit is transitioning clients using Authorize.net to their accept.js processing system. Accept.js allows ActionKit to process donations without directly handling credit card details, which is much more secure. We will deprecate the old interface to Authorize.net and all Authorize.net donation pages will be required to use Accept.js.

You can find more details about Accept.js here:

https://developer.authorize.net/api/reference/features/acceptjs.html

{% if pp.use_accept %}
<script src="/resources/ak_authnet_accept.js"></script>
{% authnet_js_libs %}
<script>
$(function() {
    var form = document.querySelector("#act"),
    options = {
            form: form,
            submit: form.querySelector(".ak-submit-button")
    };
    actionkit.authnet.initClient('{{ pp.login }}', '{{ pp.public_key }}', options);
});
</script>
{% endif %}

{% with page.payment_processor_information as pp %}

{% if profile.payment_processor_information.use_accept %}
{% once %}
<script src="/resources/ak_authnet_accept.js"></script>
{% authnet_js_libs %}
<script>
$(function() {
    var form = $("#change_profile_{{ profile.id }}").get(0);
    options = {
            form: form,
            submit: $("#change_profile_{{ profile.id }} .ak-change-submit button").get(0),
    };
    actionkit.authnet.initClient('{{ profile.payment_processor_information.login }}', '{{ profile.payment_processor_information.public_key }}', options);
});
</script>
{% endonce %}
{% endif %}

{% for profile in active %}

Additional Settings¶

We strongly recommend enabling the Transaction Details API in Authorize.net. By default, when Authorize.net processes a recurring donation, they attempt to send that data to ActionKit once and only once. Sometimes the attempt fails and ActionKit never gets a record of the payment. If you enable the API, we’ll also run a nightly server-to-server sync to pick up any missing transactions from the preceding 30 days.

Read how here: http://developer.authorize.net/api/reference/features/transaction_reporting.html

VGS¶

Payflow Pro itself doesn't provide a PCI compliant service, but ActionKit has an integration with VeryGoodSecurity (VGS) to that makes PCI compliant Payflow Pro donations possible.

Support for VGS was added to the built-in Original templateset in August 2021, and use of the VGS proxy is now required for Payflow Pro accounts in ActionKit.

If you've customized your donate.html templates, changes may be necessary before VGS will work on your donation pages. Reach out to ActionKit support for pointers on how to add VGS to your templates.