Mobile Payments iOS Releases

Build 1.1.12

Released 14 December 2021

❗️

Breaking Change

Stripe users need to add locations to their Stripe dashboard before upgrading their iOS mobile devices to the latest version. If the locations are not added first, users will be unable to connect to a Stripe card reader.

:rocket: Enhancements:

  • The iOS Mobile Payment app release includes updates to meet the new Stripe Terminal mobile SDKs version 2.0.0 requirements. To assist users and meet the locations requirement of the new SDK, Blackthorn has added the ability to add a device location to a reader. Users will see a new field on the reader screen and can now select a location that was previously created in their Stripe dashboard. These changes do not impact the payment functionality of the app.

  • When a user selects a UK Payment Gateway while using the iOS Mobile Payments, the GBP currency is automatically selected. The accepted Payment Methods are "Cash" and "Card".

Build 1.1.11

Released 10 May 2021

:rocket: Enhancements:

  • Added: A Payment Gateway selector on the Tokenize Card screen now that multiple provider options are available.

  • Added: A validation to inform users when the Payment Gateway selected is not configured properly.

  • Added: Updated the messaging when the location permission is disabled for the Mobile Payments app. This will inform users why they are unable to use the card reader and allow them to update their app settings.

:bug: Bug Fixes:

  • Resolved: When Postal Code was added during Transaction capture with manual card payments the value wasn't being added to the resulting Payment Method. Now users will see Postal Code populated on the Payment Method created in Salesforce.

Build 1.1.9

Released 5 Apr 2021

  • Restored the ability to send email receipts for ACH Transactions.

Build 1.1.8

Released 29 Mar 2021

:rocket: Enhancements:

  • Added the ability to capture Authorize.net credit card payments using manual card entry.

  • Added the ability to capture Authorize.net ACH payments.

  • Removed the ability to send email receipts for ACH transactions since they result in a "Pending" Payment Status This should be a more intuitive user experience.

  • In order to match the Android Mobile Payments app UI, we added a Postal code field to manual credit card entries.

  • Check21 Users: We added edge detection to the check capture feature. This will prevent blurry image capture.

📘

Authorize.net Note

The ability to add related Accounts and Contacts to an Authorize.net Transaction will be in an upcoming release.


Build 1.1.6

Released 28 Jan 2021

:rocket: Enhancements:

  • Updated the iOS App Store app listing to include a more detailed description and screenshots of the app.

Build 1.1.5

Released 15 Dec 2020

:rocket: Enhancements:

  • Added the platform name to the version data that appears in the Mobile App Version field on the Transaction. This will further allow users to troubleshoot items by identifying from which platform a Transaction originated.

  • The field labeled Mobile App Version will now populate a value for all types of Payment Methods not just those associated with Stripe.

:bug: Bug Fixes:

  • Resolved: When the iPad was oriented to the landscape position the Return to Salesforce button was moving outside of the visible screen.

  • Resolved: If users were on a Payments package that didn't include all of the new field references there was an error displaying. Logic has been put in place to determine what Payments package the Mobile Payments user has installed.


Build 1.1.4

Released 23 Nov 2020

:rocket: Enhancements:

  • The Mobile Payments app now includes better error handling during token expiration.

  • Added an About page so users can view the Mobile Payments app version from the app rather than the App Store.

  • Added Mobile App Version labels for use inside of Salesforce. You can now add a field Mobile App Version to your Transaction to see what Mobile App version was used to create the record.

  • Added the ability to update the card reader firmware from the Mobile Payments app. Read more here.

  • Added messaging to the Reader page to let users know that their card reader firmware has the latest update.

:bug: Bug Fixes:

  • Resolved: A bug where the Scanned Amount field wasn't always clickable in landscape view on iPad.

  • Resolved: An error stating 'No such payment_intent' that was being produced when a user created multiple Transactions using more than one Payment Gateway.

  • Resolved: An instance where an OK button was not clickable.

  • Resolved: Frozen Support page elements. The user can now navigate through the Support page.


Build 1.1.3

Released 15 Oct 2020

:rocket: Enhancements:

  • Added a validation to verify if Require Existing Transaction for Mobile is enabled in Salesforce.
  • Check 21 Customers: Additional validations for check and money order processing.
    • Routing Number must be exactly 9 digits and not contain spaces/symbols.
    • Acceptable value lengths for Account Number include 4-19 digits and no spaces/symbols.

Build 1.1.1

Released 2 Oct 2020

:rocket: Enhancements:

  • Added Contact and Account lookup fields on the "Mobile Payments" home screen.

  • Provided a Tokenize Card option to tokenize credit card and associate to Contact and/or Account via lookup fields.

  • Incorporated the Blackthorn brand update with new colors and logo.

  • Added "Money Order" as a picklist value on the Accepted Payment Methods fields on the Payment Gateway and Transaction objects.

  • Check 21 Customers: Added a rectangle to image capture for the check payment method.

  • Check 21 Customers: Devices now have the ability to reorient the rectangle when they have been rotated.

  • Check 21 Customers: Added validations to check processing

:bug: Bug Fixes:

  • Implemented a fix for rounding issues that were occurring on some transactions.

Did this page help you?