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
- 827091d350517847e2aa58e740aba85e761acbf2f26d83d10f53999c0be07a01
- request
- 7834cc67cc8621331f1e2f90c425effa9cdbf440212113fd664c948d88d2177b
- transaction
- 51da6af7aec85ecc501b1685d07785d25d72477a4e635f8e41d71b7deff4a23ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1610
the chainentry 1610
- sealed to the entry before
- 260ae55a427b9cbe4e8c517fd02ef0856379ca24ed5ec114ce3023870c624e9e
- this leaf
- c1d6cfc993a514fc3a284dd3d12f7e49ff0fdc65d3999f0f7f3f76cd9d5889e9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OwoZ9ffLQe/ZXBsIcANDCTW5xUWNZm21a/wDZkDfZ4oWKvtfZTTA77lENOkml49NHL96C+iVipTXIFL6hmfaAw==