Product documentation

Wise Payments Integration

Installation, permissions, configuration, transaction synchronization, HubSpot invoice reconciliation, data handling, security, troubleshooting, and support documentation.

Current documentation Last updated July 29, 2026 Atlantic Ops
Jump to a section
  1. Integration overview
  2. Requirements
  3. Installation
  4. Connecting Wise
  5. Wise profile selection
  6. Synchronization settings
  7. Transaction synchronization
  8. HubSpot records and properties
  9. Counterparty association
  10. Payment monitoring
  11. Invoice reconciliation
  12. Commerce payments
  13. HubSpot scopes
  14. Data processing
  15. Data storage and security
  16. Disconnecting and uninstalling
  17. Troubleshooting
  18. Frequently asked questions
  19. Support
01 — Overview

Integration overview

The Wise Payments Integration connects a Wise account with HubSpot so businesses can synchronize Wise transaction information, associate Wise counterparties with HubSpot companies and contacts, and reconcile incoming Wise payments with HubSpot invoices.

The integration provides the following functions:

  • Connect a HubSpot account through HubSpot OAuth.
  • Connect a Wise account through Wise OAuth.
  • Select the Wise business profile that should be synchronized.
  • Retrieve Wise profiles, balances, recipients, and balance statement transactions.
  • Create or update Wise Transaction records in HubSpot.
  • Display Wise transaction information on HubSpot company and contact records.
  • Allow users to manually associate a Wise counterparty with a HubSpot company or contact.
  • Synchronize new incoming Wise payments through signed Wise webhooks.
  • Match completed incoming Wise transactions with open HubSpot invoices.
  • Create HubSpot commerce payment records for successfully matched payments.
  • Associate HubSpot commerce payment records with matching invoices.
  • Prevent duplicate transaction and commerce payment creation.
  • Maintain periodic transaction reconciliation in addition to webhook-driven synchronization.
Explicit association only

The current integration does not use fuzzy name matching, domain guessing, or automatic CRM record creation. A user must explicitly select the HubSpot company or contact represented by a Wise counterparty.

02 — Requirements

Requirements

To install and use the integration, you need:

  • A HubSpot account that supports the requested CRM, invoice, commerce payment, and custom object functionality.
  • Permission to install and authorize Marketplace apps in the selected HubSpot account.
  • A Wise account with access to the Wise profile that will be connected.
  • Permission within Wise to authorize third-party applications.
  • At least one eligible Wise balance when transaction synchronization is required.
HubSpot subscription requirements

Some HubSpot subscriptions may not include custom objects, invoices, commerce payments, or all required API scopes. Installation may not be available in accounts that do not support the required functionality.

03 — Installation

Install the integration

Install the integration in HubSpot

  1. Open the Wise Payments Integration installation link.
  2. Select the HubSpot account you want to connect.
  3. Review the HubSpot permissions requested by the integration.
  4. Approve the installation.
  5. Return to HubSpot and open the integration settings.

After authorization is complete, the integration will:

  • Store the HubSpot account ID and OAuth credentials.
  • Create or confirm the required Wise property group.
  • Create or confirm the required company properties.
  • Create or confirm the required contact properties.
  • Initialize integration settings for the connected HubSpot account.
Screenshot placeholder HubSpot installation, account selection, and scope approval screens.

Open the integration settings

The settings page displays:

Connections

Account status

  • HubSpot connection status.
  • Wise connection status.
  • Wise permission mode.
  • Connected Wise profile.
Synchronization

Sync configuration

  • Available Wise balances and currencies.
  • Transaction history settings.
  • Last synchronization status.
  • Incoming payment listener status.
04 — Wise connection

Connect a Wise account

Before connecting Wise, select one of the available permission modes.

Permission mode

Read-only

Read-only mode allows the integration to:

  • Read Wise profile information.
  • Read Wise recipient information.
  • Read balance information.
  • Read balance statement transactions.
  • Synchronize Wise transactions into HubSpot.
  • Configure the Wise webhook subscription required for incoming payment monitoring.

Read-only mode does not permit the integration to create, update, send, cancel, or delete Wise transfers or payments.

Permission mode

Read and create

Read and create mode includes all read-only capabilities and authorizes supported Wise API write operations.

