Banning a player does not block S2S order creation for a specific player_id

If you create orders through the Server-to-Server (S2S) Create Order method, Aghanim uses the player_id provided by your backend as-is. There is currently no Aghanim-side dashboard setting or blocklist that prevents order creation for one specific player_id.

What Ban Player does and does not do

• Ban Player does not stop order creation. Orders can still be created if your backend keeps sending that player_id in S2S Create Order requests.
• Ban Player does stop successful payment capture. Payments for a banned player are rejected with a USER_BANNED error.
• Banned players do not receive entitlements from those blocked payments. Since the payment is not successfully captured, the purchase is not completed.

Recommended action

The reliable fix is to correct the player_id your backend sends when creating orders. If you are seeing placeholder or invalid IDs such as 00000-..., add validation on your side before calling S2S Create Order.

Temporary mitigation

As a temporary safeguard, you can ban the affected player record to ensure payments cannot be captured. This will not stop the orders from appearing, but it will prevent those orders from being paid successfully or granting access.

Current platform limitation

At this time, there is no Aghanim-side feature to block S2S order creation for a particular player_id. Any prevention of invalid IDs at order-creation time must happen in your integration until platform-side validation is introduced.