Ellipse Gradient for Header

Wise Business Integration Guide

Connect Wise Business to enterprise finance applications through REST APIs, bearer tokens or OAuth 2.0, and selected webhook notifications.

Wise Business integration options at a glance

Wise Business primarily integrates through REST APIs covering Profiles, Balance accounts, Quotes, Transfers, and Recipients. Requests use bearer-token authentication, while OAuth 2.0 is available for supported applications that authorize access to customer accounts. Wise also provides webhook-style notifications for selected resources and events, particularly transfer processing, although coverage must be confirmed for each lifecycle requirement. Martini can consume these APIs, securely manage tokens or OAuth configuration, orchestrate quote and transfer workflows, receive supported webhook events, and schedule reconciliation when notifications are incomplete. Wise does not expose a confirmed GraphQL, SOAP, database, or general-purpose file integration model for core Business automation.

Integration pointSupported by Wise Business?Common use casesHow Martini supports it
REST APIsYesWise documents REST endpoints for Profiles, Balance accounts, Quotes, Transfers, Recipients, and related account operations.Martini can consume Wise REST endpoints, map request and response payloads, orchestrate dependent calls, and expose reusable APIs or workflows.
Webhooks / outbound callbacksLimitedWise supports notifications for selected resources and events, particularly some transfer state changes. Coverage must be checked for the required resource and lifecycle.Martini can receive supported Wise webhook requests, validate and deduplicate events, start workflows, and combine notifications with scheduled reconciliation.
Bulk / async / batch APIsLimitedSome Wise operations may be asynchronous and provide status-based processing, but a universal bulk API should not be assumed.Martini can persist operation identifiers, poll documented status endpoints, and coordinate asynchronous processing with retries and checkpoints.
AuthenticationYesWise supports bearer-token authentication and OAuth 2.0 for supported application authorization scenarios, with access subject to account, profile, region, and product permissions.Martini can store tokens, client configuration, and secrets in secure environment configuration and apply them to outbound API calls.
GraphQL APIsNot confirmedNo official Wise GraphQL API was identified for the core Wise Business integration model.Martini can consume GraphQL from other systems in a broader integration, but this is not a confirmed Wise integration mechanism.
SOAP APIsNoWise’s current documented integration model is REST-based rather than SOAP-based.Martini can consume SOAP services generally, but Wise integrations should use the documented REST API instead.
Database / analytics accessNoWise does not expose direct database access for customer integrations.Martini can persist synchronized Wise data in an approved enterprise database, but it cannot connect directly to Wise’s internal database.

How Wise Business exposes data and business events

Wise REST APIs

Wise Business provides REST endpoints for Profiles, Balance accounts, Quotes, Transfers, Recipients, and related account operations. The API is request/response oriented, and individual operations may have different acceptance, processing, and status-retrieval lifecycles.

Martini implementation pattern

Martini implementation pattern: Martini stores Wise authentication settings securely, calls the required endpoint sequence, validates responses, maps Wise payloads to canonical enterprise models, and persists identifiers and checkpoints for audit and reconciliation.

Implementation sequence

Authenticate the request with a Wise bearer token or supported OAuth configuration
Retrieve the applicable business Profile and required Balance account context
Validate recipient, currency, amount, and payment approval data
Create or retrieve a Quote and verify its validity
Create the Transfer using the required quote and Recipient information
Persist the Wise transfer identifier and originating payment key

Wise webhook notifications

Wise supports webhook-style notifications for selected resources and events, particularly some transfer processing changes. Notifications are selective, so required event coverage and delivery behavior must be confirmed for each integration.

Martini implementation pattern

Martini implementation pattern: Martini exposes a controlled receiving endpoint or workflow trigger, validates the incoming request according to Wise’s documented mechanism, records an event identifier, and performs downstream updates asynchronously where appropriate.

Implementation sequence

Receive the Wise webhook notification
Validate the request and identify the Wise resource and event
Check the event identifier or equivalent deduplication key
Retrieve the current Transfer state when the notification is insufficient
Map the status to the target application model
Acknowledge the event and route failures for retry or review

Scheduled Wise reconciliation

