How to Use Wise to Pay International Invoices with a US Credit Card

What this guide helps you avoid#

If you want to pay a Wise invoice with a credit card, start by choosing the right flow, not the card. The first decision is whether you are paying a supplier or collecting from a customer, because those are separate jobs in Wise.

Identify whether you are paying out or collecting in.

Separate an outgoing transfer you create to settle a supplier invoice from a supplier’s own Wise Business invoice checkout. The latter can offer direct card payment when the supplier already has card receiving enabled. Collecting from your clients uses that receiving setup, not your outgoing-transfer funding rules.

• For a supplier’s ordinary invoice, create an outgoing transfer and use card funding only if the final payment-method screen offers it for your source currency, address, card, and amount.
• For an invoice issued through Wise Business, follow its Pay now checkout and check the methods enabled by the supplier.
• To collect client card payments yourself, you need existing enabled Wise Business card receiving; the feature is currently unavailable to new Wise Business customers.

Receiving fees and transfer-funding fees are different. An enabled U.S.-based Wise Business charges receiving fees according to the customer’s card class; those merchant fees do not tell you what it costs to fund your own outgoing payment. The receiving section below keeps that comparison separate.

Make a go or no-go decision before you try card funding.

For payer-side card funding, make that decision before the due-date window gets tight. Waiting until the invoice is due can turn avoidable failures into late-payment risk. Check the basics first:

• Use an accepted network: Visa, Mastercard, or supported Maestro. AMEX and Discover are not accepted for transfer funding.
• Have the card number, expiry date, CVV, and working 3D Secure authentication ready.
• Use a card in your or your business’s name; a Wise Business transfer requires a business card, not a personal card or personal bank account.
• For USD funding, check account-address restrictions and card-payment limits as well as the options shown at checkout.
• Compare the final Wise fee, issuer charges, and recipient delivery estimate before approving.

Use one repeatable routine.

A good process here is simple: decide the flow, confirm eligibility, verify the invoice, and keep the record. Use a consistent routine instead of improvising at the last minute.

1. Name the flow first: payer-side transfer or business receiving.
2. Check card eligibility and cost tradeoffs before payment day.
3. Confirm invoice details before submitting.
4. Save payment records and any failure message for reconciliation and fast fallback.

Related: Value-Based Pricing: A Freelancer's Guide.

Know which Wise flow you are using before you click#

The cleanest way to avoid payment mistakes is to separate paying bills from collecting money. In Wise, those jobs use different tools and checks.

Classify the payment job first.

For an ordinary supplier invoice, verify the payee’s bank details independently and create a transfer in Wise. When funding from USD, the USD transfer guide lists ACH, wire, card, and Wise-balance options, subject to availability. It explicitly excludes cash, checks, and bill payments; a U.S.-addressed account also cannot fund its USD transfer by Swift. A supplier’s Wise-issued invoice has its own checkout instead.

If you are paying a bill, save the payment confirmation after the payment completes for audit and reconciliation.

Treat client collection as a separate receiving setup.

For collection by payment link, Wise requires at least one set of account details. A customer without a Wise account can pay only in a currency for which you have account details. Card collection additionally requires existing enabled access and is currently unavailable to new Wise Business customers.

A single-use payment link accepts one payment and expires after 30 calendar days. Check whether a late customer needs a fresh request.

Split ownership before mistakes repeat.

If your team keeps blurring these flows, split them into two SOPs with two owners: one for bills you pay and one for money you collect through payment requests.

That split reduces repeat errors because the risks are different. On payer-side card funding, processing and international costs can outweigh cashback, and a tight credit limit can trigger a refused payment or extra fees. On receiving, common problems include setup gaps and expired links.

Gather what you need before starting payment#

Preparation matters more than speed. It is easier to check requirements before you start than to fix a failed card payment under a deadline.

Confirm your card can be used.

Check the card-funding requirements before setup. The card must be in your or your business’s name, with a 16-digit number, valid expiry, CVV, and 3D Secure. Supported networks are Visa, Mastercard, and some Maestro; AMEX, Discover, and Wise cards are excluded. For a Wise Business transfer, use a business card rather than a personal card or personal bank account.

Check this before the due date so you are not troubleshooting at checkout. If the card payment fails, Wise shows an error message and you lose time switching methods.

Prepare the invoice details you will enter.

Keep the invoice open while you pay so you can match the details exactly. Have the vendor name, total amount with currency, invoice number, due date, and payment reference in front of you. Wise invoice guidance also says to confirm amounts, item descriptions, and due date before you pay.

