Skip to main content
Subscribe to updates on the Fluz Status Page for incidents and proactive change notifications. You can also subscribe to this changelog via RSS.
Added
November 2026
  • New query getDepositFeeEstimate. It quotes a deposit before you submit it: the total funding fee, the amount that will be charged to the funding source, and the settlement delay. Pass the amount, the deposit type, and exactly one of bankCardId or bankAccountId. The estimate is never lower than the fee the deposit is charged. Requires MAKE_DEPOSIT. See getDepositFeeEstimate.
  • feeBreakdown lists the parts that make up the estimated fee: Fluz’s funding fee, then any fee on account funding transactions charged on top of it: your application’s, or a Fluz AFT fee. Each part carries its rate, its amount and what set the rate. Where one applies, it also carries the identifier of the fee definition, override, payment rate or BIN configuration behind it. A part priced by an override of a fee definition has source FEE_OVERRIDE. When a part’s rate replaces a standard one (an override, BIN configuration, merchant category tier or AFT rate), baseFeePercent / baseFeeFixed carry the standard rate. The amounts add up to fee; when no complete breakdown is available the list is empty, which does not mean the fee is zero. Additive and backward-compatible. See DepositFeeComponent.
Changed
November 2026
  • sendMoney now holds money for a claim only when held sends are turned on for the account. Fluz turns them on per account, separately from send money. Without them, Fluz refuses any send it would hold, such as a linkOnly send or a send to an email or phone that no Fluz user has verified. The error is G-0003 with the message Sending to someone who isn't on Fluz isn't enabled for this account. No money moves. Sends that land right away aren’t affected. Ask your account team to enable held sends. See Send money.
Changed
November 2026
  • sendMoney now takes the recipient’s account id as recipientId, the name lookupUser and lookupBusiness return it under. Requests that still send recipientAccountId are refused. See Send money.
Added
November 2026
  • New mutation sendMoney sends money from a user’s cash balance to an email address, a phone number, a Fluz account id, or a claim link, and cancelMoneySend cancels a send nobody has claimed. A send to an account id reaches that account right away, and a send to an email or phone a Fluz user has verified reaches that user’s personal account right away. If you pass both an email and a phone and they match the same user, the phone decides, and if they match different users the send is held. An email or phone that matches more than one user is refused. Any other send is held until the recipient claims it on a Fluz page, and returns to the sender if you cancel it or it expires, after 30 days by default. Both need a Bearer user access token with the MAKE_PAYOUT_TRANSFER_SEND scope and a user who is an owner or admin of the account, and a new send also needs send money enabled on the account. Additive and backward-compatible. See Send money.
Added
October 2026
  • New webhook event OAUTH_USER_UNLINKED, currently available in staging only — it is not yet delivered in production. Fired once when a user’s OAuth link to your application is revoked, whether the user removes your app under Apps & Integrations or Fluz revokes the link on their behalf. The payload carries accountId, userId, appId, externalReferenceId, reason (USER_REVOKED or ADMIN_REVOKED), and occurredAt; it never includes contact details or scopes. No scope is required, and like OAUTH_USER_LINKED it is delivered to public/OAuth and widget apps only. Once it fires, the user’s access and refresh tokens are rejected, generateUserAccessToken with the revoked externalReferenceId is refused, and no other events are delivered for that user until they link again, which fires OAUTH_USER_LINKED as usual. See OAuth user unlinked.
Added
October 2026
  • The OAUTH_USER_LINKED webhook event now carries spendAccountAccess, currently available in staging only — it is not yet delivered in production. It states which of the user’s spend accounts the link can act on: restricted: true with the granted userCashBalanceIds, or restricted: false with userCashBalanceIds: null when the grant covers all of the user’s spend accounts, current and future. Restricted grants also carry includesFutureSpendAccounts, which says whether spend accounts the user opens later join the grant automatically. Use it to start calling spend-account operations such as getSpendAccountPaymentInstructions right after the link without a follow-up lookup. IDs only — nicknames and balances come from getWallet, which remains the source of truth for the permitted spend accounts. The event fires again with the updated value whenever the grant changes, including a change of granted spend account alone. Additive and backward-compatible. See Spend account access.
  • In registerUser consent mode, the person must now sign in with the phone number you submitted to approve the authorizationUrl. Before, the number was only pre-filled. If they sign in with a different number, Fluz shows them an error and creates no grant, and registerUser keeps returning PENDING_CONSENT. Submit the phone number the person uses with Fluz. See Consent mode.
