Allomancy

Payment Troubleshooting

Make sense of failed sent payments, decide what to check first, and know when to ask for help.

When a sent payment does not go through, you can usually find the cause from two places: a status icon and an optional message. This page walks through what each status looks like, what to check first, and what the underlying error codes mean if they show up in the message text or in a support conversation.

The Sent Payments tab lives at stores.allomancy.com/payments/sent.

Where you see failed payments

Failed payments show up on the Sent Payments tab. Each row has:

  • A Status icon.
  • A Message column with extra detail.
  • A Source column showing what kind of payment the row is.

You can narrow the list to a single category from the payment-type dropdown above the table: All, Manual, ProfitShares, Fees, Refunds, Subscriptions, or Other.

Reading the status icon

StatusWhat it means
RequestedAllomancy has queued the payment but has not started sending it yet.
ProcessingThe payment is being sent to a vendor for delivery.
SuccessThe payment completed. A short Transaction ID appears in the row.
FailedThe payment did not go through.
ErrorAn unexpected problem stopped the payment.

Failed and Error rows both use the same red alert icon, so check the Status and Message columns for details.

What to check first

Most failed payments come down to one of these issues.

  • At least one of your vendors is rezzed inworld. Allomancy sends L$ through your rezzed vendors. With nothing rezzed, no send can succeed.
  • The vendor has debit permission. When you rez a vendor, Second Life asks whether to grant debit permission. Without it, the vendor cannot spend L$ on your behalf.
  • The recipient username is spelled correctly. The Send L$ dialog looks the username up before the confirmation step, but a misspelled name in another flow can still fail.
  • Your sending balance covers the amount. The L$ comes out of the avatar that owns the rezzed vendor, so that avatar needs enough L$ available.
  • You have not sent too many payments too quickly. If you have just sent many payments in quick succession, wait several minutes before trying again.

Allomancy does not retry a failed payment. While a payment status is Processing, Allomancy automatically retries for several minutes (covering cases where no vendor was rezzed inworld at the time, or where the funds were insufficient). Once the status becomes Failed or Error, no further retries occur. To send the same payment again, open Send L$ on the Payments page and submit a new request.

Error codes

Allomancy and Second Life's L$ system use short codes for specific failure reasons. If support mentions one of these codes, refer to the table below to see what it means.

CodeWhat it likely meansWhat to check
NO_VENDORS_FOUNDNo rezzed vendor was available to send the payment.Rez at least one vendor inworld and try again.
LINDENDOLLAR_INSUFFICIENTFUNDSThe sender's L$ balance was too low.Top up the L$ balance of the avatar that owns your vendors.
LINDENDOLLAR_ENTITYDOESNOTEXISTSecond Life could not find the recipient avatar.Double-check the spelling of the recipient's username.
LINDENDOLLAR_BADCLOCKSKEWSecond Life rejected the transfer for a timing reason.Wait a moment and try again. If it persists, contact support.
INVALID_DESTINATIONThe recipient could not be used as the destination for this payment.Check the recipient username and try again. If the username is correct, contact support.
INVALID_AMOUNTThe amount was outside the allowed range.Use a whole number between L$1 and L$9,999,999.
THROTTLEDThe Second Life payment system temporarily rate-limited the request.Wait several minutes before trying again.
MISSING_PERMISSION_DEBITThe vendor does not have permission to spend L$.Re-rez the vendor and grant debit permission when Second Life asks.
GROUP_OWNEDThe object that was supposed to send the payment is owned by a group instead of by you.Take the vendor back into inventory and re-rez it under your own avatar.
TRANSFERS_DISABLEDThe transfer could not be completed because transfers are disabled or blocked.Confirm that the sender and recipient can normally send and receive L$, then contact support if the issue continues.
EXPIREDThe payment request was not processed in time.Send the payment again.
SERVICE_ERRORA general error occurred while processing the payment.Wait a few minutes and try again, or contact support if the issue continues.

When to contact support

If a payment keeps failing after you have worked through the checks above, or if you see SERVICE_ERROR more than once, email archis@allomancy.com with:

  • The receiver username
  • The amount
  • The approximate time of the failed payment
  • The status (Failed or Error) and any text from the Message column

Including the status and the message text helps the team trace the specific failed payment in the system.

On this page