Follow the recipient’s reference instructions. For an invoice sent from Wise Business, Wise says to enter either its invoice number or its payment reference, not both. For a separate transfer to settle an ordinary invoice, agree a reference the supplier can match.

Check country context before payment day.

Record the card-issuing country, Wise account address, funding currency, recipient currency, and amount separately. A supplier billing in EUR does not mean you must fund Wise in EUR: you can quote a USD-funded transfer with a EUR payout. Check the final payment options for that exact route, not just the currency printed on the invoice.

Keep a backup rail ready.

Keep a permitted bank-funded option ready for an outgoing transfer. For a Wise Business transfer, use business funding rather than a personal account. For a supplier’s Wise invoice checkout, note the alternative methods enabled on that invoice. Availability in one flow does not establish availability in the other.

For a step-by-step walkthrough, see How Australian Agencies Can Pay US Contractors With Lower Risk.

Run a pre-check on card and corridor eligibility#

Check the exact setup before payment day. For a U.S.-issued credit card, card ownership, account address, source currency, amount, and the live payment options matter alongside the network. The current card help page does not guarantee acceptance of every U.S. card on every route.

Map your card against the key eligibility checks.

Record the funding currency as well as the invoice currency. Funding USD to deliver EUR is a different setup from charging your U.S. card in EUR. Use the source-currency guide and final quote to check the former; ask the issuer about conversion charges before considering the latter.

Mark the proposed method as available, unavailable, or awaiting confirmation. An issuer-approved card and a supported network alone do not complete the eligibility check.

Check limits and source-currency conditions.

Apply the restrictions for the currency you are funding, then review the live quote:

• For USD funding, account addresses in Nevada, American Samoa, or Mariana Islands cannot use card funding.
• For other eligible USD setups, check the published $2,000/24-hour and $8,000/7-day card limits and your remaining allowance.
• The card help page also lists blocked issuing regions. Review its current list when the issuer country differs from your usual setup.

As a hypothetical example, a $3,000 invoice exceeds the published USD card-funding daily limit even if your business card has $10,000 available credit. A timely bank-funded quote may fit better; the card’s own credit limit does not override Wise’s limit.

Switch early if anything is ambiguous.

If card funding is not offered for the exact transfer, select a permitted non-card option before the due date. Authentication prerequisites do not override address, amount, ownership, or source-currency restrictions.

Wise says failed card payments show an error message, and its Help Centre advises trying another payment method if troubleshooting does not resolve the issue. In practice, ambiguity is enough reason to move to your backup method early. Make a firm execution choice before payment day: either proceed with card or switch now.

Decide when a credit card is worth it and when it is not#

Use a card for a timing problem, not as the default. If a lower-cost method will still arrive on time, that is often the better choice.

Price the full cost, not just the Wise screen.

Wise says transfer cost depends on the amount, payment method, and exchange rate. It also says payment methods vary in speed and cost. Compare the same invoice in Wise using two options: card funding and your lower-cost alternative.

Then add issuer-side risk. Wise also warns that:

• credit or business card funding costs more to process
• card-issuing country and funding currency can increase Wise’s fee, with an EEA exception
• your issuer may add conversion, foreign-transaction, or cash-advance charges

Wise generally charges higher international card fees when the issuing country differs from the currency you fund. It exempts EEA-issued cards paid in an EEA currency. For a U.S. card, compare the actual USD-funded and foreign-currency-funded quotes rather than treating the supplier’s currency as the card charge currency. Before approving, confirm:

• total cost shown in Wise for this invoice with card funding
• whether this is domestic or international for the card and currency pair
• any issuer foreign transaction, conversion, or cash-withdrawal-style charges

Separate card classes in your comparison.

For transfer funding, compare the fee quoted for your actual eligible credit or business card with a permitted bank method. Keep a small worksheet:

The card payment being approved is only one part of the process:

• confirm how much the supplier should receive after the transfer
• separate funding receipt, conversion, and recipient delivery timing
• keep the quote and final charge for reconciliation

Wise’s USD guide estimates card funding reaching Wise in 0–30 minutes, but conversion and delivery follow afterward. Use the recipient estimate shown for your transfer when setting the payment deadline.

Use a cashflow rule, not a rewards rule.

If card funding protects runway you need right now, the fee drag can be worth it. If timing is flexible and margin is tight, it usually is not.

