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
- 9d71e3a761eef86b149d27f84bb48cf09170d0d696ddc06f16ccb0424bce784c
- request
- e18dc41fa27ac5302cb66e06434214793b1708edc6900ae9345c4b9d4a6f5784
- transaction
- e6e01a6adef17ce0811eab942d9a63886ddbf5d491a4deaffb84c9a1a9023da6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10628
the chainentry 10628
- sealed to the entry before
- 972e4277b9de26757a5852f03e991ea30cc720b25d70a68fd4f2739dbaf7c9d5
- this leaf
- 9038ce9f8e3b8d988340c81b387e1461f8907a0d55c195a5154f15c2f9d3f5f6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- j0WPB+ZvdUCm3a7O/1L/LJrmrjPfT/GMhnxrkCGqgtHIE4JkcNS7UnFLC2M5ssjJdREV2CN+/wawiLAANAd+BA==