why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 5fa72c787466ee271584ef6b1cb3d5428dfd31fd481673efb42aa9e739044d8b
- request
- c994ca87fff74367e28b8ad2b4ed0391d35f811c159387f5943b9a5f34ed22e9
- transaction
- d07acb70c16fe4ce860eae9b227255935784b03392ba78289cccdec919e1c614computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13228
the chainentry 13228
- sealed to the entry before
- 4d72e067f5f78b9843722e5ca819f6f47d20574b85fe5acbf9d5efa818c44c62
- this leaf
- 84496556d3ce6ed0103e2aa1923dda04e406224ceb6615240bcf01272bdc7d8c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AGgNuGLYovSQWmkpA+cwo3kZ4MOo5UHhwn7Jx+h8d9Rnh6Wd7gL8G7dY3p8O4I1ZVHfZK3GXpBqFpirhl0JZBw==