New getPaid tokenization setting and bug fixes

This release includes a new tokenization setting for the getPaid endpoint, as well as several bug fixes and enhancements across the web app, API, and embedded components. Here are the highlights:

Web app

Creator updates (beta)

• Removed erroneous console error messages
• Added copy button to color picker values in the editor

UI updates

• Added View Check button to the Bill Details screen for viewing check images
• Made navigation heading improvements
• General icon tweaks and enhancements
• Fixed several issues:
  • Entering digits in Transaction report filters now works as expected
  • Field display on boarding applications
  • User status badge display
  • 404 error when adding payment methods from customer records
  • Date picker logic for operations with start/end dates
  • Pagination in Residuals report
  • Organizations report 500 error

Embedded components

• Fixed an issue that returned a 401 error when a customer tries to make multiple payments

API

New saveIfSuccess option

We’ve added a new option to the /getPaid endpoint that allows you to tokenize and save the payment method on any successfully authorized transaction with a card, device, or ACH payment method.

To tokenize a payment method while making a sale transaction, pass saveIfSuccess: true in the paymentMethod object. The new tokenized payment method will be returned in the response if the transaction is successful. If successful, the request returns the new method’s reference ID as methodReferenceId.

Other API fixes

• Fixed blank Billing & Fees column in exports
• Fixed 500 error when saving previously saved boarding applications
• Fixed Organizations query 500 error