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
- 6f3359b21a0e0a5cd00fa6699637a5699f89ddffdf52861ef771c11719a616c7
- request
- 9874217b80cf4440fd0890711ed6c593059be0e2060bd8b6bdf92cebd4a91472
- transaction
- c6bd45e51c3eee5162a235ac5fd5bd2cd0759d789e97644e57aabd88ea94911bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14846
the chainentry 14846
- sealed to the entry before
- 4acaa565215a6196109b3a20fb9836ac5e7a2edd90e08cd0c99c9124709aad05
- this leaf
- 555cea8c3f89fd8cd643cf6796248222f0792be56e62363798c1e044cab5583c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1iwLiXI4hV0V/XwiqDwH6rolP0WwRkebOBH9dh2skA5np7ZY4VcmbGU168GNyMekhmcw6o7qEwTzvSMOE8YaDw==