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
- c71ab79e06936fa0d257ba2c641e8874737c298d10da46aaa5d347dabc25597e
- request
- d05e931bd02d93639556a10a7e1280bd77cf3525514d6345045a0969dbf4cc1e
- transaction
- 6c9edced542724d022227d4c2f2b8781c6f50c74041e0841026bc3a849a41b13computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22847
the chainentry 22847
- sealed to the entry before
- ac10cbe01d40e89fbf3686893e74158f76693ed8ec1ce28ad5091f0e4d88dd88
- this leaf
- 5a31cf33c7b1caf8e647b4f27324ec60fa4f39c4be63c622a1562171db75105b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FgtXJAIf/X1NIkAidRYFeDAS13awO5mMCcxLt77weuH09vEJlBnyuee2NRCajrcqr9QFKqEwJlh6iOnVdIxaCw==