ChangedSecurity
October 2026
  • Widget tokens now identify your application with an appId claim, the App ID shown on your app’s Overview tab. Stop signing apiKey into the token: your API key is your application’s credential, and the token is visible in the user’s browser. Tokens that still carry apiKey keep working for now. See Set Up Your Server.
  • The widget script 1.3.0 no longer takes apiKey in FluzEmbedded.init(), and it ignores the value if you still pass it. Update the script URL to ?v1.3.0 and remove apiKey from your init() call. See Adding the JS Widget.
Added
October 2026
  • registerUser has a new consent mode, which Fluz turns on per application. In consent mode, registerUser creates no user, account, or grant when you call it. It returns status: PENDING_CONSENT with an authorizationUrl and expiresAt, where the person signs up or logs in, with the phone number you submitted pre-filled, and approves your application’s scopes. You then call generateUserAccessToken with your externalReferenceId. The response is the same whether or not the person already has a Fluz account, and AUTH-0026 and AUTH-0027 are never returned in this mode. If your application already holds a grant for the externalReferenceId, the response is status: LINKED with the userId and accountId. New arguments: externalReferenceId (required in consent mode), steps, and callbackUrl. dateOfBirth, billingAddress, and acceptCardholderAgreement are now nullable in the schema; direct registration still requires them, and leaving one out now returns ARG-0002 or ARG-0001 in data instead of a GraphQL validation error. New response fields: status, authorizationUrl, expiresAt. Additive and backward-compatible for applications that are not switched. See Consent mode.
  • The enrollment widget token now accepts an empty steps array, which ends the flow at consent. See Choosing the steps.
Added
September 2026
  • The enrollment widget token accepts an optional targetFundingSource claim, currently available in staging only — it is not yet supported in production. Set it to BANK_ACCOUNT, BANK_CARD, or PAYPAL to open that funding source’s flow the first time the user reaches the FUNDING_SOURCE step; it changes only where the step starts and does not restrict the user to that type. Requires FUNDING_SOURCE in steps. An unknown value, or a type that is not enabled for your application, rejects the session. Additive and backward-compatible. See Opening a specific funding source.
Added
September 2026
  • The OAUTH_USER_LINKED webhook event now carries the linked user’s emailAddress and phoneNumber, currently available in staging only — they are not yet delivered in production. This lets you provision the connected user without a follow-up lookup. Either field is null when the user has no value on file, and both are absent in the rare case the details can’t be loaded, so treat an absent field as unknown rather than as null. The phone number format is not normalized, so normalize it before matching against your own records. Additive and backward-compatible. See Webhooks.
Added
September 2026
  • Transaction webhooks now carry externalReferenceId, currently available in staging only — it is not yet delivered in production. Present on TRANSACTION_CREATE, TRANSACTION_UPDATE and TRANSACTION_DECLINE, resolved from the OAuth grant between the user and your application, so the same event reaches each application carrying that application’s own identifier for the user. Absent for private-app deliveries and for grants created without an external reference, so handle a missing value. FUNDING_SOURCE_STATUS_UPDATE also emits it and is now documented as such. Additive and backward-compatible. See Webhooks.
Improved
September 2026
  • Virtual Card Return events now carry isReversal: true for a released authorization hold, whether the card issuer or Fluz released it, and false for a merchant refund. Returns pushed before 2026-09-25 20:15 UTC carry no value; for those, and for the few returns we still cannot classify, use referenceId and the original authorization to tell a released hold from a refund, as described under Reversals vs refunds. Additive and backward-compatible.
Added
September 2026
  • Bring Your Own Integration for Plaid (BYOI Plaid). Your application can now use its own Plaid client ID and secret for the bank links that your users make through it. The developer of the application registers the credentials with registerPlaidIntegration, reads them with getPlaidIntegration, and turns BYOI Plaid off with disablePlaidIntegration. These three operations need the new BYOI_PLAID scope. Applications with a Plaid integration repair a disconnected bank link with createPlaidRelinkToken and completePlaidRelink, which need MANAGE_PAYMENT. The bank linking flow does not change, and bank links made with Fluz Plaid continue to work. Additive and backward-compatible. See BYOI Plaid.