Selecting this mode does not automatically send money or create Wise transfers. Current synchronization and HubSpot invoice reconciliation create records in HubSpot; they do not initiate a Wise transfer.

Future features that perform a Wise write operation will only be available when the connection uses Read and create access.

Webhook configuration in read-only mode

Webhook subscription configuration is permitted in read-only mode because it controls delivery of incoming synchronization events. It does not move funds or modify a Wise payment.

Authorize the Wise account

  1. Select the required Wise permission mode.
  2. Click Connect Wise.
  3. Sign in to Wise.
  4. Review and approve the Wise authorization request.
  5. Return to the integration settings page.
  6. Select the Wise profile to synchronize.
  7. Save the settings and test the connection.
OAuth state protection

The Wise authorization request uses a single-use state value that expires after ten minutes. This protects the connection process against unauthorized OAuth callback requests.

05 — Profile selection

Select a Wise profile

A Wise account may contain more than one personal or business profile. The integration synchronizes one selected Wise profile per HubSpot account at a time.

The selected profile determines:

  • Which Wise balances are available.
  • Which currencies are synchronized.
  • Which recipients can be displayed.
  • Which balance statements are retrieved.
  • Which incoming payment webhook subscription is configured.
  • Which transactions are created in HubSpot.
Changing profiles

Changing the selected profile does not automatically delete transactions previously synchronized from another Wise profile.

06 — Settings

Transaction synchronization settings

Transaction history

The transaction history setting determines how much Wise statement history is retrieved during a manual synchronization.

Option Description
30 days Retrieves the previous 30 days of statement activity.
90 days Retrieves the previous 90 days of statement activity.
180 days Retrieves the previous 180 days of statement activity.
365 days Retrieves one year of statement activity. This is the default.
730 days Retrieves up to two years of statement activity.

Existing HubSpot transaction records are not automatically deleted when the transaction history setting is reduced.

Displayed transaction limit

The integration can limit how many transactions are displayed in applicable CRM cards or settings views.

  • 10 transactions.
  • 25 transactions.
  • 50 transactions.
  • 100 transactions.

The default display limit is 25 transactions. This setting affects the display of transaction data and does not necessarily limit how many eligible records are synchronized into HubSpot.

07 — Synchronization

Run and manage transaction synchronization

Run the initial synchronization

  1. Test the Wise connection.
  2. Confirm that the correct profile, balances, and currencies appear.
  3. Save the transaction history setting.
  4. Click Run sync.
  5. Allow the integration to retrieve and normalize eligible Wise transactions.
  6. Review the Wise Transaction records created in HubSpot.

The first synchronization may process a larger amount of data than subsequent synchronizations.

Wise limits the maximum date range of an individual balance statement request. When necessary, the integration divides the selected history period into smaller statement windows and combines the results.

How synchronization works

The integration retrieves balance statements for the selected Wise profile and converts each eligible statement entry into a normalized Wise Transaction record.

The integration may extract:

  • Wise transaction ID.
  • Wise profile ID.
  • Transaction amount and currency.
  • Transaction date.
  • Direction and status.
  • Counterparty name.
  • Counterparty account identifier when available.
  • Payment reference.
  • Transaction description.
  • Wise transfer ID when available.
  • Transaction type.

Normalized transaction values

Direction

Transaction direction

  • Incoming.
  • Outgoing.
Type

Transaction category

  • Incoming payment.
  • Outgoing payment.
  • Refund.
  • Fee.
  • Conversion.
  • Other.
Duplicate prevention

Each Wise transaction ID is used to identify existing records and reduce duplicate creation.

08 — HubSpot data

HubSpot records and properties

Wise Transaction custom object

The integration uses a HubSpot custom object representing individual Wise transactions. Depending on the approved object configuration, the object may be labelled Wise Transaction or Payment Transaction.

Property Description
Wise Transaction Name Human-readable name containing the date, direction, counterparty, amount, and currency.
Wise Transaction ID Unique transaction identifier received from Wise.
Wise Profile ID Wise profile associated with the transaction.
Wise Counterparty Name Name of the sender, recipient, merchant, or other counterparty.
Wise Counterparty Account Available Wise account or bank account identifier associated with the transaction.
Wise Transaction Amount Transaction amount.
Wise Transaction Currency ISO currency code.
Wise Transaction Date Date and time of the transaction.
Wise Transaction Description Description and available transaction details.
Wise Transaction Direction Incoming or outgoing.
Wise Transaction Reference Payment, invoice, or bank reference when available.
Wise Transaction Status Completed, pending, cancelled, failed, or another supported status.
Wise Transaction Type Incoming payment, outgoing payment, refund, fee, conversion, or other.
Wise Transfer ID Wise transfer identifier when available.
Wise Last Sync Last date and time the record was synchronized.

