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
- cadaa15ac224b8ac1169683ce8094af3ff831b267b77f594689316e23b34e41f
- request
- 0676be390daa91aa8881aa65e8425bfaae62c668c09b05f976e7edc1e78d27c2
- transaction
- 98f396fb98914a36f6ab71cfcd7d62137554ccb2ca89dae28dce53b42de82afdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28148
the chainentry 28148
- sealed to the entry before
- 6295109a713728765e9d1cb8583c2b45793ee2a1d381e1d80d2150414e539aa9
- this leaf
- fcbd46f14a9011e5dcf1e8ec1398dbd41db716e4c74b1fa888fea68d1a845503
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1Wa0A61K7YoTlIR8YO5PbjvFHo4Jakup4gGgZ0rI5mn0HAUrNtpkpf9xtYG5Sc2dKaywY5zGHEWhKDBasv08BA==