Wise Webhooks API
Subscribes a partner application to event notifications for transfers, balances, cards, and profile-state changes. Supports creating, listing, and deleting webhook subscriptions and verifying signed payloads.
OpenAPI Specification
openapi: 3.1.0
info:
title: Wise Platform API
version: ''
description: >
The Wise Platform API is a REST-based interface that enables programmatic
access to Wise's payment infrastructure. All endpoints return JSON-formatted
responses and use standard HTTP methods and status codes.
{% admonition type="success" name="New to wise?" %}
We strongly recommend first reading our **[Getting Started Guide](/guides/developer/index.md)** to help you set up credentials and make your first call.
{% /admonition %}
Before you begin {% .title-2 .m-t-5 %}
To use this API reference effectively, you should have:
- Received Valid [API credentials from
Wise](/guides/developer/auth-and-security/index.md) (Client ID and Client
Secret)
- Understand OAuth 2.0 authentication
- Be familiar with RESTful API concepts
Core API resources {% .title-2 .m-t-5 .m-b-0 %}
| Resource | Purpose |
|----------|---------|
| **[Quote](/api-reference/quote)** | Exchange rate and fee calculations |
| **[Recipient](/api-reference/recipient)** | Beneficiary account management
|
| **[Transfer](/api-reference/transfer)** | Payment creation and execution |
| **[Balance](/api-reference/balance)** | Multi-currency account operations
|
| **[Profile](/api-reference/profile)** | Account ownership details |
| **[Rate](/api-reference/rate)** | Current and historical exchange rates |
**Not sure which workflow to build?**<br>
Start with our [Integration
Guides](/guides/product/send-money/use-cases/index.md) for step-by-step
implementation examples.{% .m-t-3 .m-b-5 %}
servers:
- url: https://api.wise.com
description: Production Environment
- url: https://api.wise-sandbox.com
description: Sandbox Environment
tags:
- name: 3ds
x-displayName: 3D Secure Authentication
description: >
To manage certain aspects of the 3D Secure (3DS) authentication, you will
need to integrate with the following APIs.
- name: activity
x-displayName: Activity
description: |
Activity represents a snapshot of a performed action for a profile.
- name: verification
x-displayName: Additional Verification
description: >
In certain situations, additional evidence is required to verify customers
and ensure we’re compliant with the KYC regulations.
Additional Verification APIs support a list of evidences that can be found
in the [Supported Evidences
guide](/guides/product/kyc/partner-kyc/supported-evidences).
If you use the [Customer Account with Partner
KYC](/guides/product/kyc/partner-kyc) model and your customers are
primarily based in the EU,
refer to this [Onboarding EU
customers](/guides/product/kyc/partner-kyc/additional-verification#onboarding-eu-customers)
guide
for instructions on how to use these APIs.
If you use the [Customer Account with Partner
KYC](/guides/product/kyc/partner-kyc) model and you are onboarding high
risk business customers
based primarily based in the US, refer to
this [Onboarding High Risk US
Businesses](/guides/product/kyc/partner-kyc/additional-verification#onboarding-high-risk-us-businesses)
guide for
instructions on how to use these APIs.
- name: address
x-displayName: Addresses
description: >
Manage physical addresses associated with user profiles.
Address requirements vary by country — use the address requirements
endpoints to dynamically discover which fields are needed before creating
an address.
- name: balance
x-displayName: Balances
description: >
Create and manage balance accounts within a multi-currency account.
Each profile can hold multiple balance accounts in different currencies. A
`STANDARD` balance is limited to one per currency, while `SAVINGS`
balances (Jars) allow multiple in the same currency. Creating the first
balance for a profile automatically creates the multi-currency account.
Balances include an `investmentState` field. Only balances with
`NOT_INVESTED` can be operated on via the API. Invested balances should be
shown but not actionable.
For a complete guide on multi-currency accounts, see [Multi-Currency
Accounts](/guides/product/accounts).
- name: balance-statement
x-displayName: Balance Statements
description: >
Balance statements contain transactional activities on a Wise
Multi-Currency Account, including deposits, withdrawals, conversions, card
transactions, and fees.
Statements can be retrieved in multiple formats: JSON, CSV, PDF, XLSX,
CAMT.053, MT940, or QIF.
- name: bank-account-details
x-displayName: Bank Account Details
description: >
Bank account details allow users to receive money into their Wise
Multi-Currency Account. Each currency balance can have local bank details
(for domestic payments) and international bank details (for SWIFT
payments) where available.
Bank account details can be retrieved for existing balances, or new
details can be ordered for currencies where they're available but not yet
issued.
- name: batch-group
x-displayName: Batch Payment Groups
description: >
A batch group is a named collection of up to 1000 transfers that can be
managed as a single unit. Batch groups are primarily used for funding
multiple transfers with a single payment.
**Workflow:**
1. Create a batch group with a source currency
2. Add transfers to the group (up to 1000)
3. Complete the batch group to close it for modifications
4. Fund the batch group from a balance or via direct debit
Individual transfers in the group follow standard transfer lifecycle and
can be tracked separately.
- name: bulk-settlement
x-displayName: Bulk Settlement
description: >
Bulk settlement allows partners to settle multiple transfers in a single
bank transfer at the end of a settlement period. This model splits
transfer creation/funding from final settlement, allowing Wise to process
transfers before receiving funds based on a partner's guarantee.
Use the settlement journal endpoint to submit a list of transfers to be
settled, along with the settlement reference that matches your bank
transfer payment.
- name: card
x-displayName: Cards
description: >-
Manage your customers' cards programmatically. These APIs allow you to
list cards, retrieve card details, control card status, and manage
spending permissions.
**Key capabilities:**
- List and retrieve card details for a profile
- Update card status (active, frozen, blocked)
- Control spending permissions (e-commerce, ATM, contactless, magnetic
stripe, etc.)
- Reset PIN attempt counter after incorrect PIN entries
- Update card phone number for verification purposes
{% admonition type="info" %}
For accessing sensitive card data (PAN, CVV, PIN), see the [Sensitive Card
Details API](/api-reference/card-sensitive-details). For ordering new
cards, see the [Card Orders API](/api-reference/card-order). For
transaction history, see the [Card Transactions
API](/api-reference/card-transaction).
{% /admonition %}
- name: card-sensitive-details
x-displayName: Sensitive Card Details
description: >-
Wise is a PCI DSS compliant provider and stores all card data securely.
The scope for PCI compliance depends on your use case and will impact how
you integrate. For all sensitive card details endpoints, follow the
[detailed guide](/guides/product/issue-cards/sensitive-card-details).
**Key capabilities:**
- Access sensitive card data (PAN, CVV, PIN) via encrypted JWE payloads
**Related operations:**
- For card management (list, status, permissions), see the [Cards
API](/api-reference/card)
- For ordering new cards, see the [Card Orders
API](/api-reference/card-order)
- For transaction history, see the [Card Transaction
API](/api-reference/card-transaction)
- name: card-kiosk-collection
x-displayName: Card Kiosk Collection
description: >
These APIs are designed to allow you to print and encrypt your card
directly from a kiosk machine. The card information will be sent to our
card manufacturer to configure and print the card on-site on a kiosk
machine.
The card printing process will automatically begin once the request is
received by our card manufacturer.
During the printing process, you will be notified via webhook about any
[card production status
change](/guides/developer/webhooks/event-types#cards-card-production-status-change).
Before using these APIs, make sure to read the guide on [kiosk
collection](/guides/product/issue-cards/card-kiosk-collection#card-kiosk-collection).
{% admonition type="warning" %}
Please reach out to your Implementation Manager for more information on
these APIs.
{% /admonition %}
**Testing**: In the sandbox environment, use the [card production
simulation API](/api-reference/simulation/simulationcardproduction) to
test your integration with various production statuses and error
scenarios.
Production status flow {% .title-2 .m-t-5 %}
These statuses represent the lifecycle of a card production:
- `READY` - Card is ready for production. The [produce card
endpoint](/api-reference/card-kiosk-collection/cardkioskcollectionproduce)
can be called.
- `IN_PROGRESS` - Card is being produced at the kiosk machine (chip
encryption and printing in progress).
- `PRODUCED` - Card has been successfully produced and collected from the
kiosk. This is a final state.
- `PRODUCTION_ERROR` - Card production failed. Check the errorCode to
identify the issue, resolve it, then retry using the [produce card
endpoint](/api-reference/card-kiosk-collection/cardkioskcollectionproduce).
A card with production status `PRODUCED` will trigger an asynchronous call
to update the associated card order to `PRODUCED` status.
- name: card-order
x-displayName: Card Orders
description: >
With this set of APIs, you will be able to create cards for your
customers. You can also retrieve and view the status of your current card
orders, as well as the list of available card programs for the user.
{% admonition type="info" %}
On production, each personal profile can order at most 1 physical card and
3 virtual cards. On sandbox, we allow up to 10 physical cards and 30
virtual cards for testing purpose. However, no more than 3 virtual cards
can be ordered per day. This limit includes cards and card orders.
{% /admonition %}
Card order status flow {% #card-order-status-flow .title-3 .m-t-5 %}
The card order response will contain the `status` field. The initial
status is `PLACED` or `REQUIREMENTS_FULFILLED` depending on the
requirement fulfillment state:
- `PLACED` - The card order is created. The card will be generated once it
has fulfilled all the requirements
- `REQUIREMENTS_FULFILLED` - The card order has fulfilled all the
requirements and the card should be generated in a short while
- `CARD_DETAILS_CREATED` - The card has been generated
- `PRODUCED` - The physical card has been produced and waiting to be
picked up by delivery vendor (physical card only)
- `COMPLETED` - The card has been activated and is ready to use. The card
order is completed
- `CANCELLED` - The card order has been cancelled. This can happen if you
reach out to Wise Support to cancel a card order
- `RETURNED` - Delivery failed, the physical card has been returned and
will be blocked (physical card only)
- name: card-transaction
x-displayName: Card Transactions
description: >-
Retrieve information on transactions made on your users' cards.
Transaction types {% #card-transaction-type .title-3 .m-t-5 %}
The possible `type` values are:
- `ACCOUNT_CREDIT` - Receiving money on the card, excluding Visa OCT or
Mastercard MoneySend
- `ACCOUNT_FUNDING` - Sending money to another card or e-wallet
- `CASH_ADVANCE` - Cash disbursement
- `CASH_WITHDRAWAL` - ATM withdrawal
- `CHARGEBACK` - Currently unused. Reserved for future use
- `CREDIT_TRANSACTION` - Visa OCT and Mastercard MoneySend
- `ECOM_PURCHASE` - Online purchase
- `POS_PURCHASE` - Purchase via a POS terminal
- `REFUND` - Partial or full refund of an existing card transaction
Transaction states {% #card-transaction-state .title-3 .m-t-5 %}
The possible `state` values are:
- `IN_PROGRESS` - The transaction has been authorized but not captured
- `COMPLETED` - The transaction has been captured and/or settled
- `DECLINED` - The transaction has been declined
- `CANCELLED` - The transaction has been cancelled
- `UNKNOWN` - Default fallback status if the state cannot be confirmed
The transition from `CANCELLED` to `COMPLETED` is an edge case. Wise
releases the customer funds after 7 days (30 days for pre-authorization)
if the merchant has not captured the transaction, and the state becomes
`CANCELLED`. However, the merchant can decide to capture the transaction
at a later date, at which point the state will become `COMPLETED`.
Decline reasons {% #card-transaction-decline-reasons .title-3 .m-t-5 %}
The decline reason field provides information about the specific issue
that led to the transaction being declined, helping the merchant and the
customer troubleshoot the problem.
While the decline reason field provides valuable information, it may not
cover all possible reasons for a decline, such as technical issues or
unforeseen circumstances.
{% admonition type="warning" %}
New decline reasons may be added in the future, and not all decline
reasons are currently documented. Review this documentation regularly to
ensure accuracy.
{% /admonition %}
{% admonition type="warning" %}
Exercise caution when communicating decline reasons to your customers, as
some may not be relevant or may cause confusion.
{% /admonition %}
- `ACCOUNT_INACTIVE` - Balance related to the transaction is not active.
Ensure that all outstanding actions have been completed before using the
card, as this may help avoid potential issues or declines
- `ACCOUNT_SUSPENDED` - The transaction has been declined pending further
compliance checks. It may have been flagged for potential sanctions issues
- `ATM_PIN_CHANGE_NOT_ALLOWED` - PIN change via ATM terminal is not
allowed
- `BLOCKED_COUNTRY` - Transactions were made in unsupported countries.
Check this
[link](https://wise.com/help/articles/2935771/where-can-i-use-my-wise-card)
to see if the country is included in the list of supported nations. It is
possible for a merchant to be based in a supported country and have an
address registered in a blocked country, albeit infrequently
- `BLOCKED_SUBSCRIPTION` - The system cannot facilitate this transaction
as the customer has opted out of recurring payments with this merchant
- `CARD_EXPIRED` - The card provided has reached its expiration date,
making it invalid for this transaction
- `CARD_FROZEN` - The customer or the customer service team has put this
card on a temporary hold. If the card has not been frozen by the customer,
it may be worth investigating further. To resume spending, advise the
customer to unfreeze the card
- `CARD_INACTIVE` - The card is either not active or has not been received
by the customer, so the transaction cannot proceed
- `CARD_BLOCKED` - The card has been blocked and cannot be used anymore
- `CARD_PARTNER_SUSPENDED` - The internal team has deactivated the account
for compliance reasons related to AML, fraud, or EDD. Contact the team if
this is believed to be an error
- `CHIP_PIN_ENTRY_TRIES_EXCEEDED` - The PIN is restricted on the chip of
the card due to excessive incorrect entries. The blocked PIN can be
unlocked at an ATM using specific steps that vary depending on the machine
and country, such as PIN management or PIN operations followed by
unblocking the PIN
- `CONNECTION_ISSUE` - A connection problem occurred during the
transaction
- `CONTACTLESS_PIN_ENTRY_REQUIRED` - Contactless payment systems sometimes
require a PIN for authentication purposes to protect users' accounts from
potential fraud or tampering. In Europe, contactless payment transactions
that follow one after the other require PIN verification as an additional
security measure
- `CREDIT_TRANSACTIONS_NOT_SUPPORTED` - Credit is not supported for this
specific transaction. Review the [Acceptable Use
Policy](https://wise.com/gb/legal/acceptable-use-policy-eea) for further
information
- `CUMULATIVE_LIMIT_EXCEEDED` - In certain jurisdictions, there are
restrictions on the amount that can be spent. Refer to [spending
limits](https://wise.com/help/articles/2899986/what-are-my-spending-limits)
for further details
- `DECLINED_ADVICE` - There is a problem with the message from the
processor, so it might not be accepted because it could be incomplete or
unsafe. This does not indicate a problem with the card. Advise the
customer that there was a technical issue with the payment and to try
again later
- `INCORRECT_CVV` - The customer entered the wrong security code. Advise
the customer to check their card details and try again. If the saved card
details are correct, they should remove their card details from the
merchant's website and add them back again
- `INCORRECT_EXPIRY_DATE` - The customer entered the wrong expiration date
for their card. If the saved card details are correct, they should remove
their card details from the merchant's website and add them back again
- `INCORRECT_PIN` - The customer entered their PIN incorrectly. Advise the
customer to check their PIN and try again. If the PIN is correct and still
fails, suggest resetting the PIN
- `INSUFFICIENT_FUNDS` - The customer does not have enough money in their
account to make the payment. Advise the customer to add money to their
account and try again. In most cases, this will resolve the issue
- `INVALID_3DS_UCAF` - The 3D Secure checks failed during the transaction.
The customer should try again and request authentication
- `INCORRECT_ARQC` - ARQC (Authorization Request Cryptogram) is a
cryptogram generated by the card during a transaction, which is validated
on the server side. If incorrect, it could indicate a faulty card, a
fraudulent attack, or an issue with the POS terminal
- `INCORRECT_ICVV` - ICVV (Integrated Circuit Card Verification Value) is
a security feature used to validate the authenticity of a card during
chip-based transactions. There were problems reading the chip on the card,
which may indicate an issue with the card's chip, the terminal, or the
transaction process. Wait and try again
- `INVALID_MERCHANT` - Transaction from a specific merchant is declined by
scheme. The merchant should clarify the exact cause with the scheme
- `INVALID_TRANSACTION` - Certain types of transactions are not supported.
The customer should ask the merchant to use a different payment method or
try a different merchant
- `MANDATE_DCC_NON_SUPPORTED_FOR_CARD_COUNTRY` - The transaction was
declined because the system does not support conversions for Brazilian
cards when BRL is involved. BRL will not be automatically exchanged to
other currencies. If the customer wants to continue with the payment, they
need to change the currency
- `MANDATE_LOCAL_CASH_WITHDRAWAL_NOT_ALLOWED` - ATM withdrawal services
are not provided in the country where the transaction is taking place
- `NON_SUPPORTED_CURRENCY` - The currency in this transaction is not
supported
- `NON_SUPPORTED_MCC_FOR_COUNTRY` - Transactions in this category are not
supported for customers in the country of purchase. Consider using an
alternative payment method or changing merchant
- `PAYMENT_METHOD_DAILY_LIMIT_EXCEEDED` - The customer has reached the
daily spending limit for the card or their profile. Advise if they would
like to update [card](/api-reference/spend-limits/spendlimitscardupdate)
or [profile](/api-reference/spend-limits/spendlimitsprofileupdate) limit
- `PAYMENT_METHOD_LIFETIME_LIMIT_EXCEEDED` - The customer has reached the
lifetime spending limit. Advise if they would like to
[increase](/api-reference/spend-limits/spendlimitscardupdate) their
lifetime limit
- `PAYMENT_METHOD_MONTHLY_LIMIT_EXCEEDED` - The customer has reached the
monthly spending limit for the card or their profile. Advise if they would
like to update [card](/api-reference/spend-limits/spendlimitscardupdate)
or [profile](/api-reference/spend-limits/spendlimitsprofileupdate) limit
- `PAYMENT_METHOD_NOT_ALLOWED` - This payment type has been disabled.
Advise if they would like to
[enable](/api-reference/card/cardpermissionsbulkupdate) the payment type
- `PAYMENT_METHOD_TRANSACTION_LIMIT_EXCEEDED` - The customer has exceeded
the transaction limit for the card. Advise if they would like to update
their [card](/api-reference/spend-limits/spendlimitscardupdate) limit
- `PIN_ENTRY_TRIES_EXCEEDED` - The customer has reached the maximum number
of allowed online PIN entry attempts. Consider implementing a [reset
PIN](/api-reference/card/cardpincountreset) feature within the app to help
the customer regain access to their card
- `PRE_ACTIVATED_CARD_PIN_ENTRY_REQUIRED` - The customer has attempted to
make a contactless payment at a POS or ATM, but their card has not been
activated for chip and PIN transactions. To modify the card activation
strategy for all cards, contact the implementation manager
- `PROCESSING_ERROR` - The system is currently experiencing technical
difficulties. Advise the customer to try again after a brief period
- `RESTRICTED_MODE` - Although rare, restricted mode can occur. Advise the
customer to replace their card promptly as the system should have already
informed them. In this mode, more secure payment methods like chip and
PIN, contactless, mobile wallets, and online payments with 3DS are
allowed, while less secure methods like magnetic stripe and online
payments without 3DS are not permitted
- `REVERSAL_NOT_MATCHING_AUTH_CURRENCY` - The merchant has issued a
reversal instruction for a different currency than what was originally
requested during the authorization process
- `SCA_SOFT_DECLINE` - The transaction cannot proceed due to SCA
regulations. Suggest the customer contact the merchant and use a more
secure authentication method such as 3DS. For example, the customer can
try chip and PIN, or a mobile wallet like Apple Pay or Google Pay
- `SCHEME_BLOCKED_TRANSACTION` - This transaction has been flagged by the
scheme and cannot be processed
- `SECURITY_CVM_FAILURE` - The system has detected that the POS terminal
was misconfigured and failed security checks. Suggest the customer use an
alternative payment method like contactless or mobile wallets, or
recommend asking the merchant to accept a signature instead
- `SECURITY_MAGSTRIPE_SECURE_ELEMENTS_INCORRECT_OR_MISSING` - The merchant
has entered the wrong type of purchase. Advise the customer to contact the
merchant and ask them to correct this issue
- `SECURITY_PIN_ENTRY_REQUIRED` - To proceed with this transaction, the
customer is required to enter their PIN
- `SUSPECTED_FRAUD` - This transaction has been labeled as high-risk by
Wise
- `SUSPECTED_FRAUD_AML` - This transaction has been flagged as high-risk
based on AML compliance protocols. This reason cannot be disclosed to end
customers
- `SUSPECTED_FRAUD_COMPLIANCE` - The compliance system has flagged this
transaction as high-risk. This reason cannot be disclosed to end customers
- `SUSPECTED_FRAUD_CORE_FRAUD` - This transaction has been blocked based
on fraud policies and procedures
- `SUSPECTED_FRAUD_SANCTIONS` - This transaction has been flagged as
high-risk based on sanctions list analysis. This reason cannot be
disclosed to end customers. This classification is final and cannot be
appealed
- `SUSPECTED_FRAUD_SOFT_DECLINE` - This e-commerce transaction cannot be
processed due to high risk factors. The merchant must complete 3DS before
the transaction can be approved
- `TRANSACTION_TYPE_NOT_SUPPORTED` - There are restrictions on this type
of transaction, and sometimes the scheme will not allow it. Check if
[spend control](/api-reference/spend-controls) is set up to block this
transaction
- `UNEXPECTED_ERROR` - There may have been a communication error between
the merchant's system and the server, but the POS system may have already
notified the user of this issue
Detailed decline reasons {% #card-transaction-detailed-decline-reasons
.title-3 .m-t-5 %}
Detailed decline reasons provide secondary level information for certain
decline reasons, adding more context to transaction failures.
Please be aware that new detailed decline reasons may be added in the
future, and not all reasons are currently documented. Therefore, it is
important to exercise caution and regularly review the documentation to
ensure accuracy.
{% admonition type="warning" %}
Please exercise caution when communicating reasons to your customers, as
some may not be relevant or may cause confusion. If you have any questions
or concerns, we are here to assist you.
{% /admonition %}
- `INSUFFICIENT_FUNDS_FOR_BLOCKED_SMART_CONVERSION` - Transaction was
declined due to insufficient balance in transaction currency when smart
conversion feature is disabled (e.g. BRL cards). The customer needs to
convert their funds to the transaction currency and try again.
- `INSUFFICIENT_FUNDS_FOR_SPECIFIC_CURRENCY_RESERVATION` - The transaction
will be declined with this reason if the customer's card is issued in a
region subject to smart conversion limitations, and the transaction
currency is the limited currency but the customer doesn't hold enough of
that currency. Other currencies won't be automatically converted to the
limited currency. The customer needs to convert their funds to the
transaction currency before retrying the payment.
- `SUSPECTED_FRAUD_NO_BALANCE` - The customer might be abusing merchants
by saving a card without having any balance to cover upcoming charges from
them. The customer will need to top up their account to cover any charges
from the merchant at a later date before re-attempting the transaction.
- `RESET_YOUR_PIN_AT_ATM` - There's a problem with how Chip was read and
we had to decline the transaction. The customer will need to reset their
PIN at an ATM.
- `INCORRECT_CVV2` - Invalid CVV2 was provided. The customer needs to
check their saved card details and if they're correct, they should remove
and add their card details to the merchant's website again. If this
doesn't help, they could try to use their card at another merchant's
website. If the same issue happens, they'll need to order a new card.
- `SCA_SOFT_DECLINE_CONTACTLESS` - Contactless transaction could not be
approved due to SCA regulations. The customer should perform at least one
PIN transaction or use an ATM to reset PIN.
- `SUSPECTED_FRAUD_REVIEW_ACTIVITY` - We couldn't confirm all transactions
in the customer's activity were done by them, so we froze their card. The
customer should review recent transactions and unfreeze the card.
- `INVALID_TRANSACTION_TYPE_FINAL` - This decline reason is used for
unmapped processor or network error codes, indicating an external system
issue or unclassified response. The decision authority on the transaction
information identifies a SCHEME decline, which may relate to card usage in
unsupported countries. The customer will need to use an alternative
payment method to complete this transaction.
- `INVALID_TRANSACTION_TYPE_CONTACTLESS_MAGSTRIPE` - The POS terminal used
a deprecated and not secure way to transmit card data. The customer will
need to use another POS machine or try another payment method (Chip and
PIN or Mobile Wallet).
- `INVALID_TRANSACTION_TYPE_FALLBACK` - The chip couldn't be read due to a
technical issue which resulted in the transaction "falling back" to
magnetic stripe. As damaging the chip (so it would fall back to stripe) is
a common way of fraud, these types of transactions are often deemed risky
and being blocked.
The customer will need to:
- Try again or try a different terminal / ATM if it still doesn't work
- Use another payment method, e.g. Contactless
- Use another card
- If the issue persists with multiple terminals, they'll need to replace their card as it may be damaged
- `CONTACTLESS_DISABLED` - `POS_CONTACTLESS` permission (contactless
payments) is disabled. The customer will need to enable the permission to
allow contactless transactions.
- `ECOM_DISABLED` - `ECOM` permission (online payments) is disabled. The
customer will need to enable the permission to allow e-commerce
transactions.
- `CHIP_DISABLED` - `POS_CHIP` permission (Chip transactions) is disabled.
The customer will need to enable the permission to allow Chip
transactions.
- `MAGSTRIPE_DISABLED` - `POS_MAGSTRIPE` permission (magnetic stripe
transactions) is disabled. The customer will need to enable the permission
to allow magnetic stripe transactions.
- `WALLET_DISABLED` - `MOBILE_WALLETS` permission is disabled. The
customer will need to enable the permission to allow mobile wallet
transactions.
- `PROFILE_GENERAL_DAILY_LIMIT_EXCEEDED_CHANGEABLE` - The customer has
reached their daily total account limit (profile-level). The customer will
need to edit the limit.
- `PROFILE_GENERAL_MONTHLY_LIMIT_EXCEEDED_CHANGEABLE` - The customer has
gone over their monthly total account limit (profile-level). The customer
will need to edit the limit.
- `CARD_GENERAL_DAILY_LIMIT_EXCEEDED_CHANGEABLE` - The customer has
reached their daily limit for this card (card-level). The customer will
need to edit the limit.
- `CARD_GENERAL_MONTHLY_LIMIT_EXCEEDED_CHANGEABLE` - The customer has gone
over the monthly limit for this card (card-level). The customer will need
to edit the limit.
- `PAYMENT_METHOD_MAX_MONTHLY_LIMIT_EXCEEDED` - The card's maximum
non-changeable monthly spending limit has been reached. The customer will
need to wait until the start of the next calendar month to perform
transactions
# --- truncated at 32 KB (1178 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/wise/refs/heads/main/openapi/wise-platform-openapi.yml