Company properties

The integration creates a Wise Integration property group on HubSpot company records.

Property Description
Wise Profile ID Wise business profile associated with the company.
Wise Account Connected Indicates whether the company is connected to a Wise profile.
Wise Current Balance Current synchronized Wise balance where applicable.
Wise Balance Currency ISO currency code for the synchronized balance.
Wise Total Received Total received through transactions associated with the company.
Wise Total Sent Total sent through transactions associated with the company.
Wise Payment Count Number of associated Wise transactions.
Wise Last Payment Date Date of the most recent associated payment.
Wise Last Payment Amount Amount of the most recent associated payment.
Wise Last Payment Currency Currency of the most recent associated payment.
Wise Last Transaction ID Wise ID of the most recent associated transaction.
Wise Last Transaction Direction Direction of the most recent associated transaction.
Wise Last Transaction Status Status of the most recent associated transaction.
Wise Connection Status Connected, disconnected, or error.
Wise Last Sync Date Last date and time Wise data was synchronized.
Wise Manual Counterparty Name Exact Wise counterparty selected by a user.
Wise Manual Transaction Count Number of transactions matching the selected counterparty.
Wise Manual Transaction Last Associated At Last date and time the association was updated.

Contact properties

The integration creates a Wise Integration property group on HubSpot contact records.

Property Description
Wise Profile ID Wise profile used for the contact’s transaction data.
Wise Recipient ID Wise recipient identifier associated with the contact.
Wise Recipient Currency Currency configured for the Wise recipient.
Wise Recipient Match Status Current recipient association status.
Wise Total Received Total received through transactions associated with the contact.
Wise Total Sent Total sent through transactions associated with the contact.
Wise Payment Count Number of associated Wise transactions.
Wise Last Transaction Date Date of the most recent associated transaction.
Wise Last Transaction Amount Amount of the most recent associated transaction.
Wise Last Transaction Currency Currency of the most recent associated transaction.
Wise Last Transaction ID Wise ID of the most recent associated transaction.
Wise Last Transaction Direction Direction of the most recent associated transaction.
Wise Last Transaction Status Status of the most recent associated transaction.
Wise Last Sync Date Last date and time Wise data was synchronized.
Wise Manual Counterparty Name Exact Wise counterparty selected by a user.
Wise Manual Transaction Count Number of transactions matching the selected counterparty.
Wise Manual Transaction Last Associated At Last date and time the association was updated.
09 — Associations

Associate Wise counterparties with HubSpot records

Automatic or fuzzy CRM matching is not used.

  1. Open a HubSpot company or contact record.
  2. Open the Wise integration card.
  3. Search or browse the available Wise counterparties.
  4. Select the exact counterparty represented by the HubSpot record.
  5. Preview the matching Wise transactions.
  6. Confirm the association.

After confirmation, the integration:

  • Finds Wise Transaction records with the exact selected counterparty name.
  • Associates those transaction records with the selected company or contact.
  • Saves the counterparty mapping.
  • Updates the manual counterparty properties.
  • Updates applicable transaction totals and latest transaction information.

The integration does not

  • Guess a company based on an email domain.
  • Guess a contact based on a similar name.
  • Automatically create a company.
  • Automatically create a contact.
  • Associate a transaction without user confirmation.
Screenshot placeholder Counterparty selection, transaction preview, and confirmed HubSpot record association.
10 — Monitoring

Incoming payment monitoring

The integration can create a Wise profile-level webhook subscription for incoming payment state changes.

The monitored Wise event is:

account-details-payment#state-change

When an eligible webhook is received, the integration:

  1. Verifies the webhook signature using the Wise public key.
  2. Confirms the event type and connected Wise profile.
  3. Checks whether the webhook delivery has already been processed.
  4. Runs a targeted Wise transaction synchronization.
  5. Updates or creates the corresponding Wise Transaction record.
  6. Starts HubSpot invoice and commerce payment reconciliation.

