Found 4 packages
Ding.BankCardValidation是基于.net core平台开发的应用框架中的基于支付宝接口实现银行卡号码验证功能组件，可对银行卡进行在线验证，以及获取银行卡所在银行信息等。
Service Objects BIN Validation Libraries utilizing best practices with fail over configuration. This service can be used to Validate a BIN number for credit card transactions. If an entered BIN is valid it will return the Bank Name, card type, country of origin and various other pieces of information. NOTE: In order to use this web service, a License Key is needed. To download a trial License Key with up to 500 transactions, please see the license link of this nuget package. To see more Service Objects web services visit the project page of this package or search the tag "DOTSWebServices".
This library provides a credit card purchase payment authorizer that randomly authorizes a payment (50/50), but only if the credit card number is a valid card number. If the class constructor is called without arguments it instantiates its own ICreditCardValidator. If it is called with an ICardValidator instance then it uses that. This scenario allows for a demonstration of dependcy injection without involving any other components. When paired with the sister project Everyone Is Authorized Client both libraries may be used to create a scenario to demonstrate the problems of a tightly coupled dependency in a SalesOrderManager class. Use this to demonstrate dependency injection and the Adapter Pattern to decouple the authorization from the SalesOrderManager, and then allow for a test-double to be injected in their place. To setup this scenario use the default constructor for each class and ignore the internal card validation. In a real application the classes would not share the same validator interface, they only do in these libraries to help in the first scenario.
This library provides a credit card purchase payment authorizer that authorizes a payment 100% of the time, but only if the credit card number is a valid card number. If the class constructor is called without arguments it instantiates its own ICreditCardValidator. If it is called with an ICardValidator instance then it uses that. This scenario allows for a demonstration of dependcy injection without involving any other components. When paired with the sister project The Bank of Random Credit Authorizer both libraries may be used to create a scenario to demonstrate the problems of a tightly coupled dependency in a SalesOrderManager class. Use this to demonstrate dependency injection and the Adapter Pattern to decouple the authorization from the SalesOrderManager, and then allow for a test-double to be injected in their place. To setup this scenario use the default constructor for each class and ignore the internal card validation. In a real application the classes would not share the same validator interface, they only do in these libraries to help in the first scenario.