Security News
pnpm 10.0.0 Blocks Lifecycle Scripts by Default
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
@datafire/adyen_binlookupservice
Advanced tools
Client library for Adyen BinLookup API
npm install --save @datafire/adyen_binlookupservice
let adyen_binlookupservice = require('@datafire/adyen_binlookupservice').create({
ApiKeyAuth: "",
username: "",
password: ""
});
.then(data => {
console.log(data);
});
The BIN Lookup API provides endpoints for retrieving information, such as cost estimates, and 3D Secure supported version based on a given BIN.
Verifies whether 3D Secure is available for the specified BIN or card brand. For 3D Secure 2, this endpoint also returns device fingerprinting keys.
For more information, refer to 3D Secure 2.
adyen_binlookupservice.get3dsAvailability.post({}, context)
object
Use the Adyen Cost Estimation API to pre-calculate interchange and scheme fee costs. Knowing these costs prior actual payment authorisation gives you an opportunity to charge those costs to the cardholder, if necessary.
To retrieve this information, make the call to the /getCostEstimate
endpoint. The response to this call contains the amount of the interchange and scheme fees charged by the network for this transaction, and also which surcharging policy is possible (based on current regulations).
Since not all information is known in advance (for example, if the cardholder will successfully authenticate via 3D Secure or if you also plan to provide additional Level 2/3 data), the returned amounts are based on a set of assumption criteria you define in the
assumptions
parameter.
adyen_binlookupservice.getCostEstimate.post({}, context)
object
object
string
: The three-character ISO currency code.integer
: The payable amount that can be charged for the transaction.object
string
: The country where the card was issued.object
string
: The first 6 digit of the card number. Enable this field via merchant account settings.boolean
: If true, it indicates a commercial card. Enable this field via merchant account settings.string
: The card funding source. Valid values are:string
: Indicates availability of funds.string
: The issuing bank of the card.string
: The country where the card was issued from.string
: The currency of the card.string
: The payment method associated with the card (e.g. visa, mc, or amex).string
: Indicates whether a payout is eligible or not for this card.string
: The last four digits of the card number.object
boolean
: If true, the cardholder is expected to successfully authorise via 3D Secure.boolean
: If true, the transaction is expected to have valid Level 3 data.integer
: If not zero, the number of installments.object
string
: The card number (4-19 characters) for PCI compliant use cases. Do not use any separators.string
string
: Encrypted data that stores card information for non PCI-compliant use cases. The encrypted data must be created with the Checkout Card Component or Secured Fields Component, and must contain the encryptedCardNumber
field.string
: The merchant account identifier you want to process the (transaction) request with.string
: The recurringDetailReference
you want to use for this cost estimate. The value LATEST
can be used to select the most recently stored recurring detail.string
(values: Ecommerce, ContAuth, Moto, POS): Specifies the sales channel, through which the shopper gives their card details, and whether the shopper is a returning customer.string
: The shopper's reference to uniquely identify this shopper (e.g. user ID or account ID).object
object
string
: Card brand.string
: Directory Server (DS) identifier.string
: Public key. The 3D Secure 2 SDK encrypts the device information by using the DS public key.object
string
: 2-letter ISO 3166 country code of the card acceptor location.boolean
: If true, indicates that the merchant is enrolled in 3D Secure for the card network.string
: The merchant category code (MCC) is a four-digit number which relates to a particular market segment. This code reflects the predominant activity that is conducted by the merchant.object
string
(values: ONECLICK, RECURRING, PAYOUT): The type of recurring contract to be used.string
: A descriptive name for this detail.string
: Date after which no further authorisations shall be performed. Only for 3D Secure 2.string
: Minimum number of days between authorisations. Only for 3D Secure 2.string
(values: VISATOKENSERVICE, MCTOKENSERVICE): The name of the token service.object
string
: Card brand.string
: BIN end range.string
: BIN start range.string
: 3D Secure protocol version.string
: In a 3D Secure 2 browser-based flow, this is the URL where you should send the device fingerprint to.object
object
: This field contains additional data, which may be required for a particular request.array
: List of brands.
string
string
: Card number or BIN.string
: The merchant account identifier.string
: A recurring detail reference corresponding to a card.string
: The shopper's reference to uniquely identify this shopper (e.g. user ID or account ID).object
array
: List of Directory Server (DS) public keys.
boolean
: Indicator if 3D Secure 1 is supported.array
: List of brand and card range pairs.
boolean
: Indicator if 3D Secure 2 is supported.FAQs
DataFire integration for Adyen BinLookup API
The npm package @datafire/adyen_binlookupservice receives a total of 0 weekly downloads. As such, @datafire/adyen_binlookupservice popularity was classified as not popular.
We found that @datafire/adyen_binlookupservice demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.