Added
September 2026
  • Merchant categories are now available over the API, so you no longer need a CSV export to show or filter by category. getMerchants returns categories on each merchant — a list, because a merchant can belong to more than one, empty when it is uncategorized — and accepts a categoryId argument to return only the merchants in one category. The new getMerchantCategories query lists the categories with their ids, which is the same taxonomy shown in the Fluz catalog. Category ids are stable, so store the id rather than the name if you cache the mapping. Both require the LIST_OFFERS scope. Additive and backward-compatible. See Get Catalog.
Added
September 2026
  • New webhook event FUNDING_SOURCE_STATUS_UPDATE, currently available in staging only — it is not yet delivered in production. Fired when a user adds, renames or removes a funding source. One event type covers all three cases — branch on changeType (ADDED, UPDATED, DELETED) rather than on the event name. The payload carries fundingSourceId, fundingSourceType (BANK_ACCOUNT, BANK_CARD, PAYPAL), brand, lastFour, nickname, status, and timestamps; full card and account numbers are never included. Requires the LIST_PAYMENT scope, and is delivered to private apps as well as OAuth apps. It is emitted from the change to the funding source itself, so it fires wherever the user made the change — mobile app, web app, or embedded widget. The user’s Fluz cash balance is not a funding source and produces no event. See Webhooks.
Added
September 2026
  • Transaction webhooks now carry isReversal. It is true for an authorization reversal, false for a transaction we classified as something else, and absent when we could not classify it. Present on TRANSACTION_CREATE, TRANSACTION_UPDATE and TRANSACTION_DECLINE. Coverage is still partial: today only card verification voids are flagged true, and returns carry no value at all, so the field cannot yet tell a released hold apart from a merchant refund. Treat an absent value as unknown, never as false. Additive and backward-compatible. See Webhooks.
Added
September 2026
  • Correction (November 2026): this entry previously announced useRewardsBalance on createTransfer and requestAccountTransfer. That field is not available in the API, and these mutations are funded from the sender’s spend account (or a linked bank card, bank account or PayPal) only. See Pay with rewards for where rewards can be used today.
Added
September 2026
  • getUserPurchases now accepts purchaseDisplayId on its filter argument, so you can fetch a single order by the reference ID returned at purchase time instead of paginating your history to find it. It is the same value exposed as referenceId on getTransactions, and the purchase record carries the full details — seatRewardValue for cashback, the payment breakdown, and the linked giftCard — in one call. The filter applies on top of scope and only narrows it. scope values combine with AND, so passing both TOKEN_USER and TOKEN_ACCOUNT returns only purchases the token’s user made on the token’s account — an order placed by another user is returned when scope is TOKEN_ACCOUNT on its own. Additive and backward-compatible. See UserPurchaseFilterInput.
Added
September 2026
  • getVirtualCardBalance now returns status, locked and authorizationSetting alongside the spend figures, so you can read card state for many cards in one call instead of calling revealVirtualCardByVirtualCardId per card and hitting the issuer’s rate limit. A locked card still reports status: ACTIVE, so use locked, which covers locks set by the cardholder, by Fluz once the lock date passes, and by Fluz support. authorizationSetting is the same object reveal returns. Additive and backward-compatible. See Get Virtual Card Balance.
Added
August 2026
  • Documented how debit cards are used for money movement. Deposits from a debit card into CASH_BALANCE may be processed as account funding transactions (AFT), which carry their own fee rate — read depositFee from the response rather than computing it. Push-to-card withdrawals (method: BANK_CARD) are delivered as original credit transactions (OCT). Card eligibility for either is not available in advance and is independent per direction — a card a user can deposit from is not necessarily a card you can send a withdrawal to. See Deposit From External Accounts and Withdraw to External Account.
  • isExpedited on WithdrawCashBalanceInput now controls push-to-card delivery speed: true delivers to the card immediately, false or omitted settles on the standard schedule. A standard push-to-card withdrawal can still fail after it is submitted and be refunded to the source balance — so a PENDING withdrawal is not yet final.
  • Documented getWithdrawFeeEstimate on Withdraw to External Account for previewing fee, netAmount, feePercent, feeMaxCap, and settlementDelayDays before submitting a withdrawal.
  • Corrections to Withdraw to External Account: the required scope is MAKE_WITHDRAWAL (not MANAGE_PAYMENT), error codes are the real WDR-* / ARG-* / HN-* / BC-* / G-* codes, and FLUZPAY — though present on the WithdrawMethods enum — is not a usable withdrawal method: withdrawCashBalance rejects it with WDR-0004 and getWithdrawFeeEstimate with ARG-0001.