Scheduled retrieval is an important complement to Wise notifications because webhook coverage is not universal and financial integrations require completeness. Workflows can retrieve balances, transfers, and statuses at controlled intervals.

Martini implementation pattern

Martini implementation pattern: Martini schedules bounded API reads, follows the endpoint-specific pagination model, compares Wise identifiers and states with the originating system, and records checkpoints so missed events or incomplete processing can be corrected.

Implementation sequence

Start the scheduled reconciliation workflow
Load the last successful synchronization checkpoint
Retrieve paginated Wise Transfers or Balance accounts
Compare identifiers, amounts, currencies, recipients, and statuses
Apply reconciliation and exception rules
Persist the new checkpoint and publish unresolved exceptions

Common Wise Business integration patterns

Pattern 1: Orchestrate approved supplier payments

When to use this pattern

Use this pattern when an ERP or finance application approves a supplier payment and Wise should execute the cross-border transfer. The workflow should validate the request, confirm the recipient and currency requirements, protect against duplicate execution, and preserve the quote and transfer lifecycle for audit.

Integration direction
NetSuite
Martini
Wise Business
Example Mapping
Wise Business FieldCanonical FieldTarget Field
originatingPaymentIdpayment.externalIdWise customer reference or idempotency value where supported
sourceCurrencypayment.sourceCurrencyQuote source currency
targetCurrencypayment.targetCurrencyQuote target currency
amountpayment.amountQuote and Transfer amount
Martini implementation pattern

Martini receives the approved payment, validates business approval and required recipient data, resolves or creates the applicable Recipient where permitted, creates a Quote, checks validity and fees, submits the Transfer, and stores the Wise identifier. Duplicate requests are detected using the originating payment key, while transient failures are retried and uncertain outcomes are reconciled before another transfer is attempted.

Martini capabilities used
  • APIs
  • workflows
  • data mapping
  • business rules
  • secure configuration
  • error handling
  • scheduled reconciliation

Pattern 2: Synchronize Wise balances

When to use this pattern

Use this pattern for daily or intraday cash visibility across Wise business profiles and currency accounts. It supports treasury reporting, balance thresholds, and reconciliation against expected payments without direct database access to Wise.

Integration direction
Wise Business
Martini
PostgreSQL
Example Mapping
Wise Business FieldCanonical FieldTarget Field
profileIdaccount.ownerProfileIdWise profile reference
currencybalance.currencyCurrency code
amountbalance.availableAmountAvailable balance
balanceAccountIdbalance.externalIdExternal account identifier
Martini implementation pattern

A scheduled Martini workflow retrieves Profiles and Balance accounts, follows documented pagination where applicable, maps currency balances into a canonical model, writes the results to PostgreSQL or a reporting target, and applies threshold alerts. Checkpoints and idempotent upserts prevent duplicate snapshots, while API throttling and retries protect the Wise service.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • pagination handling
  • data mapping
  • database integration
  • business rules
  • monitoring

Pattern 3: Reconcile transfer statuses

When to use this pattern

Use this pattern when transfer completion, cancellation, failure, refund, or compliance-review states must be reflected in an accounting, payroll, or treasury platform. It is especially important when a required event is not covered by Wise webhooks or when delivery must be independently verified.

Integration direction
Wise Business
Martini
SAP S/4HANA
Example Mapping
Wise Business FieldCanonical FieldTarget Field
idpayment.wiseTransferIdWise transfer reference
statuspayment.processingStatusPayment lifecycle status
sourceValuepayment.amountPayment amount
targetCurrencypayment.currencyPayment currency
Martini implementation pattern

Martini retrieves transfer statuses on a controlled schedule, compares them with the originating payment record, and updates SAP only when the mapped state passes validation. The workflow records the last successful page or checkpoint, handles rate limits with backoff, detects mismatched amounts or recipients, and routes unresolved exceptions for finance review.

Martini capabilities used
  • scheduled workflows
  • REST API consumption
  • mapping and transformation
  • validation
  • idempotent updates
  • retry handling
  • operational monitoring

Pattern 4: Expose a normalized multi-currency payment API