Scheduled reconciliation

Webhooks are supplemented by scheduled reconciliation. The default schedule runs approximately every six hours.

This provides a secondary method for discovering eligible transactions if a webhook is delayed, missed, or received while the application is temporarily unavailable.

A manual synchronization can also be run from the integration settings page.

11 — Reconciliation

HubSpot invoice reconciliation

The integration reviews completed incoming Wise transactions and open HubSpot invoices.

Invoice reference match

The integration compares:

  • Wise payment reference or transaction description.
  • HubSpot invoice number.
  • Transaction amount.
  • Invoice amount.
  • Transaction currency.
  • Invoice currency.
Required reference-match conditions

The amount and currency must match. The invoice number must also appear in the Wise payment reference or transaction description.

Associated-record match

When a reliable invoice reference is unavailable, the integration may evaluate whether the transaction and invoice share the same associated:

  • HubSpot company, or
  • HubSpot contact.

The amount, currency, transaction date, and invoice date must also support the match.

An exact-date match is preferred. A limited seven-day date window may be used as a fallback when the transaction and invoice share the same company or contact.

Ambiguous matches are not processed

The reconciliation process is designed to avoid processing duplicate or ambiguous invoice matches.

12 — Commerce payments

HubSpot commerce payment creation

When an eligible incoming Wise transaction is matched with an open HubSpot invoice, the integration checks whether a commerce payment has already been created for that Wise transaction.

The payment reference uses the following structure:

WISE:{Wise transaction ID}

If no existing payment is found, the integration creates a HubSpot commerce payment containing:

  • Initial payment amount.
  • Payment date.
  • Currency.
  • Successful payment status.
  • Wire transfer payment method.
  • Wise transaction reference.
  • Wise counterparty information.
  • Matching invoice number.
  • Internal reconciliation comment.

The commerce payment is associated with the matching HubSpot invoice.

Invoice status

HubSpot may update the invoice status through its native commerce payment behaviour. The integration reads the resulting invoice status after creating the payment but does not directly overwrite the invoice status property.

13 — Permissions

HubSpot OAuth scopes

All HubSpot scopes listed below are requested during installation. There are currently no optional or conditionally required HubSpot scopes.

Scope Access Purpose
oauth HubSpot OAuth authorization Installs the integration, exchanges authorization codes, refreshes access tokens, and identifies the connected HubSpot account.
crm.objects.companies.read Read companies and associations Displays companies during manual association and reads company associations used during invoice reconciliation.
crm.objects.companies.write Update companies and associations Writes Wise company properties and creates associations between companies and Wise Transaction records.
crm.objects.contacts.read Read contacts and associations Displays contacts during manual association and reads contact associations used during invoice reconciliation.
crm.objects.contacts.write Update contacts and associations Writes Wise contact properties and creates associations between contacts and Wise Transaction records.
crm.schemas.companies.read Read company property definitions Determines whether required Wise company properties already exist.
crm.schemas.companies.write Create company property definitions Creates the Wise Integration property group and required company properties.
crm.schemas.contacts.read Read contact property definitions Determines whether required Wise contact properties already exist.
crm.schemas.contacts.write Create contact property definitions Creates the Wise Integration property group and required contact properties.
crm.schemas.custom.read Read custom object schemas Locates and validates the Wise Transaction custom object and its properties.
crm.objects.custom.read Read custom object records Reads Wise Transaction records for display, duplicate detection, association, and reconciliation.
crm.objects.custom.write Create and update custom object records Creates and updates normalized Wise Transaction records and their associations.
crm.objects.invoices.read Read HubSpot invoices Reads open invoices, invoice numbers, amounts, currencies, dates, statuses, and associations for payment matching.
crm.objects.commercepayments.read Read commerce payment records Checks whether a Wise transaction has already been represented by a HubSpot commerce payment.
crm.objects.commercepayments.write Create commerce payment records Creates a successful wire-transfer commerce payment and associates it with the matching invoice.

The integration does not request permission to read all HubSpot CRM data. HubSpot access is limited to the objects and schemas required for the documented functionality.

14 — Data processing

Shared data and processing direction

