BillShipper Payment Method Is Not Valid For This Shipment 111600 | Fix It Fast

You hit “Buy label,” your app spins, then you get the message with code 111600. It feels like a payment problem, yet your card or account looks fine. This error pops up most when the shipment’s billing block and the shipment type don’t line up, or when the account you’re trying to bill is missing the right billing setup.

If you print labels in batches, fix one order, then resume.

What The Error Means In Plain Terms

UPS uses a “who pays” section inside the shipment request. BillShipper is the standard choice when the shipper’s account pays the transportation charges. The 111600 message is UPS saying the payment method you provided under BillShipper isn’t allowed for the kind of shipment you’re creating. That message reads billshipper payment method is not valid for this shipment 111600.

One common trap is using an alternate payment type that only works for forward shipments. In UPS billing fields, an AlternatePaymentMethod value like PayPal is only valid for forward shipments, and UPS rejects it for Return or Import Control shipments. That rule is documented in UPS parameter references used by shipping integrations.

Another common trigger is sending multiple billing options at once, like an account number plus a credit card block plus an alternate method. UPS expects one path for the charge, not a grab bag. Many shipping apps hide this from you, but custom code and middleware can accidentally send conflicting fields.

BillShipper Payment Method Is Not Valid For This Shipment 111600 Triggers

Most teams fix this error by hunting the trigger, not by swapping random settings. Use the table below to spot the pattern fast.

Some shipping setups rely on your UPS.com profile having a valid payment method tied to the shipper number. Pitney Bowes documents a related UPS setup failure where adding a payment method to the UPS.com profile resolves shipping errors after account configuration changes.

Start With A Fast Checklist Before You Change Anything

Run these checks in order. Each one narrows the cause without making your setup messy.

1. Confirm the shipment type — Check whether you’re creating a forward shipment, a return label, or an Import Control flow. If it’s not forward, remove any AlternatePaymentMethod under BillShipper because it’s not allowed for returns or Import Control shipments.
2. Look for mixed billing blocks — Inspect the request payload or your platform’s advanced settings. You should see one of these for the main charge: AccountNumber, CreditCard, or AlternatePaymentMethod. If you see two or three, strip it down to one.
3. Validate billing address fields — If you bill a UPS account number, the billing address data for that account can matter in third-party and receiver billing flows. Many integrations fail when city, state, or postal code doesn’t match what UPS has on file.
4. Check account status and lockouts — If labels stopped across the board, your UPS account may be restricted or suspended. Many shipping help centers point to account restrictions and billing issues as the real cause behind “cannot be used” errors.

If your platform hides request data, run one test label with logging enabled so you can see the billing block.

Fix The Billing Block In Your Request Or Shipping App

Once you know the trigger, the fix is usually a small edit in one place. The section below covers the three billing patterns that produce the 111600 error most often.

Forward shipments using BillShipper

For standard outbound labels, BillShipper is the cleanest approach. Use the shipper’s UPS account number for charges, and keep the billing section simple. If you want an alternate method like PayPal, confirm your integration uses the exact allowed value and that the shipment is forward only. UPS parameter docs used by integrators note that PayPal (value 01) is only valid for forward shipments.

• Use one payment path — Pick AccountNumber, CreditCard, or AlternatePaymentMethod, then remove the other siblings.
• Match the payer to the shipper — The shipper number and the billed account should belong to the same UPS relationship unless you’re doing third-party billing.

Return labels and Import Control flows

Returns change the rules. A return label can still bill the shipper, yet some alternate payment options that work on outbound shipments are blocked. If your request includes AlternatePaymentMethod under BillShipper, remove it and send the shipper’s account number instead.

• Remove alternate method fields — Delete AlternatePaymentMethod for returns, then re-run the request.
• Verify return address format — UPS can reject malformed “ship from” data; fix obvious issues like state or province codes.

Third-party or receiver billing

When you bill a third-party account, UPS checks permission and address alignment. If the account owner blocks inbound charges, UPS rejects the billing method. Vendor knowledge bases for UPS billing errors call out address mismatches and blocked inbound billing as common causes.