When to use this pattern

Use this pattern when several internal applications need to initiate Wise payments without each one implementing Wise-specific request formats. A Martini API can provide a stable internal contract while the backend workflow applies entity, currency, recipient, approval, and funding rules.

Integration direction
Salesforce
Martini
Wise Business
Example Mapping
Wise Business FieldCanonical FieldTarget Field
paymentAmountpayment.amountWise quote and transfer amount
beneficiarypayment.recipientWise Recipient
fundingCurrencypayment.sourceCurrencyWise Quote source currency
destinationCurrencypayment.targetCurrencyWise Quote target currency
Martini implementation pattern

Martini exposes an authenticated API that accepts a normalized payment request, validates required fields and authorization, invokes Wise quote and transfer operations, and returns a controlled response containing the Wise identifier and processing state. The workflow separates accepted from completed payments, applies idempotency rules, and uses webhook or scheduled reconciliation updates for later lifecycle changes.

Martini capabilities used
  • API exposure
  • workflow orchestration
  • REST API consumption
  • data transformation
  • authentication and authorization
  • business rules
  • error handling

Applications commonly integrated with Wise Business

Wise Business can be integrated with finance, accounting, payroll, and operational applications where organizations need cross-border payments, multi-currency balances, or transfer reconciliation. These are architecture patterns rather than claims of native Wise partnerships; the exact objects and permissions depend on each application and account configuration.

Application Scenario Direction Martini Pattern
NetSuite Send approved supplier payments to Wise and reconcile transfer statuses, identifiers, and balances back to the ERP. NetSuite → Martini → Wise Business Martini receives approved payment instructions, validates recipients and amounts, creates or retrieves a quote, submits the transfer to Wise, persists the Wise transfer identifier, and sends status updates or reconciliation results back to NetSuite.
SAP S/4HANA Orchestrate international payments and synchronize payment outcomes with finance and treasury processes. SAP S/4HANA → Martini → Wise Business A Martini workflow normalizes SAP payment instructions, applies entity and currency rules, calls Wise REST endpoints for recipients, quotes, and transfers, and reconciles accepted, failed, cancelled, or completed states.
Xero Reconcile Wise balances and payment information with multi-currency accounting records. Wise Business → Martini → Xero Martini retrieves Wise Profiles, Balance accounts, and relevant transfer information, maps currencies and identifiers to Xero’s accounting model, and uses checkpoints and reconciliation rules to avoid duplicate entries.
QuickBooks Online Synchronize Wise account activity and payment information for financial reconciliation. Wise Business → Martini → QuickBooks Online Scheduled Martini workflows retrieve Wise balances and transfer statuses, transform currency and payment data, validate accounting references, and write approved results to QuickBooks Online while routing exceptions for review.
Workday Support international payroll or worker-related payment processes where Wise is used as a payment provider. Workday → Martini → Wise Business Martini validates Workday payment outputs, applies recipient and currency business rules, submits eligible transfers to Wise, stores identifiers securely, and returns processing outcomes for payroll reconciliation.
Salesforce Connect customer, partner, or operational payment processes with Wise transfer execution and status visibility. Salesforce → Martini → Wise Business A Martini API accepts normalized payment requests from Salesforce, orchestrates Wise quote and transfer calls, and exposes or pushes transfer status back to Salesforce after webhook or reconciliation processing.

How to build a Wise Business integration in Martini

Objective

Configure Wise access for the required business profile and API product without embedding credentials in workflow logic.

Instructions in Martini

  • Choose bearer-token authentication or a supported OAuth 2.0 authorization model.
  • Store tokens, client configuration, and secrets in Martini secure configuration.
  • Limit access to payment workflows and avoid logging credentials or sensitive bank details.
  • Confirm Wise account, profile, regional, and product permissions.

Objective

Select an event-driven, API-led, or scheduled entry point based on the payment or reconciliation requirement.

Instructions in Martini

  • Use an internal API for normalized payment requests.
  • Receive Wise webhook notifications only for confirmed supported events.
  • Use a scheduler for balance synchronization and transfer reconciliation.
  • Design a reconciliation fallback when webhook coverage is incomplete.