Data object Direction Purpose
Wise profiles Wise to integration Lists profiles and saves the profile selected for synchronization.
Wise recipients Wise to integration Displays available counterparty and recipient information.
Wise balances Wise to integration Verifies connected currencies and identifies statement sources.
Wise balance statements Wise to integration Retrieves transaction history for synchronization.
Wise transactions Wise to HubSpot Creates or updates normalized Wise Transaction records.
HubSpot companies HubSpot and integration service Reads company information and associations, then writes Wise properties and transaction associations.
HubSpot contacts HubSpot and integration service Reads contact information and associations, then writes Wise properties and transaction associations.
HubSpot custom objects HubSpot and integration service Reads existing Wise Transaction records and creates or updates transaction records and associations.
HubSpot invoices HubSpot to integration Reads invoice information and associations for reconciliation.
HubSpot commerce payments HubSpot and integration service Reads existing payments for duplicate prevention and creates matched Wise payment records.
Integration settings HubSpot user to integration Stores selected profile, synchronization preferences, and connection configuration.
Wise webhook events Wise to integration Notifies the integration of incoming payment state changes.
No current HubSpot-to-Wise record synchronization

No HubSpot company, contact, invoice, custom object, or commerce payment data is written back to Wise as part of the current transaction synchronization or invoice reconciliation process.

Data processed from Wise

Depending on availability in the Wise API response, the integration may process:

  • Wise profile ID, type, and display name.
  • Balance IDs and currencies.
  • Wise recipient IDs, names, and currencies.
  • Transaction and transfer IDs.
  • Transaction dates, amounts, and currencies.
  • Transaction directions, statuses, and types.
  • Counterparty names and account identifiers.
  • Payment references and transaction descriptions.
  • Fee information.
  • Webhook event type, delivery ID, and event time.
  • Wise OAuth scope and token expiration metadata.

The integration does not request or store a user’s Wise password.

Data processed from HubSpot

The integration may process:

  • HubSpot account ID.
  • HubSpot OAuth credentials and expiration metadata.
  • Company and contact record IDs.
  • Applicable Wise properties and record associations.
  • Wise Transaction custom object records.
  • Custom object schema information.
  • Invoice IDs, numbers, statuses, amounts, and currencies.
  • Invoice, due, and creation dates.
  • Invoice company and contact associations.
  • Commerce payment IDs, references, and statuses.
  • Integration settings and synchronization status.

The integration does not intentionally access HubSpot objects outside the scopes listed in this documentation.

15 — Storage and security

Application-side data storage and security

Application-side storage

The integration uses an application storage layer for authentication, configuration, mapping, and operational information.

The storage layer uses PostgreSQL when a database connection is configured. The application also contains a restricted JSON file storage fallback intended for local development.

The application may store:

  • HubSpot account ID.
  • HubSpot OAuth access and refresh tokens.
  • HubSpot token expiration and installation timestamps.
  • Wise connection status and permission mode.
  • Encrypted Wise access and refresh tokens.
  • Wise token expiration metadata.
  • Selected Wise profile ID, name, and type.
  • Synchronization history and display settings.
  • Manual counterparty mappings.
  • Last synchronization information.
  • Transaction ingestion status.
  • Webhook subscription metadata.
  • Webhook delivery identifiers used for duplicate prevention.
  • Operational errors and reconciliation status.

Normalized Wise transaction information is primarily stored in the customer’s HubSpot account as Wise Transaction records. The integration does not intentionally retain complete raw Wise balance statements after they have been processed.

Wise token storage

Wise access and refresh tokens are encrypted before they are written to application storage.

  • AES-256-GCM authenticated encryption.
  • A randomly generated initialization vector for each value.
  • An authentication tag to detect unauthorized modification.
  • An encryption key derived from a server-side secret.
  • A minimum encryption-secret length of 32 characters.

Wise tokens are decrypted only when required to make an authorized Wise API request.

HubSpot token storage

HubSpot OAuth access and refresh tokens are stored in restricted application storage and separated by HubSpot account ID.

HubSpot access tokens are refreshed automatically before expiry when a valid refresh token is available.

Application credentials, encryption secrets, and OAuth client secrets are stored as server-side environment secrets and are not returned to HubSpot users or browser clients.

Data transmission

Communication between the integration, HubSpot, and Wise occurs over HTTPS.

The integration sends authenticated API requests directly to:

  • HubSpot APIs.
  • Wise APIs.