Added
August 2026
  • Digital wallet signal on transactions. The TRANSACTION_CREATE and TRANSACTION_UPDATE webhook events and the getTransactions API now include digitalWalletProvider (APPLE_PAY, GOOGLE_PAY, or absent) so you can tell when a card transaction was made through a mobile wallet, plus digitalWalletToken (the network token id). Use digitalWalletProvider as the wallet signal — digitalWalletToken is also set for non-wallet network tokens, so its presence alone does not mean a wallet was used. Additive and backward-compatible. See Webhooks.
Improved
August 2026
  • Open Loop Cards: recipients are no longer prompted to create a PIN during the initial activation flow, and the card is no longer auto-revealed on claim. Revealing a card now prompts the recipient to enter their PIN, or create one if they haven’t set one yet. See Recipient Experience.
Added
July 2026
  • Update GenerateVCShareLinksInput for Open Loop Cards. See Open Loop Cards.
Improved
July 2026
Added
July 2026
Added
June 2026
  • GiftCard.purchaseId (UUID) — the purchase that created the gift card; the same ID returned by purchaseGiftCard and getUserPurchases. Returns null if no associated purchase.
  • GiftCard.purchaseDisplayId (String) — the short, human-readable Fluz transaction ID (e.g. 1047283) that support references in manual reviews and exports. Returns null if no associated purchase.
  • GiftCard.purchaseValue (Float) — the face value (denomination) the gift card was purchased at, in the card’s currency.
  • GiftCard.currentValue (Float) — the remaining balance on the gift card; equals purchaseValue for single-use cards.
  • GiftCard.currency (String) — the ISO currency code of the gift card’s value (e.g. USD).
All five fields are now returned by getGiftCards (and anywhere GiftCard is exposed), enabling order/value reconciliation without calling revealGiftCardByGiftCardId per card. Additive and backward-compatible.
Added
June 2026
  • Added Plaid Link support.
  • Updated Overview page with llms.txt information.
  • Updated header with AI link to llms.txt.
Added
May 2026
  • New getCardProvisioningUrl query — mints a short, single-use URL that, when opened on a mobile device, launches Fluz and adds a virtual card to Apple Pay (iOS) or Google Pay (Android). Surface it as a QR code, SMS, email, or in-app button. Each URL expires ~5 minutes after creation. Requires the CREATE_VIRTUALCARD scope.
  • New input GetCardProvisioningUrlInput { offerId, platform }.
  • New enum ProvisioningPlatform (IOS | ANDROID | OTHER) — controls the desktop / unknown-device fallback only; iOS and Android opens are auto-routed.
  • New return type CardProvisioningUrl { url, expiresAt }.
Improved
May 2026
Added
May 2026
  • Added addVirtualCardAddress mutation to save billing addresses for virtual card issuance.
  • Updated createVirtualCard mutation to support creating cards on behalf of authorized users.
  • Added full flow using registerUser, addAuthorizedUser, addVirtualCardAddress, and createVirtualCard.
  • Retry pending issuer approvals with VC-0020 and returned addressId.
Added
May 2026
  • redeemFluzGiftCard — Redeem a Fluz Gift Card using a code. Credits giftCardCashBalance. Requires MAKE_DEPOSIT. See Redeem a Fluz Gift Card.
  • unlockVirtualCard — Unlock a previously locked virtual card to restore transaction capability. Requires EDIT_VIRTUALCARD. See Unlock a Virtual Card.
Improved
May 2026
Transaction-related webhooks
  • Added description for TRANSACTION_CREATE, TRANSACTION_UPDATE & TRANSACTION_DECLINE webhooks.
  • Included new fields after webhook enrichment (MCC-related, virtualCardId, etc.).
Added
May 2026
  • Added mcc, merchantCountryCode, originalCurrencyCode, originalCurrencyAmount, and currencyConversionRate to VirtualCardTransaction. Now returned by getVirtualCardTransactions.
  • Made virtualCardIds optional on getVirtualCardTransactions — omit to query transactions across all cards on the authenticated account. Added dateRangeStart and dateRangeEnd filters. Default limit of 100 when virtualCardIds is omitted; limit is capped at 500. transactionAmount is now nullable for rows without a settled amount (e.g., AVS-only decline records).
  • Added usePrepaymentBalance and useRewardsBalance to CreateVirtualCardInput. Now accepted by createVirtualCard. Both default to true (existing behavior preserved). Set both to false to restrict a card to drawing only from the specified userCashBalanceId, excluding prepaid (gift card) and rewards funds.
