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
- a2af6cd9f40d81f426d7b121697fb206bb3734894a794c9190c1abdb8b4fce17
- request
- 130700034cbcf17c5b96107a0f79ca1b810ead404c1e37cb595adb86f89e0038
- transaction
- 522cc48243f94066bfe4eb96d1724cbb7216612459641b70627a1cafd43a882ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73908
the chainentry 73908
- sealed to the entry before
- a004556086cdd2c04a8d6c41d866cfbd3f6e087ac0a9eb2930403066740c813d
- this leaf
- a3cef262c8a99d8b68f0958140eb3309a4359bb35dbb72c48cfac36fb3946241
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- O/rH776TgZcDHUbhoHutFZZtsgG2uc5TrLDzbAKsFKNzs/vCuaec6uJZ6fqMdByXph9byYTCxi3SFItDr1SxDw==