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
- 0393e4357ada4be8970acfc020aab187596964b102d29c977d4905ac919dc70a
- request
- d08947f2909bc23f6fd906c80ae7ce63b362a781485ad0118ace7c44e745f386
- transaction
- b72985786de6ca1399d0852b89f4e558c59db265479a98fa55bb2645196ef93acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1142
the chainentry 1142
- sealed to the entry before
- d7ebfca67603094c76268821ac0f944a8d297f58973a061c82d495c7849af43e
- this leaf
- 083692f22772209f65ae1e8221404eff5402c0ac14da1f0bd6ace9cd28e08140
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2iuoOePeqUVXDjMaNKm9Lrhjrf4A84ryxOnpDNcsBrkKKpf36ssoiA2VT15OaNAJqI3nQ3w7U3ZmFhRb0s3sDA==