• Confirm the billing address — Use the exact billing city, state, and postal code for the account you’re charging.
• Verify billing permissions — Ask the account owner to confirm they allow third-party charges for your shipment type.

Account Setup Checks That Fix “Payment Method Not Valid”

Sometimes the request is correct and UPS still rejects it because the account profile isn’t ready to be billed. This shows up more often after OAuth migrations, new account creation, or when a saved payment method expires.

A clear example is documented in Pitney Bowes guidance for UPS shipping issues after OAuth changes. Their resolution includes adding a payment method to the associated UPS.com account profile.

1. Log in to the UPS account — Sign in at UPS.com with the login tied to the shipper number you’re billing.
2. Add or refresh a payment method — Ensure there is an active card or billing method saved, and that it’s not expired.
3. Review invoices in the Billing Center — If your account has past-due invoices or holds, clear them before retrying label creation. UPS describes the Billing Center as the place to view invoices and manage payment methods for shipping accounts.
4. Check for suspension signals — If UPS shows a restriction, resolve it in the account portal or with UPS billing so the shipper number can be charged again. Some shipping platforms note that suspended accounts and expired billing details can cause shipping failures.

Deeper Troubleshooting When It Still Won’t Clear

If you’ve corrected the billing block and verified the UPS account profile, treat the error like a data validation issue. One small field mismatch can cause UPS to reject the billing method even when the account is real.

Check address and contact field limits

Shipping tools regularly see failures when address lines exceed UPS limits or when state and province codes are not in the expected format. ShippyPro’s UPS error notes include practical fixes like using valid province abbreviations and keeping address fields within length limits.

• Trim address line length — Shorten Address 1 and Address 2, then retry the label.
• Use official state or province codes — Swap full names for the standard code your carrier expects.

Watch for account lockouts

If your UPS login was recently entered wrong in a platform, UPS can lock the account for a period of time. ShipWorks notes that UPS account restrictions and lockouts can block shipping until the issue is cleared with UPS.

• Try a single label after waiting — If the lockout is time-based, a later attempt can succeed without any config changes.
• Rotate credentials carefully — Update stored passwords or OAuth tokens once, then stop repeated retries that can extend the lock.
• Switch to manual label purchase — Buy one label directly in UPS.com to confirm the account can still be billed, then return to your app.

Confirm the billed account can be charged

When you bill a UPS account number that isn’t yours, UPS checks whether you have permission to charge it. Pitney Bowes notes that “UPS account number … missing or invalid” errors can also happen when there is no permission to bill the target account.

• Reconfirm account ownership — Make sure the account number belongs to the party that agreed to pay.
• Match the billing address exactly — Use the billing address UPS has on file for that account, not the ship-to address.
• Ask for inbound billing approval — The paying party may need to enable third-party billing for your lane.

Common Mistakes That Bring The Error Back

Once you clear the 111600 issue, these are the moves that tend to re-create it a week later. Catch them early and you save a lot of label retries.

• Saving PayPal for all labels — AlternatePaymentMethod values can be valid for forward shipments and blocked for returns, so a global setting can break return labels.
• Copying billing addresses from the ship-to — Third-party billing often needs the payer’s UPS billing address, not the recipient address.
• Ignoring expired cards on UPS.com — If the account profile payment method expires, shipping platforms can start failing even when your API request looks unchanged.
• Retrying too many times — Rapid retries after a credential issue can lead to lockouts and longer downtime.
• Mixing payer types in one shipment — If you send BillShipper plus a third-party payer block, UPS can reject the billing method as inconsistent.

If you’re documenting this for a team, save one working payload example for each label type you create: outbound, return, and third-party. That small internal reference stops the “it worked last month” scramble.

And if you need one last sanity check, re-read the error text itself: billshipper payment method is not valid for this shipment 111600. It’s not saying your card is bad. It’s saying the payment method choice doesn’t fit this specific shipment request, so adjusting the billing block to match the shipment type is the fastest fix.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback