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
- 1ea95a38531485d09d7793b84bd441a44ab35b17d0a085c6f6b4696bf5807a45
- request
- ab50cd72691685c53927119b14c7a634631dff1dea8b887cd62ca226b4b7df52
- transaction
- 2db1b4a1220b5311d31b12de83392f7695de0436dbb05f230a73bb6921db1c90computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77438
the chainentry 77438
- sealed to the entry before
- 4a0b2bd576aea6f36a43e857d701b17ff98b9769b00b00e4e3718a7674a91bd2
- this leaf
- 5232856a270c45bc2c80819580b1c5ce0269d86a3c326601790e4ce456256072
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xR0z5TVFNsBJ2IGn+h4Ivru7mh8GkC9brupjTImuoIk+bN1HZtLuznY0irHn+Zhv5GUNUnNG8BOUJdXHJacBDg==