Objective

Call the Wise resources required to establish profile context, balances, quote information, recipients, transfers, or current statuses.

Instructions in Martini

  • Retrieve the applicable Profile and Balance account context.
  • Follow the endpoint-specific pagination model for list operations.
  • Persist checkpoints and external identifiers after successful reads.
  • Treat accepted transfer responses separately from completed payment outcomes.

Objective

Coordinate dependent Wise calls and enterprise-system actions in a maintainable Martini workflow.

Instructions in Martini

  • Validate the incoming request before creating financial instructions.
  • Sequence Recipient, Quote, and Transfer operations according to the Wise lifecycle.
  • Branch for approval failures, expired quotes, rejected requests, and uncertain outcomes.
  • Keep Wise-specific payloads isolated from the internal canonical payment model.

Objective

Convert Wise payloads into stable enterprise models for accounting, payroll, treasury, and reporting systems.

Instructions in Martini

  • Map currency, amount, identifier, recipient, quote, and status fields explicitly.
  • Apply country- and currency-dependent recipient rules.
  • Normalize Wise lifecycle states into the target application’s status model.
  • Version mappings when Wise schemas or endpoint behavior changes.

Objective

Persist payment, balance, and reconciliation results while preserving audit relationships between source and Wise identifiers.

Instructions in Martini

  • Store the originating payment key with the Wise transfer identifier.
  • Use idempotent upserts for accounting and reporting records.
  • Update ERP, payroll, treasury, or accounting systems only after validation.
  • Route mismatches and sensitive exceptions for controlled review.

Common Wise Business data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
ProfilesIdentify personal or business profiles and obtain the business profile context required for account operations.ERP, treasury platforms, accounting applications, reporting databasesMartini retrieves and validates profile identifiers, stores only required metadata, and uses the appropriate business profile in downstream workflow calls.
Balance accountsRepresent currency-specific balances held within a Wise profile and support cash visibility or threshold monitoring.ERP, treasury platforms, accounting applications, data warehousesMartini retrieves balances on a schedule or as part of reconciliation, maps currency and amount fields to a canonical model, and persists synchronization checkpoints.
QuotesCapture exchange-rate, pricing, fee, currency, amount, and quote-validity information for a transfer.ERP, payment approval systems, treasury platformsMartini creates or retrieves a quote, validates its currencies and expiration, applies approval rules, and passes the quote identifier into transfer processing.
TransfersRepresent payment instructions and their processing lifecycle between Wise balances or external recipients.ERP, payroll platforms, accounting applications, treasury systemsMartini creates transfers where permitted, persists Wise identifiers and originating payment keys, processes status events, and reconciles final outcomes.
RecipientsStore beneficiary or bank-account details used as transfer destinations, with requirements varying by country and currency.ERP, procurement applications, payroll platforms, payment approval systemsMartini validates country- and currency-dependent data, protects sensitive fields, and applies careful recipient-change and duplicate-payment controls.
WebhooksDeliver selected notifications about supported Wise resource changes, including some transfer state changes.Workflow engines, ERP, accounting applications, monitoring systemsMartini receives and validates event requests, records event identifiers for idempotency, starts downstream processing, and uses reconciliation to detect missed notifications.

Authentication and security considerations

Bearer tokens and OAuth 2.0

Wise Business supports bearer-token authentication and OAuth 2.0 for supported application authorization scenarios. Access depends on the Wise account, business profile, region, and API product permissions.

Secure Martini configuration

Store Wise API tokens, OAuth client configuration, and secrets in Martini secure configuration. Do not hard-code credentials or expose them in workflow logs.

Financial data controls

  • Restrict access to payment workflows and secrets.
  • Protect recipient and bank-account information.
  • Apply approval and segregation-of-duties controls before creating or funding transfers.
  • Use HTTPS for API communication and avoid logging full sensitive payloads.

Operational considerations for Wise Business integrations

Rate limits and retries

Confirm Wise quotas for the relevant account and API product. Handle HTTP 429 responses with controlled backoff and avoid high-frequency polling when webhook notifications are available.

Pagination and checkpoints

