Package Updates

Major, Minor, Patch, and Build updates

We update our Payments package often with new features and bug fixes. You can always get the latest stable version of the Payments package from the AppExchange.

Package Version Upgrade Path

Sometimes we remove code or metadata from our package that requires a defined upgrade path. If you receive an error when upgrading our Package and you have an old package version, follow these instructions:

Package Version 4.31 or earlier: First upgrade Payments to this package version in Production or Sandbox. Then upgrade to our lastest package version using the link at the top of this page.

Package Version 2.89 or earlier: Follow these instructions

Version 4.127 Coming Soon!

:new+: New Features :new+:

  • Users will now be able to allocate funds from one transaction to the multiple line items.

:high-brightness+: Enhancements :high-brightness+: :sunglasses+:

:ant+: Bug Fixes :bug+::beetle+:

  • Non-Gateway refund transactions roll up to the related opportunity.

  • When creating a Subscription, the default payment method from the related payment gateway customer will be used if the Payment Method field is blank.

  • Fixed the failing invoice.created (or payment_succeeded) webhook. These webhook events now successfully create an invoice in Salesforce.

  • Fixed the calendar UI on the Virtual Terminal object.

  • Users can now use valid ACH type Payment Methods in the Virtual Terminal to process transactions.

:dollar+: Stripe Billing :dollar+:

Version 4.125

July 30th, 2019
:thumbsup+: Upgrade Instructions :thumbsup+:

  1. Upgrade your Payments app.

  2. Navigate to the Blackthorn | Payments Admin tab | Click on the "Metadata Updates" tab | Click the "Add Picklist Values" and "Add Payment Fields to Page Layouts" buttons.

Custom Permission Sets

