Skip to main content
This page lists dated changes to the Swipelux API. Each entry notes the affected version, the change type, and any action required from integrators. For upgrading an existing integration from an earlier version, see Migrate to v3.

​
Unreleased

Upcoming changes will be listed here before they ship.

​
2026-09-08

Version: v3

​
Changed

  • POST /v3/transfers and transfer reads use checkoutMethod instead of paymentMethod for the card checkout pre-selection, and accept card, apple_pay, google_pay, cash_app, sepa, and blik. The list is open and can grow. paymentMethod is no longer recognized; requests that still send it are treated as if it were omitted. sepa and blik are funding options inside the card checkout, not Swipelux capabilities. See Receive funds.

​
2026-09-07

Version: v3

​
Added

  • POST /v3/transfers accepts an optional paymentMethod of card, apple_pay, or google_pay for card quotes. The hosted checkout opens on the requested method when it is available for the customer and their device, transfer reads echo the request, and the quote’s amounts and fees are unchanged. See Receive funds.

​
2026-08-31

Version: v3

​
Added

  • Requesting a capability for a business with no beneficial owner now creates an intake task to add one instead of failing with a 503. Requests that cannot proceed return 422 beneficial_owner_required with instructions to add an individual related party with declared or at least 25% ownership. See Shareholders, UBOs, and control persons.
  • The merchant panel’s task table now shows each request’s subject and capability scope, so you can see who and what a compliance request covers. See Capabilities and requirements.
  • Industry classification fields in the merchant panel now offer searchable NAICS codes on customer profiles and requirement tasks. See KYB workflow.

​
Changed

  • Bank-detail submissions that conflict with an in-progress bank setup now return 409 ops_rail_handoff_conflict. Keep your uploaded document IDs and retry the same submission after the conflict is resolved instead of re-uploading documents. See Errors and retries.
  • The minimum for unannounced stablecoin deposits into customer wallets is now 1 unit instead of 10. Smaller deposits are still treated as dust. See Receive funds.
  • Webhook configuration is now isolated per environment. The webhook portal opens scoped to the environment you request it from, so sandbox and production endpoints no longer share settings. See Webhooks.
  • The merchant panel now derives available pay-in methods from the customer’s v3 capabilities, so account setup only offers methods the customer is entitled to. See Accounts.
  • RFI forms now collect qualifying beneficial owners with shorter, clearer prompts, and RFI history displays as lifecycle milestones. See Document requirements.

​
Removed

  • The merchant panel no longer offers Fedwire when adding new pay-in methods. Existing Fedwire accounts remain readable. See Accounts.

​
Fixed

  • Unannounced USDT deposits into customer wallets are now recognized and settled instead of being ignored.
  • Evidence you have already submitted now carries over to other tasks that require the same item, so customers are not asked for the same document twice.
  • Re-requesting a capability no longer discards bank routes that are already ready, so issued account details stay stable.
  • Bank instruction views in the merchant panel now show complete details, including SWIFT addresses and the target wallet address.
  • RFI forms now surface submission validation errors, validate legal form descriptions before submission, and accept multiple business websites.
  • You can now edit related-person drafts in RFI forms before submitting.
  • Canceled compliance requests no longer appear in the merchant panel task list.
  • Document review statuses display correctly again in the merchant panel.

​
2026-08-24

Version: v3

​
Added

  • Customer-scoped hosted verification and Terms of Service sessions now include an authoritative action object. Follow its available or unavailable kind; the flat url and expiresAt fields remain compatibility mirrors for available actions. See Capabilities and requirements.
  • Sandbox wallet top-ups now return transfer IDs that you can read with GET /v3/transfers/{transferId} or list with GET /v3/transfers. They appear as completed inbound stablecoin deposits. See Test in the sandbox.

​
Changed

  • The merchant panel’s First pay-in walkthrough for card and Apple Pay now requires a Polygon wallet under the customer. Create that wallet before you start the walkthrough. See Accounts.
  • New requests and public responses use sepa as the canonical method and capability name. The sepa_instant input alias and previously stored resources remain compatible, but public responses use sepa. See Accounts.
  • New Faster Payments capability, issued-account, and quote requests are unavailable. Existing accounts, quotes, and transfers remain readable. See Accounts.
  • The first KYB page no longer collects the representative’s birth date. Shareholder birth dates remain a separate requirement. See KYB workflow.
  • RFI document references now accept the image/jpg MIME alias in addition to image/jpeg. See Document requirements.
  • Task history in the merchant panel now presents a human-readable audit trail without revision counters. See Capabilities and requirements.

​
Removed

  • The merchant panel no longer offers new UAEFTS account setup. Existing UAEFTS accounts remain readable. See Accounts.

​
Fixed

  • RFI forms preserve existing entries when a reviewer adds a new document drop, so previously supplied answers are no longer lost on resubmission.
  • The merchant panel resumes hosted compliance sessions from available actions without discarding valid links.
  • Hosted Terms of Service links now work for every task scope returned by the API.
  • After you request Payment Access in the merchant panel, it opens the intake task returned by that request instead of a task from an earlier request.
  • The merchant panel’s KYB demo now asks for the current required fields.
  • A quote that reuses its source wallet as destinationId now returns actionable 422 quote_direction_invalid details before any provider work starts. See Quotes and transfers.
  • The API rejects malformed query-string encoding with a 400 error instead of silently normalizing the request, so invalid inputs surface earlier. See Errors and retries.
  • POST /v3/customers/{customerId}/documents now rejects empty, non-multipart, or malformed request bodies with a 400 error.

​
2026-08-17

Version: v3

​
Added

  • Published the v3 Problem Details catalog in the OpenAPI spec so integrators can map error responses directly from the schema. See Errors.
  • Added customerId to v3 account webhook events, letting you correlate account activity to the owning customer without a follow-up read. See Webhooks.
  • The merchant panel now exposes every v3 individual-profile field, so onboarding operators can review and edit all KYC data collected through the API. See Onboard customers.
  • Published a developer migration guide for v3. See Migrate to v3.

​
Changed

  • Customer and account country codes are now validated as assigned ISO 3166-1 alpha-2 values at write time. Reads tolerate legacy stored values so existing records keep resolving. See Accounts.
  • USDC availability is now scoped by destination network, so quotes and transfers offer USDC only on networks that the destination supports.
  • Every onboarding flow now requires the Swipelux Terms of Service. Existing sessions remain resumable. See Onboard customers.
  • Capability.ready continues to report entitlement approval. Use accountProvisioning to track account issuance as not_applicable, not_started, in_progress, issued, or failed. See Capabilities and requirements.
  • HEIC uploads from iPhone are now accepted as identity and address documents.

​
Fixed

  • Re-executing a consumed quote now returns 409 quote_execution_consumed instead of a generic error. See Quotes and transfers.
  • Transfer list and quote amount reads no longer return 500 for large historical result sets.
  • Concurrent KYC redirects now return a conflict instead of 404, so retries resolve cleanly. Hosted redirects no longer roll back midway, and KYC links remain resumable.
  • Related-party reads for individual customers no longer return 404.
  • KYB submissions with invalid wallet fields are rejected before submission, and failed synchronization is no longer reported as success in the merchant panel.
  • Requirement tasks in the merchant panel now show submitted responses as complete, track terms actions separately, remove duplicate document text, keep started KYC sessions pending until completion, and handle stale tasks without breaking the requirements view.
  • Verification-link rows in the merchant panel now show an Open action on every row, and every task link renders in the requirements view.