Follow the pagination mechanism documented for each Wise endpoint. Persist the last successful page or synchronization checkpoint for transfer and balance retrieval.

Idempotency and lifecycle

Protect payment creation with an originating payment identifier and a persisted Wise transfer identifier. Treat accepted, completed, failed, cancelled, refunded, and compliance-review states as distinct lifecycle outcomes.

Quotes and recipients

Quotes may expire, and recipient requirements vary by destination country and currency. Validate quote validity and recipient data immediately before transfer creation where appropriate.

Webhook reconciliation

Validate and deduplicate supported webhook events, then use scheduled reconciliation to detect missed notifications or incomplete downstream updates.

Schema and testing

Keep Wise-specific mappings versioned, avoid undocumented fields, and test endpoint, currency, country, and lifecycle variations before production deployment.

Why use Martini instead of scripts or point-to-point integrations?

Centralized orchestration

Martini coordinates Profiles, Balance accounts, Quotes, Recipients, and Transfers in one workflow instead of scattering payment logic across point-to-point scripts.

Reusable APIs and mappings

Martini can expose a normalized payment API, reuse Wise integration logic, and isolate Wise payloads from the data models used by ERP, accounting, payroll, and treasury applications.

Reliable operations

Workflows can combine webhook handling with scheduled reconciliation, checkpoints, validation, retries, idempotency controls, and operational monitoring.

Maintainable integration delivery

Martini provides a structured low-code development environment for API consumption, transformation, business rules, and deployment while retaining flexibility for custom integration logic when required.

Frequently asked questions

How can Wise Business be integrated with enterprise systems?

Wise Business is primarily integrated through REST APIs for Profiles, Balance accounts, Quotes, Transfers, and Recipients. Bearer tokens and supported OAuth 2.0 scenarios provide authentication, while selected webhook notifications and scheduled reconciliation can support transfer status updates and account synchronization.

Can Martini integrate with Wise Business?

Yes. Martini can integrate with Wise Business by consuming its REST APIs, securely managing bearer-token or OAuth configuration, orchestrating quote and transfer workflows, receiving supported webhook notifications, and running scheduled reconciliation workflows.

Do I need a connector to integrate Wise Business with Martini?

No dedicated Wise Business connector is required. Martini can use Wise’s confirmed native integration mechanisms, including REST APIs, bearer authentication, OAuth 2.0 where supported, selected webhook notifications, and scheduled API requests.

Is there any extra Lonti cost to integrate Wise Business with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Wise Business. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Wise, cloud infrastructure, or other third-party systems depending on subscription, usage, and deployment model.

Which Wise Business integration methods should be used?

REST APIs are the primary method for Wise Business automation. Typical workflows use Profiles, Balance accounts, Quotes, Recipients, and Transfers. Webhooks can be used for selected events, while scheduled retrieval remains important for reconciliation and event coverage gaps.

Are Wise Business webhooks available for transfer events?

Wise supports webhook-style notifications for selected resources and events, including some transfer state changes. Coverage is selective rather than universal, so the required event and lifecycle must be verified; Martini can combine supported notifications with scheduled reconciliation.

How does Martini handle Wise Business synchronization and data transformation?

Martini maps Wise objects into canonical enterprise models, preserves Wise identifiers, follows documented pagination, and stores synchronization checkpoints. Workflows can transform currencies, amounts, recipients, quotes, and lifecycle states for ERP, accounting, payroll, treasury, or reporting systems.

How are duplicate payments, errors, and retries handled?

Payment workflows should use an originating payment identifier, persist the Wise transfer identifier, and apply Wise-supported idempotency or reference mechanisms where available. Martini can validate requests, retry transient failures with controlled backoff, avoid duplicate webhook processing, and reconcile uncertain outcomes before retrying a payment.

Related Martini documentation

Martini APIs

Workflows

Security

Operations

Build a Wise Business integration with Martini

Use Martini to connect Wise Business REST APIs and selected webhook events with your finance, accounting, payroll, treasury, and operational systems through secure workflows, reusable APIs, data mapping, and reconciliation.

EXPLORE MARTINI
BOOK A DEMO