Wise webhook requests are verified using the original request body and Wise’s RSA-SHA256 signature before the event is processed. Requests with missing or invalid signatures are rejected.

Webhook delivery retention

The integration stores webhook delivery identifiers to prevent the same event from being processed more than once.

Webhook delivery records are retained for up to 30 days and are limited to a maximum of 500 stored delivery records per connected HubSpot account. Older delivery records may be removed when either limit is reached.

General data retention

Active connection and configuration records are retained while needed to operate the integration. HubSpot CRM records created by the integration remain subject to the customer’s HubSpot account settings and retention policies.

Production retention details

Before publication, confirm the production application log retention period, database backup retention period, primary processing region, and deletion request completion period.

Security controls

  • HubSpot OAuth authentication.
  • Wise OAuth authentication.
  • Random OAuth state values.
  • Ten-minute Wise OAuth state expiration.
  • AES-256-GCM encryption for Wise tokens.
  • HTTPS communication.
  • Wise RSA-SHA256 webhook signature verification.
  • Portal-specific separation of connection records.
  • Automatic access-token refresh.
  • Removal of unusable Wise tokens when reconnection is required.
  • Duplicate webhook delivery detection.
  • Duplicate transaction detection.
  • Duplicate HubSpot commerce payment detection.
  • API request correlation IDs.
  • Idempotency identifiers for supported Wise write requests.
  • Restricted local storage file permissions.
  • HubSpot API throttling and retry handling.
  • Retry handling for temporary HubSpot and Wise service errors.
Compliance representations

No certification, audit standard, or regulatory compliance status should be inferred unless explicitly stated in published Atlantic Ops security or privacy documentation.

16 — Account management

Disconnecting and uninstalling

Disconnect Wise

Disconnecting Wise does not uninstall the HubSpot integration.

  1. Open the integration settings.
  2. Select Disconnect Wise.
  3. Confirm the disconnection.

Disconnecting Wise:

  • Stops new authenticated Wise API requests.
  • Clears the stored Wise access token.
  • Clears the stored Wise refresh token.
  • Clears token expiration metadata.
  • Clears selected profile connection metadata.
  • Records the disconnection time.
  • Stops future Wise synchronization until the account is reconnected.

Disconnecting Wise does not automatically delete:

  • Existing Wise Transaction records in HubSpot.
  • Existing company or contact Wise properties.
  • Existing transaction associations.
  • Existing HubSpot commerce payment records.
  • Existing HubSpot invoice associations.
  • Historical application synchronization records.

Disable incoming payment monitoring

Before disconnecting or uninstalling the integration, disable the incoming payment listener or remove the corresponding profile webhook subscription where the integration provides that option.

Removing a webhook subscription stops new Wise event deliveries. It does not delete transactions already synchronized into HubSpot.

Uninstall from HubSpot

  1. Disconnect the Wise account.
  2. Disable incoming payment monitoring.
  3. Open HubSpot connected app settings.
  4. Select the Wise Payments Integration.
  5. Choose Uninstall.
  6. Confirm the removal.

Uninstalling the integration:

  • Revokes future HubSpot API access.
  • Removes the CRM cards and settings interface.
  • Stops future synchronization and reconciliation.
  • Prevents the integration from updating HubSpot records.

Uninstalling does not automatically delete:

  • Wise Transaction custom object records.
  • Company or contact Wise properties.
  • Values stored in those properties.
  • CRM associations created by the integration.
  • HubSpot commerce payment records.
  • Commerce payment-to-invoice associations.
  • Existing invoice status changes resulting from native HubSpot payment processing.

Request application-side data deletion

Submit a deletion request through the Atlantic Ops contact page and include:

  • HubSpot account ID.
  • Company name.
  • Name and email address of the requesting administrator.
  • Confirmation that the requester is authorized to act for the HubSpot account.
  • Whether the request applies to configuration data, authentication data, mappings, logs, or all application-side data.

After validating the request, Atlantic Ops will delete eligible active application records associated with the HubSpot account. Deleting application-side data does not delete records stored directly in HubSpot.

Backup copies may remain until the documented backup retention period expires.

17 — Troubleshooting

Troubleshooting

HubSpot installation cannot be completed

Confirm that:

  • The installing user can install apps.
  • The selected HubSpot account supports the requested scopes.
  • The account includes the required custom object, invoice, and commerce payment features.
  • The integration has not been blocked by account security settings.

