Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Fee rule conditions now offer an “either” or “all” option to better define the rules that apply for fees.

  • Business fee rule has been added to charge additional fees exclusively for business credit cards with a valid BIN and all fields titled business-card-credit have been renamed to Business BIN for better visibility.

  • Payments History page sorting default has been updated to automatically display listings by Merchant Payment ID.

  • Transactions are now searchable in the portal’s global search function using customer discretionary data.

  • Merchant profile page loading time has been drastically reduced - estimated load time is 3 seconds.

  • Account Balance Detail report added to datalake to drastically reduce generation time.

...

  • Added tmxSessionId parameter to transaction schema in API documentation to utilize our ThreatMetrix integration.

  • Added toggle added for online transaction processing via VCORE to HTTP methods.

  • Added a new ISO header and base64 prefix for encoding VCORE transactions for HTTP method processing.

  • Added new endpoints for VCORE to HTTP method to test instead of VCORE sockets.

  • Added batch dates to VCORE batch translator, assigned to that current date.

  • Added template variables for Merchants approved for onboarding with Reserve.

  • Added Google Pay API key rotation for the integration to add additional security. Added enhancements to support upgrades for customers from Pushy Pro to Pushy Enterprise.

Resolved issues

  • Issue resolved where disbursements would partially reverse.

  • Issue resolved where creating a statement withdrawal via debit would reject and return.

  • Issue resolved where some merchant batch jobs would return multiple transactions; some processed, others not.

  • Issue resolved where delay of eCheck funding (for clearance of payment funds) would not function as expected and instantly clear funds even for accounts without the necessary balance.

  • Issue resolved where Chargeback.opened webhook would not properly alert the intended addressee.

...