If you are not using our managed permission sets (https://docs.blackthorn.io/docs/payments-permission-sets) you will need to provide read/write access to all the new fields. Navigate to the Payment Gateway, Payment Gateway Customer, Payment Method, and Transaction objects view the list of fields and provide access to the fields that aren't currently checked as read or edit. At a minimum, every field should have read access.

Relabeled objects and fields

With the introduction of Authorize.net and support for more gateways (PayPal in July), we've generalized the naming conventions of non-Stripe specific objects and fields. No API field or object name changes occurred, only labels.

  1. Object: Stripe Customer -> Payment Gateway Customer
  2. Field: "Non-Stripe" is now "Non-Gateway" on Transaction
  3. Fields: "Created In Stripe" is now "Created In Gateway" on Transaction, Payment Method, and Payment Gateway Customer
  4. Buttons: Remove from Stripe buttons are now Remove from Gateway

:new+: New Features :new+:

Stripe Billing
Ability to auto-generate invoices and invoice lines for any subscription period, including upgrade, downgrade, prorate, and credit scenarios. Bi-direction integration, including create, update, and delete, of subscriptions, plans, tiers, usage, and invoices with Stripe Billing.

  • Over 63+ development tickets added to date.

Authorize.net
With Authorize.net, we support over 20 processors. The list of all supported processors is here. Authorize.net can be used with the Virtual Terminal, PayLink, Classic/Lightning UI, and REST API.

:small-blue-diamond+: :diamond-shape+: Upcoming features for August 2019 :diamond-shape+: :small-blue-diamond+:

:high-brightness+: Enhancements :high-brightness+: :sunglasses+:

:ant+: Bug Fixes :bug+::beetle+:

  • Historical Sync for Stripe Customers and Payment Methods - No Stripe Customers or Payment Methods were syncing over.

  • Payment Method with 100+ related Transactions - When you tried to refund or create a new charge, a "loop" exception error would be thrown.

  • The Amount To Pay feature with DocumentLink was not working with multiple transactions related to the Sales Document.

  • DocumentLink was not showing images in the rich text fields.

  • Refund Transactions can be updated (ie. updating the description field) without a second call to Stripe being initiated. Additional calls can cause potential duplicate refunds.

  • The payment status for a "Partially Refunded" Transaction will stays as is after all the webhook events process.

  • Unsupported webhook types will be automatically set to "Processed". This lowers the batch size and process time.

  • Generated transactions now automatically relate to the parent object record (ie. Opportunity) within a recurring Payment Schedule.

  • On create, setting a Payment Method as the default doesn’t duplicate the Payment Method record.

  • If a recurring Payment is scheduled on a certain date that other months don't have (ie. 29, 30, 31) that month will use its last date (ie 28, 29, 30).

  • The parent object's summary fields (ie. Opportunity) now update when transactions are automatically processed.

  • The Refund button the Transaction record in Salesforce Mobile is enabled.

  • Fixed error when running the "Re-calculate Account Revenue Values" from the payments admin tab. Previously it was attempting to create a new stripe customer.

  • Removed the Order lookup from Sales Document which was failing the upgrade installs. It can be enabled through the 'Enable Order to Invoice' button. Navigate to the Blackthorn |Payments Admin tab, 'Metadata Updates', then click Enable Order to Invoicebutton.

    • When creating a stripe customer from the account, the first related contact on the account will be marked as Primary Stripe Customer.
    • When creating a stripe customer from the account, the first related contact on the account will be marked as Primary Stripe Customer.

Version 4.98

:thumbsup+: Upgrade Instructions :thumbsup+:

  1. Upgrade your Payments app.

  2. Navigate to the Blackthorn | Payments Admin tab | Click on the "Metadata Updates" tab | Click the "Add Picklist Values" and "Add Payment Fields to Page Layouts" buttons.

:high-brightness+: Enhancements :high-brightness+: :sunglasses+:

:new+: New Features :new+:

  • Webhook Signatures - Webhook signatures include additional security for webhook event records that are created in Salesforce
  • Stripe Billing - Create Stripe subscriptions, products, plans, and tiers all from Salesforce

:small-blue-diamond+: :diamond-shape+: Upcoming features for June 2019 :diamond-shape+: :small-blue-diamond+:

:ant+: Bug Fixes :bug+::beetle+:

  • Historical Sync for Stripe Customers and Payment Methods - No Stripe Customers or Payment Methods were syncing over.
  • Payment Method with 100+ related Transactions - When you tried to refund or create a new charge, a "loop" exception error would be thrown.
  • The Amount To Pay feature with DocumentLink was not working with multiple transactions related to the Sales Document.
  • DocumentLink was not showing images in the rich text fields.
  • Refund Transactions can be updated (ie. updating the description field) without a second call to Stripe being initiated. Additional calls can cause potential duplicate refunds.
  • The payment status for a "Partially Refunded" Transaction will stays as is after all the webhook events process.
  • Unsupported webhook types will be automatically set to "Processed". This lowers the batch size and process time.

Version 4.77

  • Subscription update support
  • Push to Stripe checkboxes on Plan and Subscriptions
  • Opportunity Start Date (Subscription mapping)
  • Post install bug fixed
  • Delete coupons supported
  • Account based coupons supported
  • Subscription Item lookup to Account
  • Tax rollup rounding

Version 4.72

  • Stripe Coupons MVP
  • Webhooks sets Transaction source This feature requires that after upgrading, navigate to the Blackthorn | Payments Settings tab and click the Add Picklist Values button to deploy 2 new values to the field: Transaction.Source of Webhook and Sync.
  • Tax Rounding problem
  • Invoices related to Customer Account/Contact
  • Push Plan to Stripe checkbox

Version 4.71

  • Default Payment Gateway bug
  • Line Item sort order update fixed
  • Plan currency mapping on Sync

Version 4.70

  • 'Flipping transaction status on refund' bug fixed
  • Opportunity Product validations
  • Invoice push (Sales Document) from Salesforce
  • Transaction Statement Descriptor property mapped

Version 4.69 - Not for customers (not publicly available), technical release

  • Invoice push MVP
  • Product type field on Opportunity
  • Protection against double-processing Transactions in batch runs

Version 4.68

  • When syncing Stripe Products, zero-dollar price entry is created for new Products

Version 4.67

  • Added a new Lightning Flow Component that allows users to enter and charge a card
  • Log the results of the Setup Wizard - Permission Set Assignments to the browser console to make debugging any assignment issues easier for customers
  • Refactored the Setup Wizard - PayLink Install step to avoid callout timeouts
  • Improved console error logging for Virtual Terminal

Version 4.65

  • Auth.net support implemented (hidden)
  • Stripe Radar support implemented

Version 4.63

  • Added tab for Virtual Terminal and enabled it to work in Salesforce mobile
  • Fixed filter logic on Relationship step in the Setup Wizard
  • Fixed bug with parent transaction rollups
  • Added app fee support for mobile manually entered cards and ach
  • Stripe Billing beta!

Version 4.61

  • Added Lightning Actions to Add Card from Account records and Charge Card from a Payment Method record. These can be used in the Lightning desktop and on the Salesforce mobile app.
  • Added better exception handling in code when Payment Method trigger code updates the Account or Contact record. Now the error is handled, logged as a Blackthorn Log record and the Payment Method update completes successfully. This is useful for customers with sharing rules for Accounts and Contacts.
  • Fixed Webhook bug that was setting the wrong Record Type on ACH Payment Methods

Version 4.60

  • Added the Virtual Terminal to the Sales Document Lightning page
  • Added logic to the Schedule Recommended Payment Jobs (on the Payment Settings tab) that will un-schedule old and unused jobs
  • The Currency field on Sales Document defaults to USD and is no longer required

Version 4.59

  • Fixed minimum amount validation to exclude Payout Transactions which can be negative
  • Updated the Non-Stripe Transaction trigger to work for inserts and updates
  • Changed the Stripe Connect Get Balance batch job to only if Stripe Connect is enabled
  • Updated query to only process Connected Accounts with a Connected Account Id when running the Get Balance batch job

Version 4.58

  • Fixed the pre-population logic on the Virtual Terminal - Add Payment Method page

Version 4.56

  • Updated Stripe query API call to return 100 records at a time for Payout Balance processing
  • Updated the Setup Wizard - Relationships page to be faster and to sort object names correctly
  • Add validations to the (Promo) Code object for Valid From/Through Dates, that only Discount Amount or Percent is populated - not both and that the Code Name is unique in the system

Version 4.54

  • Updated logic for refunding a Authorized Transaction when using Refund button. Now it will update the Payment Status to Uncaptured instead of creating a Refund Transaction. This is same behavior as when Stripe releases an Authorized transaction after 7 days.

Version 4.53

Version 4.52

Version 4.43

Version 4.32

Version 4.9

Package Updates


Major, Minor, Patch, and Build updates

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.