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
- 0f5c6c69fab7a72108423f8c4f70a5c788791cd44baee7a0f0cb86dcfcf190f5
- request
- 8955a74852cc89f7eae637d546e968cdc549fef70dc8c22711095d73176ca95e
- transaction
- cba46e3706302eada44a7029b242127653a94d2188b303052185ccd629d9dda3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25485
the chainentry 25485
- sealed to the entry before
- 7b4d8ad36cd44d751a3fb161726d03a377ddb53c7881e97c115c876b4442f5ce
- this leaf
- 6d4172f3d5f71f98d21daefa5682a0af73808fd952965d06d2c7bb4fcb9289e9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6gA70aK6b/PQbwBiFcqBE54i5IUoGuk7U2B2ibH6KUwsyAqvCu+QD0z47S7lCf6hBg7sK+ZTXSWwlHSuM/63BA==