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
- 5efab0c680464f0f74591f6450a21a3534bd9b53e65f2d49813443014241d779
- request
- 9a5bafa544ae74d1a2340683d42454d256e242334b3d5907fc928440c1c0c145
- transaction
- 6f3462eb42e3299de4e2374e0e480a1ea4936a010a978089af8a4486752ea243computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16949
the chainentry 16949
- sealed to the entry before
- 9b984759e6cd1cb28d6d5318a6bafa918a9ab0c0bc9a0ddf2712a6367cf75df0
- this leaf
- 647151c6eb99cbd4d9876f363eb961f1827ac36064674f1ffa61e3dfe2f57329
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qDwlEsyYxWBcW06GD2iBFRPHNbx+VhAOYdKb0XK0zVjLPcsIqW+q4g5QDOuki/UhqBIYxgbpIeqATID1Bzi0AA==