pelecard-payment-gateway

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

• Third-party content exposure detected (high risk: 0.75). The required runtime workflow ingests Pelecard callback payload fields (including ConfirmationKey and PelecardTransactionId) delivered by Pelecard to the merchant’s ServerSideGoodFeedbackURL/ServerSideErrorFeedbackURL; this is outsider-authored free text (vendor-sent HTTP form/JSON) that the skill instructs to place into the agent/handler context for validation and processing.

MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).

• Direct money access detected (high risk: 1.00). The skill is explicitly a payment-gateway integration. It documents server-to-server API endpoints and parameters to create payment sessions (PaymentGW/init), charge cards or stored tokens (ActionType J4, IsToken/CreateToken), capture/authorize patterns (J5/J5h), and process refunds via the gateway's refund endpoint. It instructs sending the merchant credentials triple (terminal/user/password) and amounts (in agorot) and describes persisting PelecardTransactionId and tokens. These are concrete, money-moving operations (authorize/capture, tokenized recurring charges, refunds) against a payment processor — i.e., direct financial execution capability.