Skin payment overpayment: why selected skins can exceed the order total
Understand the difference between order price and accepted skin value, what overpayment means, and how merchants should validate and explain it.
What does overpayment mean in a skin checkout?
Skin payment overpayment is the difference between the store’s requested order price and the accepted value of the skins used to pay it. Individual skins have discrete values: a customer’s chosen combination may be worth slightly more than the exact order total. That does not automatically change the product price or purchase quantity.
Skinloop’s documentation distinguishes requiredAmount, the order price, from amount, the actual accepted skin value. It defines overpaymentAmount as the non-negative difference between the two. These fields describe a payment; they do not by themselves create a refund, a customer balance or a larger order.
A simple example: a $12 order paid with $12.75 of skins
Suppose a store creates a checkout for a $12.00 order, and the customer selects accepted skins worth $12.75. The required amount remains $12.00, the accepted value is $12.75, and the overpayment is $0.75. This is an arithmetic illustration, not a promised item quote or exchange rate.
- Order price: $12.00.
- Accepted skin value: $12.75.
- Difference: $0.75.
- Order contents: the products attached to the original $12.00 order.
A merchant should not reject an otherwise valid completed payment just because the accepted value exceeds the requested amount. Equally, it should not silently replace the stored order total with the higher value or grant additional goods solely from that difference.
What customers should check before confirming
Compare the requested total with the accepted value of your selected skins before proceeding. If the difference is not acceptable, consider another available selection before committing to a trade. Do not assume a displayed market price elsewhere is the checkout’s accepted valuation. Use the actual figures for this checkout.
If the store offers credit or an excess-value remedy, read that store’s policy and ask how it applies before paying. The Skinloop amount fields do not establish that policy. A larger payment also does not bypass Steam restrictions, remove CS2 protection or make the order immediately ready to deliver.
How merchants should validate the amount
Store the original order amount before creating checkout. On a verified completion event, compare requiredAmount with that saved price, confirm the expected currency and merchant/order association, and ensure amount is at least requiredAmount. Verify that overpaymentAmount matches the exact difference.
Skinloop’s create API accepts integer USD cents, while its documented webhook amount fields are decimal strings. Parse the decimal strings strictly into integer cents before comparing them. For this example, compare 1200, 1275 and 75 cents—not rounded floating-point results or display-formatted strings.
Amount validation is only one part of fulfillment. The completion state and fulfillment permission must also be valid. A protected or pending payment is not a completed order, and a browser return to a success page is not settlement evidence.
Explain the difference without changing the order
Keep the order total, accepted payment value and difference as separate records. This makes support and reconciliation clearer: the buyer can see what they ordered, what their selected skins were valued at, and why those amounts differ. Avoid describing the difference as an undisclosed store fee unless that is actually the applicable policy.
A useful customer explanation is: “Your order total is $12.00. The accepted value of the skins you selected is $12.75, so the difference is $0.75. Your order contents remain unchanged. Please check our policy or contact us about excess value.” Adapt the figures and policy language to the real transaction.
Skinloop’s hosted-checkout documentation currently assigns customer communications to the merchant rather than promising Skinloop-issued customer receipts. Include a recognizable order reference and a support route in your own communication.
What if the customer asks for a refund or credit?
First verify the completed payment and the original order. Check whether the merchant’s published policy addresses overpayment, whether any remedy has already been recorded, and which team can authorize the next step. Do not issue goods or money from an unverified screenshot or a raw, unsigned webhook.
The reviewed Skinloop amount documentation does not specify an automatic overpayment-refund or stored-credit mechanism. That absence is not proof that no separately agreed policy exists; it means an integration must not invent one. If a policy is unclear, contact the merchant before promising a particular outcome or timeline.