List Reconciliation Details by Network Funds Transfer Key

In March, 2025, we released a new endpoint to list all reconciliationDetails by NFT key. Please find the API docs here. The reason to use this endpoint is to retrieve all reconciliationDetails that belong to a specific settlement so you can easily reconcile it against the networkFundsTransfer with the same NFT key.

VAAI (optional service for acquirers from Visa)

VAAI is now available on the Silverflow API. This is only for CNP transactions, and will be returned for declined transactions as well. VAAI score is returned in 201 response under sub-property authorizationIsoFields.networkSpecificFields.vaaiScore . This sub-property is optional, meaning whenever returned by Visa, it is present. Available on endpoints /charges , /charges/mit and /charges/{initialChargeKey/mit} .

How does VAAI work
Visa is utilizing AI to help clients detect suspected fraudulent activity by providing insight into the enumeration of payment credentials. The VAAI Score uses historical and near real-time data for Visa CNP transactions processed by VisaNet to generate a score with values that range from 00 to 99 for clients to use when processing CNP transactions. The score indicates the probability of a given transaction being enumerated and potentially at risk for follow on fraud. Low scores would indicate a lower likelihood that the authorization is indicative of enumeration and high scores would indicate that payment credentials are likely being enumerated. The value of 00 will indicate that there is an insufficient history to generate a score. Contact your Visa representative to activate VAAI.

Visa ANI (Account Name Inquiry) for Visa is now available on our API.

ANI helps acquirers verify that a cardholder is who they claim to be. Visa Account Name Inquiry (ANI) enables merchants to verify that the name provided by a cardholder matches the name held by their issuing bank. It provides an additional security check during card onboarding and pre-transaction checks. Performing a name verification can help reduce exposure to fraud and scams in subsequent Card Not Present (CNP) transactions and pull/push payments such as Account Funding Transaction (AFT), Original Credit Transaction (OCT). For example, ANI might be performed ad-hoc by an online eCommerce merchant, or in a wallet when a fund recipient’s card details are entered for the first time.

* Account Funding Transaction (AFT), Original Credit Transaction (OCT). ANI results are returned (when applicable) via our 201 response on /charges , /charges/mit and /charges/{initialChargeKey}/mit endpoints.

PAR (Payment Account Reference) is now available on our API.

Payment Account Reference (PAR) is gaining attention for solving a key challenge in multi-channel payments: linking online and in-store transactions to the same customer. Historically, unifying a customer's online and in-store purchases required building algorithms around multiple data points like PANs, emails, IP addresses, and device IDs. While effective, this method relied heavily on sensitive data. When working outside an acquirer’s environment, unifying data sets becomes more difficult.

PAR simplifies this by assigning a 29-character, non-sensitive reference to each card (PAN), which remains consistent across all transaction forms - whether in-store, mobile wallet, or online. This eliminates the need for sensitive identifiers and reduces compliance burdens and PCI scope. With PAR, systems can track customer behavior more accurately, even when changes like a new token or device occur. For merchants, this leads to improved risk models, easier loyalty program enrollments, and better analytics that connect a customer’s online and offline interactions. PAR finally gives us a single, standardized tool to unify multi-channel data without passing around sensitive credentials.

PAR presents a standardized way to unify multi-channel data without compromising security - revolutionizing how we approach customer insights and fraud prevention. PAR is currently fully live for Mastercard, and we're planning on making Visa and AMEX PAR available in the coming quarter.

Mastercard Edit 25 Requires Online Refund Authorization by May 1

Mastercard has introduced Edit 25: Purchase Return Trace ID in late 2024 to monitor refund transactions for compliance with requirements. The requirements state that acquirers must ensure that all merchants seek online authorization for dual message system-acquired refund transactions.

The affected transactions here that have triggered this edit are due to offline refund, which mean trace ID can’t be matched with the online refund authorization, since it was either not approved or didn’t take place. In order to be compliant by 1 May, offline refund shall be avoided.