Ask the issuer how it classifies the payment before counting on an interest-free period or cashback. Wise warns some issuers treat its card payments like cash withdrawals. If the issuer applies cash-advance fees or immediate interest, include those in the cost comparison. Use this rule:

• choose card when it keeps a critical payment on time and protects near-term cash
• choose the cheaper method when timing risk is low

Add an urgency-versus-cost checkpoint to your SOP.

Pick the method deliberately each time:

• Can the lower-cost method still arrive before the due date?
• Is this an international card payment under Wise's definition?
• Are you using a card type that may change fees?
• Did you check issuer-side fees on top of the Wise quote?
• Is the cashflow benefit worth the incremental fee on this invoice?

This keeps card funding tied to a specific timing need, not to habit.

Before choosing card vs bank rail, run your real invoice scenario through the payment fee comparison tool.

Pay the invoice in Wise with verification checkpoints#

Accuracy matters more than speed at the point of payment. A reliable pattern is to verify the invoice, use an eligible card with 3D Secure, and submit one clean reference.

Review the invoice, then choose the correct starting point.

For an ordinary supplier invoice, sign in to Wise and create a transfer using verified bank details, the funding currency, and the recipient amount. For a Wise-issued invoice, its Pay now link opens the supplier’s invoice checkout; the email should show the supplier, items, and amount. Check unexpected payment instructions through a known supplier contact.

Before you proceed, confirm:

• recipient name
• total amount due
• currency
• that this is the exact invoice you intend to pay

Resolve any mismatch before paying. In an outgoing transfer, confirm the selected funding currency, recipient details, and live payment methods. In a Wise-issued invoice checkout, confirm the invoice and methods the supplier enabled; direct card checkout depends on the supplier’s existing card-receiving access.

Enter an eligible card and complete 3D Secure.

For an outgoing transfer, select Credit card only if it appears at the final funding step. Apply the ownership, source-currency, address, and amount checks above; business transfers require business funding. For a supplier’s enabled card checkout, follow that checkout’s displayed requirements instead of assuming every transfer-funding option applies.

The card must have:

• the required card number and valid expiry
• the CVV security code
• working 3D Secure authentication when requested

If 3D Secure cannot be completed, the card payment may not go through. Treat this as an authentication checkpoint, not just form entry.

Run a final confirmation check before submitting.

Before final submit, do one reconciliation pass against the invoice. Check:

• recipient name
• invoice currency
• total amount due
• funding method
• payment reference

For a Wise-issued invoice, use either its invoice number or its payment reference, not both. For your own supplier transfer, use the agreed reference in the field shown during setup. Check it before confirmation instead of relying on a fixed step number that may differ by flow.

If all fields align, submit. If one field is off, correct it before confirming. The goal is one clean payment with the correct amount, currency, and a single reference the recipient can match.

Handle failed card payments without missing the due date#

Read the error and check the existing transfer status before another attempt. If it was declined and not funded, correct a specific cause. If status or a card charge is pending, resolve that first; creating another transfer can duplicate the payment.

Read the error message and capture it.

Wise says failed card payments show an error message, so start there. Capture the message and log the invoice number, amount, currency, payment reference, timestamp, and card network used.

That gives you a concrete troubleshooting starting point: card type, authentication, or a restriction tied to currency or account context.

Check the eligibility assumption that likely failed.

Check card details, CVV, issuer limits, and authentication against the card troubleshooting guide. Then confirm the network and ownership requirements for your account, including business funding for a business transfer.

Check these transfer-funding conditions against the setup you actually used:

• whether the source-currency guide supports the method for your Wise account address
• for USD card funding, the address exclusions and remaining $2,000/24-hour and $8,000/7-day allowance
• whether the card is in the right personal or business name and is not a Wise card
• whether the issuer allows this payment and completes 3D Secure

An issuing-country/funding-currency mismatch can increase fees or interact with issuer restrictions; it is not proof that the supplier’s invoice currency caused the decline. Use the error and quoted funding currency to diagnose it.

Retry after a specific correction, then change method if needed.

Retry only after a verified correction and after confirming the first attempt was not funded or is safely cancelled. Examples include correcting CVV details, completing issuer authentication, or selecting a card that meets the ownership rules.

If card troubleshooting fails, choose another permitted method for the same invoice. Confirm the original transfer and card-charge status before creating a replacement; contact Wise if a pending charge or ambiguous status prevents that check.

Cancellation is conditional: only uncompleted transactions can be cancelled. The USD guide gives a 2–10-working-day card refund window after cancellation. A refund is not a same-day source of money for the replacement payment.

