Billing errors and how to clear them

Where billing errors show up

There are two places, and they are different kinds of error.

When you tap Create, Laced checks what you typed. If something cannot be right, such as a Zip that is not valid, you get a message and a red border on that field. The profile is not created until you fix it and tap Create again.

The errors named below come back from Nike when the draw goes live, and the launch shows what Nike said. They catch what a typing check cannot, for example an address that does not match what your bank holds. Starting early does not bring them up sooner, because Nike only answers once the draw is live.

Billing’s address check is built to follow Nike’s own rules as closely as it can, so the best protection is a profile that passes it. That is why creating your profiles ahead of time still helps. A day before a release, or a few hours at least, gives you a quiet afternoon to get the details right. It is better safe than sorry, and it is not a requirement. The drop day checklist puts it in order.

The errors the app names

Each one is set out below, under “If something goes wrong”, with what causes it and what clears it. Two notes that apply across all three.

Read the specific error before changing anything. The most common way a five second fix becomes a twenty minute one is retyping every field at once and then not knowing which change mattered. Fix the field the error names and change nothing else.

And leave your profiles alone while a Draw window is open. Changing billing in the middle of a run is how a working set-up gets disturbed at the worst possible moment. Full detail is in what happens during a drop.

The declines the app cannot explain

This is the honest part, and it is the reason a lot of support threads end unsatisfyingly.

Some attempts fail without a named error, or keep failing on a card where every field is demonstrably correct. When that happens, the decision was almost certainly made by your card issuer. The app receives a rejection. It does not receive a reason. We cannot see why your bank said no, and neither can anyone answering your email.

Banks decline for reasons that have nothing to do with you: an unfamiliar merchant, a cross border transaction, a fraud rule that fired on the pattern rather than the purchase, a card freeze you set and forgot. Retyping the same card will not change a decision made on their side. Two things will. Call the number on the back of the card and ask them to allow it, or add a different card as a second profile and use that one.

The same limit applies to the card itself. Laced does not store card numbers, in the app or on our servers. The address on a profile is held encrypted on your own device, and the card data is not kept anywhere, so there is no record here for us to inspect on your behalf. That is a deliberate trade and it cuts both ways.

When to write to us

Write to hello@lacedentries.com when a launch keeps showing the same named error after you have corrected the field it names. Include which error you see and what you have already changed.

Do not write to us about a card your bank is declining, because there is nothing on our side to look at. And if you are adding more profiles so you have more entries in play, the plans are auto-renewing subscriptions managed through the App Store or Google Play, so billing questions about the subscription itself go to them.