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
- 4e740800add019db0a958910185a847074852bcbcebfa40454f5dc8cb120cbc0
- request
- 4698ce0346fa02317a14297362f30fedf57c6392004920bfc6ed40c9ac3ae133
- transaction
- 0829305d0685459d4ed1a175920447d4cd0661bd8dadef22a0f374b67d0cac89computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3018
the chainentry 3018
- sealed to the entry before
- b8944b5bb229245b9781b2047d2888cb67915fd04f903abcdd805346714aec4b
- this leaf
- d7e5706f0e4885765b88655b593fdf36c0ab0074164b1179e76134e384f1aed8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6zhy0ku3chM2JbgXxIP3gnuoXQA2Lq/eNQc68ZGPiW1qVuEhdS80M5PocjY97P7F9C01iugAhF1cFHUyyKuQCw==