Confirm the first attempt’s outcome, then notify the vendor.

After confirming the original attempt will not also pay the vendor, fund the transfer through the available fallback or create a replacement if required. Tell the vendor the invoice ID, amount, currency, initiation time, and active payment reference or confirmation; identify any superseded attempt clearly.

Keep the message factual and concise so they can match incoming funds quickly. Related reading: How to Pay International Contractors With Fewer Delays and Disputes.

Know cancellation and refund limits before you rely on them#

Cancellation and refunds are not a good due-date plan. In Wise, they are conditional.

Treat cancellation as conditional.

Wise says refunds happen if a transfer is cancelled or if the recipient bank sends funds back. It also notes some transfers are cancelled for regulatory reasons. So do not assume a submitted payment can always be reversed on demand.

If funds look delayed, check Wise Activity or your home screen for pending tasks or notifications before telling the vendor the payment is being reversed. First confirm whether Wise needs action from you instead.

Keep the refund route clean.

For card-funded transfers, Wise refunds the paying card. Its guidance says an expired or cancelled card can still receive the refund if the linked bank account remains open. If the account is closed or the refund does not arrive within the stated window, contact Wise and the issuer to trace it.

If Wise asks for refund details, for example through Fix your transfer, provide the account details Wise expects for the refund. Entering different bank details can make the refund fail.

Build timing slack into your AP process.

Set a hard rule: do not schedule card payments so late that cancellation, refunds, or a rail switch have to save the due date. Wise notes most transfers run on working days, and Swift or wire payments can take 2 to 6 working days to reach Wise.

If a card attempt misses your internal cutoff, check its status before switching methods. Keep proof of any funds sent, and preserve enough timing slack for a permitted fallback and recipient delivery.

Keep an audit-ready payment record each time#

A same-day payment record saves time later. It helps you handle disputes, tracing requests, and month-end reconciliation without rebuilding the story from memory.

Download payment proof after completion.

Download the transfer confirmation PDF after a transfer completes and store it with the supplier invoice. Save the transfer identifier shown in your account and any banking-partner reference provided for recipient-bank tracing.

If a recipient bank cannot find funds, Wise says the banking partner reference on the PDF is the most useful number to share for tracing. Card statements and email notifications may not include the same tracing identifiers.

Log the exact reference and final outcome.

Record what actually happened, not just what was planned. Log your invoice number, the reference entered at payment, final status, your internal timestamp, and the funding method used.

For a Wise-issued invoice, record which one of its invoice number or payment reference you entered. For an ordinary supplier transfer, record the agreed matching reference. Keep that reference alongside the internal invoice ID rather than assuming every invoice uses Wise’s own numbering rule.

This gives your team a clean record of which reference was used, how the payment finished, and what to provide if the vendor asks questions.

Export from Transactions, not statements alone.

Use the website’s Transactions export for up to a 365-day period, filtered by date, recipient, status, direction, or other available fields. Currency-account statements omit activities funded through external methods, so they may not capture all card-funded transfers.

If your monthly statement does not show a card-funded transfer the way you expect, use the transfer export as the backup record. Keep one shared template folder and consistent naming so reconciliation stays clean, and review suggested QuickBooks matches before posting.

Use Wise Business receiving tools when you are the one getting paid#

If you are collecting money from clients, run that as a separate receiving procedure. Wise documents receiving and paying invoices as separate workflows, and payment methods can vary by request.

Pick the receiving tool based on client context.

Choose the tool that fits how the client will pay you:

• Invoices you create and send from your business account
• Payment links to request payment directly
• Quick Pay link or QR code for website, in-person, or invoice payments

Verify methods on the actual request. Wise Business card receiving is currently unavailable to new customers; an invoice or link alone does not enable it.

Confirm card acceptance before you promise it.

Wise’s card-receiving help page says the feature is currently unavailable to new Wise Business customers. Existing enabled businesses must be in the EEA, UK, Australia, Hong Kong, New Zealand, Singapore, Canada, or U.S.; eligibility does not guarantee access. Confirm the feature in your own account before promising card, Apple Pay, or Google Pay payment.

For existing enabled accounts, the help page lists Visa/Mastercard receiving in 17 currencies: AUD, CAD, CHF, CZK, DKK, EUR, GBP, HKD, HUF, JPY, NOK, NZD, PLN, RON, SEK, SGD, and USD. It works through enabled payment requests, invoices, or QR codes. Single-use payment links expire after 30 calendar days. For a U.S.-based receiving business, published fees are 2.9% + $0.30 USD for consumer cards issued in the U.S. and 4.2% + $0.30 USD for international consumer cards or any business card. These fees are deducted from the merchant’s payment and are separate from outgoing-transfer funding fees.

