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
- a599f440ebb40015fae5842641c1faef94c6c7c8afa708bb2f5e30ae5842b33a
- request
- cd630abb877affdae2520bb973cd7d048297d938333715fbd075127b1582d94c
- transaction
- 3ee50561ee7d6a1625b8efa068f53185776e7a42f27b40442600e37cd13909d3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2280
the chainentry 2280
- sealed to the entry before
- 2aaa3d4032192a473282d251acb11fe8ebf8507839539a3ccb1079bd7f0d5da4
- this leaf
- 848d86f23ef53243be797d5e9d48ed402fb049bc41549dab7393305fb289e511
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fIfQbdQlKl2nQd+Fdbdo4UgINEPsUQce9+lREhcqRTs7cAuabm8AmCm24udoZwSq4nEmNezATH+MmRUUReHsCg==