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
- cca07028814a0c5595ea968697b697bafa3452ce10e9f76c18378f620b01d05d
- request
- 150c7e67c803994754bf2b0fab5867757caf576832e97630b8b7baee60087774
- transaction
- d037c7fd5d9dfce278a58d9a9ee64bc5963ddf507dd9ec61d21ad5bc9dd368d6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29755
the chainentry 29755
- sealed to the entry before
- 3f34644379a214c4dfb744e6b981f9c0a5ee7442a014bed0f34a2c0017f03e71
- this leaf
- aeae9e62377ac37ecffa8ee37ed02c6bbd5ef96471a6f8baf933ca86f706882a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ozGCn3MMVxLBqs3m8EARp9qq1n20QBModU7MTEp2b5OZGUVP3oW+88w73uw3WeVXMzTbGHa5f6x/sYIpCaYgDA==