Keep payer-side and receiving-side procedures separate.

Maintain two short procedures:

• Payer-side SOP: how your team pays invoices
• Receiving-side SOP: how your team issues invoices, payment links, and Quick Pay or QR requests

This split prevents policy confusion, like promising methods that are not available on a specific client request or in your region.

When to move from one-off payments to stronger controls#

Move to stronger controls when ad hoc handling stops giving you clear answers on approval, status, and reconciliation. Instead of using a fixed invoice-count trigger, use the point where tracing a payment from invoice to final funds movement starts taking detective work.

Spot when ad hoc handling is becoming riskier.

Upgrade controls when these issues stop being rare:

• authorization checks are inconsistent or not clearly documented
• recurring charges run without clear authorization transparency
• reconciliation is delayed and clearing or settlement status is hard to confirm
• settled amounts are hard to explain against expected net after fees

Weak processing can increase costs, failed payments, and dispute workload, so waiting for a major failure is usually too late.

Track payments by stage, not just "submitted."

Track the statuses you can actually observe. For an outgoing supplier transfer, distinguish funding pending, funds received, conversion or payout in progress, and completion. A card authorization does not mean the supplier has been paid.

Record the displayed status, timestamp, owner, and reference at each checkpoint. For your separate receiving process, distinguish the customer’s payment confirmation from the merchant payout reaching your balance. This makes timing questions and net-after-fee differences easier to explain without inventing internal clearing statuses that Wise does not expose to you.

Keep a repeatable evidence pack for each payment.

Use one standard record per payment so any teammate can verify it without asking the initiator. Include invoice ID, legal counterparty name, currency, amount, approver, payment reference, timestamp, and confirmation evidence.

Use reconciliation forms consistently. Keep card entry in the provider’s payment interface, and store only the limited identifiers needed to reconcile the payment. Avoid saving full card numbers or CVV values in shared records.

Choose tools by control quality.

Prioritize tools and procedures that support documented approvals, traceable records, and explicit status tracking. Keep internal policy clear regardless of tool choice: who approves, what evidence is required, and when reconciliation is complete.

If you evaluate Gruv for this process, check which approval, status, and record-export controls are available for your actual market and payment program. Compare those controls with the gaps your AP team has documented.

Copy and paste this risk-first payment checklist#

Use this before any card-funded invoice payment to avoid deadline failures caused by choosing the wrong Wise flow or finding restrictions too late.

1. Confirm the flow first. For an ordinary supplier invoice, create an outgoing transfer. For a Wise-issued supplier invoice, use its enabled checkout. To collect from clients, use your separate receiving procedure; card receiving is currently unavailable to new Wise Business customers and requires existing enabled access.
2. Validate card eligibility before payment day. Confirm ownership, network, CVV, expiry, and authentication, plus the funding currency, Wise account address, amount, and actual payment options. Wise Business transfers require business funding. For USD card funding, screen the Nevada/American Samoa/Mariana Islands exclusions and remaining $2,000/24-hour and $8,000/7-day allowance. A U.S. issuer and sufficient credit alone do not establish eligibility.
3. Pick method by urgency versus cost. Compare a permitted bank method’s recipient-delivery estimate with the card-funded quote. Include Wise fees and issuer treatment, including possible cash-advance costs. Review issuing country against the funding currency; Wise’s international-card surcharge has an EEA-issued-card/EEA-currency exception.
4. Run four checks before submit. Verify recipient, currency, total amount, and payment reference directly from the invoice. Wise emphasizes checking recipient and amount, and notes references are important for many business transfers.
5. If card fails, troubleshoot from the error, then switch if unresolved. Capture the error and verify transfer status before retrying. Correct a specific cause only if the first attempt was not funded or is safely cancelled. Use a permitted fallback after confirming there will be no duplicate payment; escalate a pending or ambiguous charge to Wise.
6. Save proof immediately for reconciliation. Keep the confirmation, transfer ID or reference, invoice ID, timestamp, final funding method, and invoice terms. If you switched from card funding, record that too so later fee and timing differences are easy to explain.

If you are turning this checklist into a repeatable AP process, review the Gruv docs for compliance-gated flows, status tracking, and audit-ready records where supported.