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
- 26f74aa0abbbed4357228e28cc649d7b1b1aec2ecfce3656181682f29d4a119a
- request
- 4cd80d891d38fd1140c0a21c3a7d9f36c1838a775130f9ee234657c54f2d0eb9
- transaction
- 7b83d6e45e6fe7a64f256116131b4b06ad9a607be58d9d9375d86f87f9287bb8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61750
the chainentry 61750
- sealed to the entry before
- e050414b44bae91e13375ef48ec767bf28cf268553fcf9e43fe2c209bf853a4d
- this leaf
- f41c0be7a16f91066ce4363ec36e86b7b0e9d7ae13060df85e01a81646f86c15
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BzsAiQTqw98GFpMG2EleHxXO3gveiR+3EPZWG1qHErrQhxrXKIU8oB1RncKMHTDiS4cLWYG1P9r7DKZFmXAXDQ==