Wise will not connect

Confirm that:

  • The browser permits the Wise authorization window.
  • The Wise user has access to the required profile.
  • Authorization was completed within ten minutes.
  • The Wise account has not revoked the integration.
  • The correct Wise environment is being used.

When the integration displays Reconnect required, connect Wise again from the settings page.

No Wise profiles appear

  • Confirm that Wise is connected.
  • Confirm that the connected Wise user can access the expected profile.
  • Confirm that the connection test completes successfully.

No balances or currencies appear

  • Confirm that the correct Wise profile is selected.
  • Confirm that the profile contains eligible balances.
  • Confirm that the Wise connection has not expired or been revoked.

No transactions are synchronized

  • Confirm that the correct Wise profile is selected.
  • Confirm that the selected balance contains activity.
  • Confirm that the transaction history window includes the expected date.
  • Confirm that the connection test succeeds.
  • Run a manual synchronization.

Transactions are not visible on a company or contact

Synchronizing a transaction does not automatically associate it with a CRM record. Open the company or contact record and select the exact Wise counterparty through the integration card.

An invoice was not matched

Confirm that:

  • The Wise transaction is incoming.
  • The Wise transaction is completed.
  • The HubSpot invoice is open.
  • The amount and currency match.
  • The invoice number appears in the Wise payment reference or description.

When no invoice reference is available, confirm that:

  • The invoice and transaction share the same associated company or contact.
  • The payment and invoice dates fall within the allowed date range.
  • There is only one reasonable matching invoice.

A duplicate commerce payment appears

The integration checks for an existing payment reference using the Wise transaction ID before creating a commerce payment.

Contact support with the HubSpot account ID, Wise transaction ID, HubSpot payment record IDs, and HubSpot invoice ID.

A webhook is rejected

Wise webhooks are rejected when:

  • The signature is missing.
  • The signature cannot be verified.
  • The event is not associated with the connected profile.
  • The request is malformed.

Scheduled or manual reconciliation can be used to recover eligible transactions after a failed webhook delivery.

18 — FAQ

Frequently asked questions

Does the integration send money?

The current synchronization and invoice reconciliation process does not initiate a Wise transfer. Read-only mode prevents payment-changing Wise API requests. Read and create mode permits supported future or enabled Wise write actions but does not automatically send money.

Does the integration automatically create contacts or companies?

No. The current integration requires a user to associate an exact Wise counterparty with an existing HubSpot company or contact.

Does the integration store my Wise password?

No. Authentication occurs through Wise OAuth. The integration receives OAuth tokens, not the user’s Wise password.

Can several Wise profiles be synchronized?

One Wise profile is selected for a HubSpot account at a time. A user can change the selected profile, but historical records from the previous profile are not automatically deleted.

Are multiple currencies supported?

Yes. Transaction records retain the currency supplied by Wise. Invoice reconciliation requires the Wise transaction currency and HubSpot invoice currency to match.

Will disconnecting Wise delete my HubSpot data?

No. Disconnecting stops future Wise access and synchronization but preserves existing HubSpot records.

Will uninstalling the app delete synchronized transactions?

No. Existing HubSpot data remains unless a HubSpot administrator deletes it.

How are duplicate transactions prevented?

The integration uses the Wise transaction ID to locate previously synchronized transaction records.

How are duplicate commerce payments prevented?

The integration searches for a HubSpot commerce payment using the reference WISE:{Wise transaction ID} before creating another record.

How quickly will an incoming payment appear?

Signed Wise webhooks can trigger synchronization after a payment state change. Scheduled reconciliation also runs periodically as a fallback. Actual timing may be affected by Wise, HubSpot, hosting availability, and API rate limits.

19 — Support

Privacy, legal, and support

When contacting support, include the HubSpot account ID and a description of the affected Wise profile, transaction, company, contact, invoice, or commerce payment.

Do not send authentication credentials

Do not send Wise passwords, complete bank account numbers, OAuth tokens, API credentials, or other authentication secrets through a support request.

Contact Atlantic Ops support

Request assistance with installation, synchronization, Wise account connections, counterparty association, HubSpot invoice reconciliation, commerce payments, or application-side data deletion.

Contact support Wise integration overview
Privacy Policy Terms and Conditions Data deletion requests