January 2023 - Version 5.91

Once the updates listed below have been reviewed, please follow the upgrade instructions to upgrade your Payments application.

Upgrade Instructions

Bug Fix

• Users can now create a new Payment Method and successfully complete a Transaction when using Blackthorn APIs with web forms and an Authorize.net Payment Gateway.

Enhancements

• The current Payments package will be installed when a user installs PayLink from the Blackthorn | Payments Setup Wizard tab.
• There is a new custom setting in Blackthorn Pay – Trigger Setting: Enable Auth Trans Rollup on WorkOrder.
  • If a Transaction is captured for an amount less than the Balance Due on the Work Order, a new Transaction is automatically created with an amount equal to the difference between the first charge and the original amount due.
  • This automation will happen when a Transaction is authorized for less than the Balance Due and when the custom setting in Blackthorn Pay -- Trigger Setting, Enable Auth Trans Rollup on WorkOrder = "True".
  • The Balance Due and Balance Paid fields on a Work Order will update automatically when a Transaction with an amount less than the Balance Due on the Work Order is authorized. This change allows these fields to be used with authorized charges.

Field Service Lightning (FSL)

• A new lookup field, Payment Method, was added to the Work Order object. The new field allows users to add a Payment Method to a Work Order in the Field Service Mobile extension package.
  NOTE: Users must have the Blackthorn | Payments FSL and Blackthorn | Payments (User) permission set to access the field.

  • Field Label: Payment Method
    • API Name: Payment_Method__c
    • Data Type: Lookup

• An FSL user can add and authorize a payment or add a new Payment Method while connected to a Spreedly Payment Gateway. The authorized Transaction or Payment Method will be associated with an FSL Work Order to be used later.
  To perform these tasks, two new fields -- Mobile Add Card and Mobile Authorize -- have been added to the Work Order object. The fields store links that launch the Mobile Payments app and take the user directly to the correct screen to complete the selected action. Both fields include the Blackthorn | Payments FSL permission set with Read Access = “True”.

  • Field Label: Mobile Add Card
    • API Name: Mobile_AddCard__c
    • Purpose: Contains the URL that will launch the Mobile Payments app directly to the add card screen.
  • Field Label: Mobile Authorize
    • API Name: Mobile_Auth__c
    • Purpose: Contains the URL that will launch the Mobile Payments app directly to the authorize screen.

• An FSL user can authorize a payment using an existing Cybersource Payment Method while connected to a Spreedly gateway. This will associate the authorized Transaction with an FSL Work Order that can be charged later.

Spreedly with Cybersource

• When using a Cybersource gateway connected via Spreedly to make a purchase or authorization, information in the Spreedly/Cybersource fields will be mapped to the following new fields on the Transaction object.

  • Field Label: Authorization Code
    • API Name: bt_stripe_Authorization_Code__c
    • Data Type: Text(255)
  • Field Label: Reconciliation Id
    • API Name: bt_stripe_Reconciliation_Id__c
    • Data Type: Text(255)

• Users can authorize a Transaction in Spreedly and then process the payment at a later time. A successfully authorized Transaction will have Payment Status = “Authorized”.

• A user can predefine up to 20 fields to be passed as Merchant Defined Data from Salesforce to Spreedly/Cybersource so the data will be visible in Cybersource.

• A user can send an authorization request via PayLink (with Spreedly connected to Cybersource) to a customer so the customer can authorize the Transaction amount on the entered Payment Method.

AuthLink

• Users can now send an authorization link (AuthLink) to customers to authorize the amount of a Transaction that was charged to the customer's Payment Method.

  • The AuthLink will be created and stored in the Transaction record after the Transaction is completed.
  • If an existing AuthLink is deleted and the record is saved, a new AuthLink will be generated.
  • The AuthLink will be generated at the same time as the PayLink.
  • Access to the AuthLink field requires the Blackthorn | Payments (User) permission set.
  • Field Information
    • Field Label: AuthLink
    • API Name: AuthLink__c
    • Type: URL(255)

• When a user authorizes a payment via AuthLink using a Spreedly Payment Gateway, the Transaction’s Payment Status = “Authorized”.

• When a user authorizes a payment via AuthLink using an Authorize.net Payment Gateway, the Transaction’s Payment Status = “Authorized”.

• A user can send an AuthLink request via a Stripe Payment Gateway to a customer so the customer can authorize the Transaction amount entered on the Payment Method. Once the request is authorized, the Payment Status = "Authorized".

Mobile Payments Android Release

Build - 1.11.1

Released 20 December 2022

Bug Fix

• Updates to timeouts have been made to ensure Android Mobile Payments app users can log in and log out without experiencing periodic app crashes and successfully complete a payment.

Enhancements

• Users can now create and authorize new Payment Methods using a Spreedly Payment Gateway via the Mobile Payments app.

• When a Spreedly/Cybersource Payment Gateway is used to enter a Payment Method on the Mobile Payments app, the First name and Last name fields on the credit card screen are now visible and required.

• To create a new Payment Method with a Spreedly Payment Gateway with Cybersource in the Android Mobile Payments app, users must complete the following billing address fields. These fields will map to the Billing Information fields located on the Payment Method object.

  • Street (Field API Name: bt_stripe__Billing_Street__c)
  • City (Field API Name: bt_stripe__Billing_City__c)
  • State (Field API Name: bt_stripe__Billing_State__c)
  • Postal Code (Field API Name: bt_stripe__Billing_Postal_Code__c)
  • Country (Field API Name: bt_stripe__Billing_Country__c)

• A customer’s billing address information will be captured correctly in the Mobile Payments app and populated properly in the Cybersource dashboard.

• Users can now click a link that will take them directly to the payment screen on the Android Mobile Payments app. To set up this feature, create a new Transaction with the following settings.

  • Record Type = “Charge”
  • Mobile Skip Intro Screen = “Yes”
  • In the Accepted Payments Methods, move “Card (Typed)” to the Chosen column.

• On a Transaction, two new fields, containing deeplinks to the Android Mobile Payments app, have been added. These links will authorize and ONLY tokenize a new Payment Method.

  • Mobile Authorize = authorize screen
  • Mobile Add Card = tokenized new card screen

• When using the Android Mobile Payments app, users can now turn off the send receipt screen after authorizing or capturing a Transaction by enabling the new Custom Setting “Skip Receipt Screen”. This can be found under Setup > Custom Settings > Blackthorn Payments | Mobile Settings > Manage.

  • If Skip Receipt Screen = "True", then the last screen will not show the option to send a receipt.
  • If Skip Receipt Screen = "False", then the last screen will show the option to send a receipt.
  • Field Information
    • Field Label: Skip Receipt Screen
    • API Name: bt_stripe_Skip_Receipt_Screen__c
    • Data Type: Checkbox

If you have any questions about this or need help with testing, please don't hesitate to reach out to Blackthorn Support.