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
- f70cdc4b357c4cbf6ee2b13a48b2a2d520cb36e8c2bb209a379f17ceb3a10236
- request
- 83ac9eb42ab04231204bdae55caae553292e594ed2cd48b3eafa07b8f47fadfb
- transaction
- 1bd42d40b30572d963ea1f10e96b5b2acb5fd4b7cf1b8a258514fa8c944af674computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63956
the chainentry 63956
- sealed to the entry before
- 2479c453fcec556f89bfe5f0884c62a0313a163b71f6a54eef6cdf4f50afe1ba
- this leaf
- abf0db8786bb6ca51bb3132b14b57150c516be3087b6552a8364d61d0183f665
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Dp+cgLnsCusIpHsBl4vobKUbDvsJu/W6ZLNSYuaWVonxWsfNkAumSiE33BbGfLWWG+sttZsTxc5CkXflS0hzCA==