Back-office donations include store card info transactions and update card info transactions. To ensure compliance for back-office one-off donations, the consuming application must:

• Complete the standard workflow with Blackbaud Checkout
• Pass a valid security token
• Pass the is_offline parameter set to true

These integration steps ensure that back-office donations are compliant with SCA regulations and help reduce malicious card testing.

The security token is a unique token that enables integrating applications to operate in a privileged context. To obtain a security token, you make a request with the security token endpoint.

As with other Payments API endpoints, this security token request should be made server-to-server, and because authentication is performed with BBPS credentials, any transaction with the security token operates in a higher level of trust.

      var transactionData = {
        'key': 'ca01585e-70cb-47b1-bbe2-99040d6bba9d',
        'payment_configuration_id': '703e41ba-3e22-4bee-a70c-37c45752493b',
        'amount': 10.00,
        'client_app_name': 'Blackbaud Checkout Sample Data',
        'security_token': '1e2eccc9-4867-4620-61c9-6ab8488ec7b7',
        'is_offline': true
      };

      Blackbaud_OpenPaymentForm(transactionData);
    

var transactionData = {
  'key': 'ca01585e-70cb-47b1-bbe2-99040d6bba9d',
  'payment_configuration_id': '703e41ba-3e22-4bee-a70c-37c45752493b',
  'amount': 10.00,
  'client_app_name': 'Blackbaud Checkout Sample Data',
  'security_token': '1e2eccc9-4867-4620-61c9-6ab8488ec7b7',
  'is_offline': true
};

Blackbaud_OpenPaymentForm(transactionData);