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
- 81825b212082d37d04ed1db8a7a7c8c4c684e2bb7d64524b653986f3e44ef5e5
- request
- 308cd0cd105271bcd5060969e25e761be79a91d67f4d4ee467af67fdfc71a076
- transaction
- 08eea5f289fc58d39ce60333a34d5f88e31b233090e32673815c04ed83c230f6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16981
the chainentry 16981
- sealed to the entry before
- 5cb7a622232a1b2076b6ebe5d0783c812550bf8cc18e2daf30e4c016fb1d027b
- this leaf
- 476003638053bac499982d4fdf56c1d2a63f1bdba83180c161f2edd91c38a1d5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /JWfrTYKFrxKXcbZNnru+VyJye2gbWrH+jCS97ZBrrfbMuxluep+84MyvrDSwRGPJuv4+/HwSx8Z4qqk5+JsDg==