The Built to Pay Fast Playbook Is Here for Fintechs, PayFacs, ISOs and Vertical SaaS. Get It Now
CompletePhysicalCardGroupOrder instead of CancelPhysicalPaymentCardOrder.createPricingPlan, validate them against sample transactions with simulatePricingPlan, and apply a published plan to a merchant through onboardPayfacMerchantBusinessOrganization.expiresAt to LinkVerifiedExternalBankAccountVerificationRequiredEvent and deprecated expirySeconds in its favor.InterFinancialAccountTransfer.externalId is now generally available, returning the identifier you supplied when initiating the transfer.CARD_BRAND_NOT_SUPPORTED error description: it fires on an unrecognized card number, not a Visa/Mastercard allowlist.declineReasons field and its four enum values, including when each fires.GENERIC_NAME and UNIQUE_GENERIC_NAME personalization types. Selecting either reveals a Generic Name field whose value (e.g., CARDHOLDER) prints on the Track 1 cardholder line and submits via personalizationValue.CardPaymentAuthorizationHeldEvent, representing a payment transaction held pending a transient processing condition that is expected to resolve without cardholder action, with a holdReason of AWAITING_PROCESSOR_NETWORK_RESPONSE or PENDING_INTERNAL_RESOLUTION.INVALID_ACCOUNT_ID to RewardPointsTransferFailureReasonCode, which distinguishes a structurally invalid (non-decodable) redeem account id from ACCOUNT_NOT_FOUND.signedBalance on Ledger and on each ledger detail in balance-search results (FinancialAccountBalanceLedgerDetail), representing a single balance whose sign is derived from the ledger's normalBalance (negative when the balance runs opposite to normal).LinkVerifiedExternalBankAccountVerificationRequiredEvent carries a time-limited hosted Link URL and expiry for the account holder to complete verification. LinkVerifiedExternalBankAccountExpiredEvent fires when the journey lapses, joining the existing LinkVerifiedExternalBankAccountFailedEvent.declineReasons to the Instant Network Transfer (destination and source) payment instrument capabilities, which explain why a capability is not ENABLED (for example, card region unsupported, not debit or prepaid, or no money-transfer capability).ON_HOLD_AWAITING_NETWORK and ON_HOLD_AWAITING_RESOLUTION for Instant Network Transfers.merchantAcceptors list query and the merchantAcceptors connection on the Merchant type are now available in the production API for retrieving the merchant acceptors associated with a merchant.CardPaymentAuthorizationHeldEvent to the payment transaction event timeline. The PaymentTransactionEvent interface now has a CardPaymentAuthorizationHeldEvent implementor, surfacing authorizations placed on hold together with a holdReason, so a held authorization is observable on the transaction timeline.FinancialAccount.features now includes MerchantFundingFinancialAccountFeature, and MERCHANT_FUNDING was added to FinancialAccountFeatureType for filtering, so accounts carrying the merchant-funding feature surface it via the API.RewardPointsTransferFailureReasonCode enum now includes INSUFFICIENT_FUNDING_ACCOUNT_BALANCE, REDEMPTION_CONFIGURATION_NOT_FOUND, REDEMPTION_CONFIGURATION_ID_OR_POINT_VALUE_REQUIRED, ACCOUNT_NOT_ACTIVE, and TRANSFER_AMOUNT_NOT_POSITIVE, giving more specific failure detail on reward redemptions.idempotencyKey input, letting you safely retry a redemption without double-processing.WIRE_TRANSFER_COMPLETED_EVENT notification now fires when an inbound wire transfer completes and funds are available, delivered as a WireTransfer webhook event.InstantNetworkTransferStatus enum now includes ON_HOLD_AWAITING_NETWORK and ON_HOLD_AWAITING_RESOLUTION, distinguishing a transfer held pending network settlement from one held pending final resolution.FinancialAccount.features now includes CryptoFundingFinancialAccountFeature and CryptoReceivingFinancialAccountFeature, surfacing crypto funding and receiving account features that the API previously dropped.acquirerReferenceNumber, providing a network reference for reconciling a transaction across systems.MONTHLY frequency value and a RECURRING trigger value for pricing rules. The PricingRuleFrequency enum now includes MONTHLY (evaluated monthly), and the PricingRuleTrigger enum now includes RECURRING (triggered on a recurring schedule), supporting monthly and recurring pricing-rule evaluation.Business.services surface as generally available. The Business.services field is now available in the production API, returning the services a business is set up for through the BusinessService interface and its Merchant, Payfac, Iso, and FinancialAccountHolder implementations.MerchantPayfacRelationship now exposes a payfac: Payfac field, resolving the payfac in the relationship directly rather than by ID.transactionBatches query, the closeTransactionBatch mutation, and the TransactionBatch type are now available in the production API for retrieving and closing acquiring settlement batches, including the owner union of Merchant and Payfac.merchantAcceptors list query and a merchantAcceptors connection on the Merchant type, returning the merchant acceptors associated with a merchant.UNACTIVATED to the financial account status enum. The public FinancialAccountStatus enum now includes UNACTIVATED, so financial accounts in the unactivated window report that state instead of a null status.redeemRewardsToFinancialAccount for redeeming reward points into a financial account. The new redeemRewardsToFinancialAccount mutation redeems accrued reward points to a destination financial account, returning a RewardPointsTransferPayload.settlementImpact field, indicating whether a reversal reaches settlement (true) or released an authorization without settling (false).BalanceNotificationEvent now exposes an accountingDirection: AccountingDirection field, aligning balance notifications with the debit/credit direction convention used by transfer events.CRYPTO_*, event types as selectable options when creating or editing a Notification Target.BALANCE_* event types as selectable options when creating or editing a Notification Target.RTP_* event types as selectable options when creating or editing a Notification Target.PAYMENT_METHOD_CAPABILITY_* event types as selectable options when creating or editing a Notification Target.Owner label to Account Holder on the financial-account detail page and added a Primary Financial Account row linking an authorized-user account to its funding account.PREFUNDED_ADVANCE, PREFUNDED_ADVANCE_REPAYMENT, and CUSTOMER_FEE.FUEL_TAX_EXEMPT attribute for fuel tax exempt fleets.merchant_disbursement and merchat_dispute and updated payment_transaction_event with new columns.card_revision table.Adjustment filter to Card Transactions > Event Type.contractId with merchantAcceptorId across the acquiring APIs.eftip_12345.tx_ in search.posted_date_time > created_at, (2) card_profile_set_id > public_card_profile_set_id, (3) network_name > payment_network, (4) classification > bin_classification, (5) funding_type > bin_funding_typeapproved_amount_currency_code, (2) surcharge_fee_currency_code. Updated: (1) card_profile_set_id > public_card_profile_set_id, (2) network_name > payment_network, (3) classification > bin_classification, (4) funding_type > bin_funding_type, (5) currency_code > requested_amount_currency_coderequestedAmount and approvedAmount in the API Reference across all affected events. Requested amount is posted in the transaction's local currency. Approved amount is posted in the settlement currency. Neither include fees.estimatedPayoffDays and added estimatedPayoffPeriod which changes the estimated payoff calculation from days to years and months in the Dashboard and APIFUNDING_STARTED, 2. FUNDING_COMPLETED, 3.FUNDING_DISBURSED, 4.SHIPPED, 5.PAIDQUARTERLY velocity control window to the API and DashboardCLOSED; Prepaid/Debit products must be ACTIVE to load fundsover_limit fields to: last_statement_is_over_limit, last_statement_over_limit_amount, last_statement_over_limit_currency_codeHIGH_UTILIZATION, INCOMPLETE_IDENTITY_INFORMATION, LENGTH_OF_EMPLOYMENT, LENGTH_OF_RESIDENCE, LIEN_POSITION, UNABLE_TO_VERIFY_EMPLOYMENT, UNACCEPTED_BUSINESS_INDUSTRY, WITHDRAWN.COOLDOWN_MINUTE and COOLDOWN_HOURonReady callback function to enable the display of a loading spinner until all SDK elements are ready to be displayed.complexity to API responsesDECEASED, UNABLE_TO_VERIFY_CREDIT_REFERENCES
-Create Credit Plans: Guide was refactored as Standard Credit Purchase.CardPaymentSettledEvent to CardPaymentClearedEventYou can now accept transactions with Highnote! We added the ability to create an acquiring product, accept transactions, view metrics, and more. You can also apply to go live with Highnote acquiring through the dashboard as well. This is just the beginning with many more acquiring feature rollouts planned throughout the upcoming year.
Added the ability to view requested identity updates on an application and the changes that have been applied to an identity.
Added the ability to validate shipping addresses for physical card orders and group orders:
Added the ability to filter the disputes table by Created On, ID, and Status, with more coming in the future:
ACH v2 notification events are now available. ACH v2 notification events were created to simplify ACH transfer events and notifications on the Highnote platform.
Highnote's legacy ACH notification events are still supported. Using the legacy ACH notification events will not impact your integration's functionality or performance.
For more information about ACH v2 notification events and guidance for upgrading to the new events, see the Events Reference.
Added Card Terminal Capability and PAN Entry Mode spend rules to dashboard:
When submitting a dispute case in the Highnote dashboard, you can now issue a new card within the same flow.
The dashboard now supports resolving fraud alerts and credit freezes for credit applications. For more information on credit report inquiries, freezes, and fraud alerts, see Credit report inquiries.
releasedHighnote now integrates with the Google Maps Address Validation API to verify that all physical addresses are properly formatted, valid for identity verification and CASS-certified. For more information, see Validate shipping address.
The account activity page shows Pending and Posted transactions, and has tooltips for each section to explain what kind of transactions fall into each category.
You can now simulate credit report freezes and fraud alerts for credit card products that perform credit report inquiries. For more information, see Simulate Underwriting Decision.
You can now redeem rewards for statement credit from the dashboard. To offer rewards, you must contact support@highnote.com to request that the feature be enabled for your card product. For more information on rewards, see the Rewards guides.
You can now filter individual and group card orders by:
All information about card orders and payment cards can now be found on the cards page of the dashboard. This page now features tabs to provide an easier-to-use interface for viewing card information and card orders.
You can now use the dashboard's test environment to create a rewards program, redeem rewards, and adjust reward points. This feature must be enabled for your card product by the Highnote team. For more information, see Rewards basics.
The account holder page now features tabs to provide an easier-to-use interface for viewing objects associated with an account holder:
Reports now have a cutoff time of 5PM PT or 12AM UTC. These cutoffs are available in the API, and can be viewed in the Reports page of the dashboard:
We've redesigned the Dashboard Home page to display summary metrics for your card program.
For more information, refer to the following resources:
. API guide.The Highnote dashboard now supports the following enhancements when creating Merchant Category Code (MCC) spend rules:
Highnote now supports counter offers and secured deposits. With the counter offer feature, if an account holder’s creditworthiness does not qualify them for the card product they applied for, you can offer them an alternative card product.
Coupled with the secured deposit feature, you can use counter offers to offer a secured deposit card product alternative. This feature unlocks unparalleled flexibility and accessibility for your card program.
For more information on each feature, refer to the following guides:
The following enhancements have been added to the Highnote dashboard:
You can now generate Fleet enhanced data summary reports using the Highnote API and dashboard. This report contains all level 2 and 3 enhanced data sent by Visa and Mastercard for cleared fleet transactions. For more information, see Fleet Enhanced Data Summary Report.
You can now use the Highnote API to retrieve summary metrics for your card products' applications and transactions. For more information, see the Summary Metrics guide.
The Highnote platform now supports card profiles, which house options related to the appearance and performance of payment cards. With card profiles, you can offer your customers different payment card designs, as well as support varying point of sale (POS) behavior capabilities, all within a single card product. Contact the Highnote team for more information on implementing card profiles.
Highnote now offers consumer credit card products, which you can utilize to issue lines of credit to your person account holders. The consumer credit card product requires your account holders to make a minimum payment by their billing cycle due date and allows you to assess interest charges on their revolving balances. For more information on creating consumer credit card products, see the Consumer Credit Quick Start Template.
You can now simulate the creation and resolution of dispute and chargeback cases on your card product in the Test Environment. These simulations enable you to test your integration, along with the notification events associated with dispute cases, provisional credit state changes, and the financial account activity related to disputes, chargebacks, and the issuance and revocation of provisional credits. If you have an existing card product in the Test Environment, please contact support@highnote.com to configure your product for disputes and chargebacks.
In the Live Environment, Highnote will continue to manage the intake and processing of disputes and chargebacks on your card product.
Highnote now supports Mastercard Fleet Card Products. You can use the Transaction Simulation tool to simulate Mastercard Fleet Transactions in the Test Environment. For more information, see Simulate Fleet Transactions.
Three additional fee activity types are now supported: Inactivity, Cash Withdrawal at Point of Sale, and Over-the-Counter Cash Withdrawal. For more information, see Fee Activity Types.
Highnote now offers a Consumer Charge card issuing solution. You can issue lines of credit to US Person Account Holders that require them to pay their statement balance in full by each billing cycle's due date. For more information, see the Consumer Charge getting started guide.
Highnote now supports transferring funds between internal Financial Accounts in real time. This includes transfers from Product Funding Accounts to Account Holder Financial accounts, peer-to-peer transfers, and more. For more information, see Transfer between Financial Accounts.
You can now use Highnote's Reporting feature to generate reports, check report statuses, and download reports. You can generate up to three reports per day. For more information, see Using Reports.
You can now close a Financial Account in the Test Environment to simulate account status changes and the associated events so you can notify your Account Holders of their closed Financial Account. Highnote will continue to handle account closure processes in the Live Environment for your Card Product.
Highnote now offers a Document Upload SDK to collect identity verification documents from Account Holders when a Card Product Application enters manual review. This allows you to seamlessly embed a UI for document upload collection into your customer onboarding experience.
Highnote recently added search capabilities to Authorized Users, allowing you to utilize a node query to find Authorized Users. You can also query for an Authorized User to determine critical details such as the billing address associated with the Card issued to the Authorized User.