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
- 8d87370e78235e83a564acd2bef2bfa7cdaa243d2ebec90422da74aee5d1cc6e
- request
- 29bbe8f19ab1b1ff1af2bdf878aa5ae33fe3bf0e1a25547e9cc664e83ee1192d
- transaction
- 293fc01e19e1a911dda351ec71ec344115b5207947e95fce07e4d08d941c5d3ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50066
the chainentry 50066
- sealed to the entry before
- b7620cc3c98238d5d3d9ca435073a1d06ff7e6b365106df156e93ee2d3248b97
- this leaf
- 3ab368b1273e5d10baaae4d09c7dbc0a020cf1caab30da4ede355005cf66989e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DSkWuf8xcU04iR+Q5igTcV+lpJ7/JXQSBZV+b+vjwcTWP78Brt+nCaxXJZwmdONJbKNf2+7w40/CxoOFcb9kDw==