Added
April 2026
  • Added shortDescription (Merchant) and termsAndConditions (Offer). Now returned by getMerchants and getOfferQuote.
  • Added deliveryFormat (GiftCard). Now returned by getGiftCards — use deliveryFormat for purchased cards.
Added
April 2026
  • New setVirtualCardPIN mutation, allowing a user to set their PIN on eligible virtual cards. See Set a Virtual Card PIN.
Added
April 2026
  • New getUserCashBalances & getUserCashBalanceById queries. These queries allow a user to retrieve a list of their spend accounts and a specific spend account created on their account.
Added
April 2026
Share Virtual Cards API
  • New “Share Virtual Cards” capability under Manage Virtual Cards. Contact sales for access.
  • Added CREATE_SHARE_LINK scope to the application scopes page.
Added
February 2026
Business registration API
  • New query getBusinessCategories: [BusinessCategory] for retrieving business categories, with response types BusinessCategory and BusinessSubCategory.
  • New mutation registerBusiness(input: RegisterBusinessInput!): RegisterBusinessResult for programmatic business registration.
  • New input types: RegisterBusinessInput, BusinessLegalAddressInput, BusinessOwnerInput, OwnerAddressInput.
  • New enums: BusinessStructure (LLC, CORPORATION, PARTNERSHIP, SOLE_PROPRIETORSHIP, COOP) and BusinessAccountUsage.
  • New response types: RegisterBusinessResult { accountId, kybStatus, success, error } and RegisterBusinessError { message, code }.
  • Both operations require authentication with the REGISTER_BUSINESS OAuth scope.
Improved
January 2026
Updates to getMerchants query
  • The getMerchants query now returns all available offers properly.
  • The getMerchants query can now return an exclusiveRateId field (within the offers object). This value can be used in purchaseGiftCard to specify the exclusive rate offer you want to purchase with.
Added
December 2025
Withdrawals & Spend Accounts APIs
  • Added withdrawCashBalance mutation with MAKE_WITHDRAWAL scope requirement.
  • Added WithdrawMethods enum supporting PAYPAL, BANK_ACH, BANK_CARD, and VENMO methods.
  • Added WithdrawSource enum supporting CASH_BALANCE and REWARDS_BALANCE sources.
  • Added WithdrawCashBalanceInput with idempotency support, plus Withdraw and WithdrawCashBalanceResponse types with full withdrawal record details including fees, status, and timestamps.
  • Added transferUserCashBalance mutation with MAKE_INTERNAL_TRANSFER scope requirement, plus TransferInternalBalanceInput and TransferInternalBalanceResponse types.
  • Added userCashBalanceId to EditVirtualCardInput to enable changing the funding source to a specified spend account via editVirtualCard.
  • Added userCashBalanceIds to TransactionFilterInput for filtering transactions by spend accounts via getTransactions, and userCashBalanceId to getGiftCards for filtering gift cards by spend account.
  • Added updateUserCashBalance and closeUserCashBalance mutations with MANAGE_PAYMENT scope requirement, plus supporting input and response types (UpdateUserCashBalanceInput, CloseUserCashBalanceInput, CloseUserCashBalanceResponse, ClosedUserCashBalance, CloseUserCashBalanceResponseVirtualCard).
  • Added application action logging for audit trail.
Added
November 2025
  • Added new userCashBalances field to the UserBalances type in the getWallet query. Returns detailed information about individual user cash balance accounts with pagination via paginate (limit/offset), ordered by creation date (most recent first). Includes userCashBalanceId, totalCashBalance, availableCashBalance, lifetimeCashBalance, nickname, status, and createdAt — enabling tracking of multiple cash balance accounts per user with custom nicknames and status monitoring.
Added
November 2025
  • A new field userCashBalanceId is added to DepositCashBalanceInput to specify the cash balance (spend account) to deposit the funds into.
Added
November 2025
  • New mutations for managing saved bank cards: updateBankCardNickname, updateBankCardPreferredMerchantCategoryCode, and deleteBankCard, with corresponding input types.
  • nickname field added to the BankCard type.
  • Optional fields added to AddBankCardInput: nickname and preferredMerchantCategoryCode (MCC, normalized to 4 digits).
Added
September 2025
  • getVirtualCardBalance: new query retrieving balance information for a list of virtual cards, including spentAmount, remainingBalance, spendLimit, and spendLimitDuration.
  • getVirtualCardTransactions: new query retrieving transactions for a list of virtual cards, with filters such as transactionTypes.
