> ## Documentation Index
> Fetch the complete documentation index at: https://apidocs.synchpay.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> SynchPay's changelog, announcements, and new API features.

## API Changes

<Update label="April 27, 2026" description="v0.4.11">
  ## Webhook signatures, redesigned onboarding, and card payment polish

  ### New features

  * **Signed webhooks** — SynchPay now signs webhook payloads with an HMAC-SHA256 signature when a secret is configured for your endpoint. Each delivery includes an `X-HMAC-Signature` header in the form `sha256=<hex>` so your backend can verify that the request came from SynchPay and was not tampered with. Contact support to enable a signing secret for your [webhook endpoint](/synchpay/webhooks/intro).
  * **Redesigned mobile onboarding** — New users opening the SynchPay mobile app now see a refreshed introduction with four slides explaining one-tap payments, bank-to-bank transfers, medical bill reimbursement, and fast settlement, followed by a new boot splash. The change applies to both iOS and Android.

  ### Updates

  * **Smoother in-app card payments** — After completing an [in-app card payment](/synchpay/card-payment) in the browser, payers are now routed back to the SynchPay mobile app's success screen automatically. The action button on the card payment screen is also relabeled from "Open browser again" to "Continue to card payment" for clarity.
</Update>

<Update label="April 20, 2026" description="v0.4.10">
  ## Card payment processing and API update

  ### Updates

  * **New card payment processor** — In-app card payments are now powered by a new payment processor, improving reliability and checkout speed. The payer experience is unchanged — card payments still appear as a payment method alongside bank transfers when enabled for a company. See [card payments](/synchpay/card-payment) for details.
  * **External card payment API change** — The [register external card payment](/synchpay/card-payment#registering-an-external-card-payment) endpoint (`POST /cardpayment`) now uses a `MerchantId` field to identify the merchant. The previous `CompanyId` and `CompanyReferenceId` fields have been removed. Update your integration to pass `MerchantId` instead.
</Update>

<Update label="April 13, 2026" description="v0.4.9">
  ## In-app card payments and invoice fix

  ### New features

  * **In-app credit card payments** — Payers can now choose to pay with a credit card directly in the SynchPay mobile app. When a payment request supports card payments, payers see a payment method selection screen with options to pay by credit card or bank account. Card transactions are marked with a card icon in the transaction list. See [card payments](/synchpay/card-payment) for details.

  ### Bug fixes

  * Fixed an issue where invoice payments could fail due to an unnecessary account balance check.
</Update>

<Update label="April 8, 2026" description="v0.4.8">
  ## Card payment registration

  ### New features

  * **Card payment endpoint** — You can now [register external card payments](/synchpay/card-payment) in SynchPay using the new `POST /cardpayment` endpoint. This lets you record card transactions processed by an external terminal or POS system so they appear alongside your account-to-account payments. Payers receive an SMS (and optional email) confirmation when a card payment is registered.
</Update>

<Update label="April 6, 2026" description="v0.4.7">
  ## Deep links, iPad support, and payment API improvements

  ### New features

  * **Recurring payment deep links** — Payers can now open recurring payment consent requests directly from a shared link, making it easier to accept or decline a [recurring payment plan](/synchpay/recurring-payment-plans) without navigating through the app.
  * **iPad support** — The SynchPay mobile app is now available on iPad.
  * **CompanyReferenceId on payments** — The [create payment](/synchpay/make-payment) endpoint now accepts an optional `CompanyReferenceId` field as an alternative to `CompanyId`, so you can identify the target company using your own external reference.
  * **Attachment URL support** — You can now pass an attachment URL when [creating a payment request](/synchpay/make-payment). SynchPay automatically downloads and stores the file with the payment.

  ### Bug fixes

  * Fixed an issue where pull-to-refresh could trigger unexpectedly when switching between tabs in the mobile app.
</Update>

<Update label="March 31, 2026" description="v0.4.6">
  ## API validation and new fields

  ### New features

  * **Company reference ID** — The [company registration](/synchpay/register-company) endpoint now requires a `CompanyReferenceId` field, letting you assign your own external identifier to each company at creation time.
  * **Company website** — You can now optionally provide a `WebsiteUrl` when [registering a company](/synchpay/register-company).
  * **ForProfit company type** — `ForProfit` is now an accepted value for the `CompanyType` field during company registration.
  * **Debit auth on payments** — The [create payment](/synchpay/make-payment) endpoint now supports `EnableDebitAuth` and `DebitAuthLimit` fields as alternatives to `EnableAutoPay` / `AutoPayLimit`.

  ### Improvements

  * Stricter input validation across all company registration fields, including email format, phone number format, ZIP code pattern, and state abbreviation checks. Invalid requests now return clear error messages.
  * Owner and employee email addresses are validated for uniqueness during company creation.
</Update>

<Update label="March 29, 2026" description="v0.4.5">
  ## Recurring payments in the mobile app

  Payers can now view, accept, and cancel recurring payment plans directly in the SynchPay mobile app. The Payments tab shows upcoming recurring payments alongside unpaid requests, and payers can manage all active plans from their Profile screen. A new frequency filter helps payers distinguish between one-time, irregular, and subscription payments. See [payer experience in the mobile app](/synchpay/recurring-payment-plans#payer-experience-in-the-mobile-app) for details.
</Update>

<Update label="March 28, 2026" description="v0.4.4">
  ## Unified consent decline action

  The [decline consent](/synchpay/recurring-payment-plans#accept-or-decline-a-consent) endpoint now handles both pending and accepted consents. When a payer declines a `Pending` consent, it moves to `Declined` as before. When a payer declines an `Accepted` consent, it now moves to `Revoked` automatically — no separate revoke action is needed.
</Update>

<Update label="March 28, 2026" description="v0.4.3">
  ## Status field in consent list and filtered results

  The [list consents](/synchpay/recurring-payment-plans#list-consents) endpoint now includes a `Status` field in each consent object, so you can see whether a consent is `Pending` or `Accepted` without fetching each one individually. The endpoint also now filters out consents that are no longer actionable — only `Pending` and `Accepted` consents are returned.
</Update>

<Update label="March 28, 2026" description="v0.4.2">
  ## Company details in consent response

  The [get payment plan consent](/synchpay/recurring-payment-plans#get-a-single-consent) endpoint now returns a `RecipientCompany` object with full company details (name, contact number, email, website, and address) instead of just the company name. This gives payers more context about the company they are authorizing recurring payments for.
</Update>

<Update label="March 23, 2026" description="v0.4.1">
  ## Recurring payment plans API

  Recurring payment plans are now fully available through the API.

  ### New features

  * **Payment plans API** — You can now [create, activate, pause, and cancel recurring payment plans](/synchpay/recurring-payment-plans) entirely through the API. Define the amount, frequency, and start date, then SynchPay automatically generates and processes payments on schedule.
  * **Payer consent flow** — When you add a payer to a plan, they receive a notification and can accept or decline through the app. You can track consent status and manage multiple payers per plan.

  ### Bug fixes

  * Fixed an issue that could prevent recurring payment plans from processing correctly.
</Update>

<Update label="March 2026" description="v0.4">
  ## NexHealth integration, invoicing, and more

  We've shipped several new features and improvements over the past few months.

  ### New features

  * **NexHealth integration** — SynchPay has deepened its integration with [NexHealth](/integrations/dentalPlatforms), allowing dental practices to sync patient payments directly from their practice management software.
  * **Automated invoicing** — Businesses can now generate invoices with PDF documents and automate money movement for invoice billing.
  * **Payment reminders** — You can now send manual payment reminder notifications via SMS, giving you more control over follow-ups on outstanding [payment requests](/synchpay/make-payment).
  * **Same-day autopay** — Scheduled payments set for today are now automatically processed via [autopay](/synchpay/payment-debit-auth), reducing delays for due-date payments.
  * **Recurring payment intervals** — A new recurrence interval field lets you configure flexible recurring payment schedules.

  ### Updates

  * Richer notification content with more payment context for end users.
  * Account number masking is now included in additional API responses for improved security.
  * Enhanced login security with additional OTP verification protections.

  ### Bug fixes

  * Fixed typos and grammatical errors across user-facing text in the mobile app.
  * Resolved an issue with charity donation messaging and receipts.
</Update>

<Update label="October 2025" description="v0.3.0.1">
  ## Minor Improvements

  We've made some subtle improvements to our overall documentation with minimal functional changes.

  * Documented the `AccountNumberMasked` parameter in the [Payment Request Status](/synchpay/webhooks/payment-status) webhook.
</Update>

<Update label="September 2025" tags={["Breaking"]} description="v0.3">
  ## New, Faster Money Movement

  We've upgraded our money movement partner for faster, more certain, and more secure movement. There is one minor breaking change to the API in the [Company Creation](/synchpay/register-company) process.
</Update>

<Update label="July 2025" description="v0.2">
  ## Launching Debit Auth

  We're launching our Debit Auth API. This allows you to check, set, and update the user's authorized debit limit.

  This allows you to effectively mimic a card-on-file experience, as well as implement recurring payments.

  Take a look at our [Debit Auth API Reference](https://apidocs.synchpay.dev/synchpay/payment-debit-auth) for more details.

  ### Other Fixes

  * Clarified the [Register Company](https://apidocs.synchpay.dev/synchpay/register-company) API endpoint.
  * Added [Transaction Report](https://apidocs.synchpay.dev/synchpay/report-transactions) functionality to help with your reconciliation.
</Update>

<Update label="March 2025" description="v0.1">
  ## Hello, World

  Opening our API to the public!

  ### Features

  * Added payment requests.
  * Added refund requests.
  * Added payment status requests.
  * Added payment details requests.
  * Added payment history requests.
  * Added payment methods requests.
  * Added payment methods details requests.
</Update>