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
- 9105f21aee7a66a20b729e5f09bff7726e011f8fef8fb7841c8d315c0acac5b5
- request
- a40280dafbc58a578dc877b3cacc8a00da9c2d8e335fb360d34ccab8267e296a
- transaction
- c704ab4f4ee306429286a8d729ac8e07c0d3ee3aff04b5b005fb88c7acc4a0b2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 973
the chainentry 973
- sealed to the entry before
- 6f755e8186f96e118daf8d4ddb854389a63756dd7b6e012659f0b65fddee0a9e
- this leaf
- 2f77c16f0f02a3dcf3295207985b471578dd6564fa2a566be9c2d99cc75a4626
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fiZmZYDVThChu+L3gFarSU7kGBUBOIWnozpA04sXU1cE3SwiZf0jzjt/IHaijk6+NSbkJ492oJkPpQkD5l0lDA==