API Changelog

All notable changes to the GoodFunds Gateway API

Documentation Site

Fixes and improvements to this documentation site (not API changes)

Site update

August 23, 2026
  • Fixed Page content rendering underneath the sidebar navigation on some screen widths
  • Fixed Stylesheet updates not reliably reaching returning visitors due to browser caching

API Version History

v1.7.1

October 23, 2026
  • Changed Level 2 and Level 3 data on Converge credit card gateways is now only sent when Accept Level 2 Processing / Accept Level 3 Processing is on for the gateway account. If a setting is off, the matching object is ignored and your request is not affected. See Level 2 & Level 3 Processing.
  • Changed level2.invoice_number is always sent on card charges, whether or not Level 2 is on. If you don’t send one, the charge_id is used.
  • Added level_data in the charge response (message.charge.level_data) showing whether Level 2 / Level 3 was sent and, if not, the reason. Only included when you sent Level 2 fields or a level3 object.
  • Added Documented level2.order_date, level2.salestax_indicator, level2.bin_override, level3.order_date, level3.indicator, level3.national_tax_indicator, level3.summary_commodity_code, and items[*].tax_indicator, discount_indicator, extended_total and line_total, plus the Level 3 requirements and which values are filled in automatically.
  • Changed Level 3 is now skipped (and the charge still processed) when a required item field is missing or the items don’t add up to amount. Totals now account for item discounts, duty, freight tax, other fees and other tax. Level 3 is not sent on a buffered ccauthorize.
  • Fixed The Visa tax-exempt sales tax indicator (0) was never being sent, and ssl_order_date / ssl_merchant_vat_number could be sent twice when both levels were on. Accented characters in invoice numbers and item descriptions no longer produce invalid XML.
  • Fixed Mastercard-specific tax indicators are now correct on charges made with a stored payment_method_id.
  • Fixed Capture Authorization example: ccprocesspreauthorize takes the transaction_id of the authorization (it was missing from the example) and does not use level2.

v1.7.0

October 14, 2026
  • Added GET /rdc_transactions — pull your completed RDC check records by date, date range, store, or item ID (with paging) so you can confirm or refresh your records at any time. Records match the webhook payload; image links are freshly signed on every call and valid for 24 hours. See RDC Check Scanning.
  • Added error codes 7001–7005 and success code 708 for the RDC resync endpoint

v1.6.0

June 15, 2026
  • Added Vendor disbursement endpoints for ACH vendor payments
  • Changed Error response format for consistency across all endpoints
  • Fixed Issue with payment method deletion not removing tokens
  • Fixed Recurring payment cancellation not updating internal status
  • Deprecated Bank verification service for real-time account validation

v1.5.0

May 1, 2026
  • Added Recurring payment management with enable/disable functionality
  • Added Transaction status check endpoint for ACH returns
  • Changed Authentication moved to request headers only
  • Deprecated Query parameter authentication method

v1.4.0

March 15, 2026
  • Added eCheck payment method storage and processing
  • Added Level 2 and Level 3 data support for credit card transactions
  • Changed Payment method response to include tokenized card details
  • Security Enhanced tokenization for credit card storage

v1.0.0

July 1, 2025
  • Initial release with core payment processing functionality
  • Credit card and eCheck processing
  • Payment method tokenization
  • JSON response format