Improved
September 2025
  • The getUserPurchases query now includes the ability to filter the purchases returned in the response via a new optional UserPurchaseFilterInput variable. Filter purchases made by the user, the account, or both.
Added
September 2025
  • The revealVirtualCardByVirtualCardId mutation response now includes a new authorizationSetting field.
  • Bulk Virtual Card API: new API for creating and managing a large number of virtual cards asynchronously.
  • createVirtualCardBulkOrder mutation: submit a bulk order and receive a unique orderId.
  • getVirtualCardBulkOrderStatus query: poll to track order status and retrieve card details upon completion.
  • The bulk card creation process is asynchronous — check order status to retrieve card details.
Added
July 2025
  • New query getVirtualCardOffers: comprehensive list of all active virtual card offers available for creation, including offerId (essential for card creation), programName, bankName, rewardValue, and detailed program limits (daily, weekly, monthly spend limits).
  • Updated mutation createVirtualCard: programmatically issue virtual cards by providing an offerId (from getVirtualCardOffers), a spendLimit, and customizable attributes like cardNickname and spendLimitDuration.
  • New mutation editVirtualCard: update key parameters of an existing virtual card — spendLimit, spendLimitDuration, lockDate, lockCardNextUse, and cardNickname.
  • New mutation lockVirtualCard: immediately lock a virtual card, preventing any further transactions.
Added
July 2025
  • The Offer type in the getMerchants response now includes a deliveryFormat field specifying how the offer is fulfilled: URL, CODES, PIN_AS_CODE, or PIN_WITH_URL.
  • The getMerchants query has been enhanced with a new filterBy argument, allowing you to filter results to only include merchants with offers matching a specific deliveryFormat.
Added
2025
  • Enhanced the getMerchants query with a new offerTypes input argument, allowing filtering by giftCardOffers, cardLinkedOffers, or both. By default, if offerTypes is not provided, the query returns only gift card offers.
AddedImproved
2025
  • Introduced a new query getReferralUrl which returns a referral string based on merchant input, with a new MerchantInput type.
  • Introduced an automatic repurchase attempt on the purchaseGiftCard mutation. If a gift card purchase using a bank card, bank account, or PayPal fails, the system automatically attempts to repurchase using the Fluz balance.
  • Introduced the defaultToBalance field on PurchaseGiftCardInput to set the Fluz balance as the fallback payment method if the primary payment method fails. Defaults to true.
AddedImproved
2025
  • Introduced a new access scope, CREATE_VIRTUALCARD, to create virtual cards.
  • Introduced a new function, createVirtualCard, to create virtual cards with specific parameters.
  • Added new query, getBINs, to retrieve BINs associated with virtual cards.
  • Introduced a merchantCategoryCode input for cash balance deposits, allowing for enhanced categorization of transactions.
  • Added a new query, getMccList, to retrieve a list of merchant category codes.
  • Enhanced scope validation for the getApplicationScopes query and improved GraphQL type definition management.
Improved
2025
  • Enhanced the handling of stock information for merchant offers: the Offer object’s stockInfo field now returns either StockInfoFixedType or StockInfoVariableType depending on whether the offer is fixed or variable.
  • Enhanced error handling with more intuitive error message responses — improved responses for purchaseGiftCard no-offer errors and mismatched account and payment methods.
AddedFixed
2025
v0.0.21
  • Introduced an idempotencyKey parameter for depositCashBalance and purchaseGiftCards to prevent duplicate requests.
  • Added purchaseGiftCardInput types to streamline parameter handling for transactions.
  • Introduced a new field purchaseDisplayId on the UserPurchase type, providing a display ID for purchases.
  • Fixed the Offer object’s offeringMerchantId field to return offering_merchant_id instead of offer_id.
v0.0.20
  • Added accountId requirement to generateUserAccessToken.
  • Implemented a new query, getAccountsByUserId, to fetch accounts based on userId.
  • Added a new AccountType enum to categorize accounts as CONSUMER or BUSINESS, plus new Account, Business, and Seat objects.
v0.0.17
  • Fixed depositCashBalance platform channel input so the deposit transaction log source is logged as API.

Change management

Additive changes (new fields, new enum values, new operations) are announced at least 7 days before release when they require action from integrators. Breaking changes are announced at least 14 days in advance and are typically batched into major release windows. For a complete list of API operations, see the API reference.