This is on a test environment.
Using D365 Retail.
Modern Point of sales (MPOS)
The terminal device is a Verifone P400Plus from Adyen.
I'm getting this error on the MPOS when paying with a credit card:
"The card type is not an accepted form of payment. Use a different
payment card, and then try again"
The card I'm using is a test card with the following details:
Mastercard/Maestro
EXP: 31/12/2025
Version: 012
Cardnumber: 541333 **** 9999
Type: CREDIT
In D365\Retail\Channel setup\POS setup\Hardware profiles, I've added Master and Maestro card to the hardware profile:
In D365\Retail\Channel setup\Payment methods\Card numbers, I've added the card number on both MasterCard and Maestro
In D365\Retail\Channel setup\Payment methods\Card types, the cards are also present
Job 1070 and 1090 has been applied.
I might be missing something that I don't know about, but I've no clue what to look for. Any suggestions?
EDIT
I did a full push, but the same error happens.
So I found what was causing the MPOS to trigger the error. It was due to the card type. The mastercard was configured to have the "Card types" value set to "International debit card".
In the js file "Commerce.Core.js" line 49377, the code calls the method "Commerce.PaymentHelper.isCreditCard(...) where it checks for the credit card.
When my mastercard was configured to "International debit card" the if statement inside of the method wasn't true so my card would always be rejected. Changing the Card types value for mastercard to "International credit card" or "Corporate card" solved my problem.
Related
I'm setting up Spamassassin to use along isbg to filter mail in my IMAP mail account. My ISP already has a pretty good spam filter that adds "[SPAM]" in front of the subject line of each message it detects; thus, I'm setting up a custom rule in Spamassassin so that it adds a high score to any mail which Subject line starts with "[SPAM]". My user_prefs file is:
required_score 9
score HTML_COMMENT_8BITS 0
score UPPERCASE_25_50 0
score UPPERCASE_50_75 0
score UPPERCASE_75_100 0
score OBSCURED_EMAIL 0
score SUBJ_ILLEGAL_CHARS 0
header SPAM_FILTRADO Subject =~ /^\s*\[SPAM\]/
score SPAM_FILTRADO 20
And yet, when I feed it a spam message to test it, it doesn't seem to trigger my rule. I feed it an email with this subject line, for example:
Subject: [SPAM] See Drone X Pro in action
And I analyse it in this way:
[paulo#myserver mails]$ spamc -R < spam7.txt
9.3/9.0
Spam detection software, running on the system "myserver", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
##CONTACT_ADDRESS## for details.
Content preview: Big Drone Companies Are Terrified Of This New Drone That Hit
The Market <http://www.fairfood.icu/uisghougw/pjarx44255sweouci/I31AAdtTTKmLsu_A6Dq7ZK_a47Ko45fCRXk7Fr9fqm4/BbYMgcZjieuj_YxMOSmnXetiI6e4Z37yS9H2zVIeHEilOpatuk8V8Mt0EtJDfLLE1llzj6MiwlLzR99DGODekcqeM7kn63lcFcp8fJutAsw>
[...]
Content analysis details: (9.3 points, 9.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
2.4 DNS_FROM_AHBL_RHSBL RBL: Envelope sender listed in dnsbl.ahbl.org
2.7 RCVD_IN_PSBL RBL: Received via a relay in PSBL
[193.17.4.113 listed in psbl.surriel.com]
-0.0 SPF_PASS SPF: sender matches SPF record
1.3 HTML_IMAGE_ONLY_24 BODY: HTML: images with 2000-2400 bytes of words
0.0 HTML_MESSAGE BODY: HTML included in message
1.6 RCVD_IN_BRBL_LASTEXT RBL: RCVD_IN_BRBL_LASTEXT
[193.17.4.113 listed in bb.barracudacentral.org]
1.3 RDNS_NONE Delivered to internal network by a host with no rDNS
There isn't anything about my rule.
I know that my user_prefs is being loaded because, after the section I pasted above, I have some email addresses set up in a whitelist, and when analysing emails coming from those addresses, Spamassassin correctly detects them.
What's wrong with my rule?
Support for custom rules in user_prefs file is turned off by default.
You may use item_allow_user_rules in global configuration to change it.
I am using statvfs() to find out the available space on a uSD card. statvfs() returns expected results if I call it when the uSD card was plugged in from boot, but if I call statvfs() after I unplug the uSD statvfs() returns success and odd numbers for the number of blocks. If I call statvfs() when the uSD card was not plugged in from boot statvfs() correctly returns -1 for failure. Why doesn't statvfs() return -1 when I call it after I unplug the uSD? Is this a known issue?
Booted with uSD:
SUCCESS,
f_blocks:51091,
f_bsize:2048,
f_fsid:2049,
f_bfree:48922,
f_flag:3072
Removed uSD:
SUCCESS,
f_blocks:4096,
f_bsize:4096,
f_fsid:0,
f_bfree:4096,
f_flag:4096
Booted w/o uSD:
FAILURE
The uSD is 32 GB.
Thanks.
I think the comment by "lurker" on this question is what I was looking for on how to properly detect the uSD card being removed.
I have some card, wanted to get ATR from it (using method from some SDK).
Implementation looks like this:
unsigned char ATR[128]={0};
int len=33;
int maxlen=33;
ret = sd7816_ATR(0,1,ATR,len,maxlen,1);
first, second and last parameters to sd7816_ATR function should be like that.
The length fields I tried changing to different values, including 0 but no help.
My concern is the ATR string I am sending is empty in the beginning, and I am expecting
something to get written in it after the call finishes (which actually returns success).
But after call ATR is still empty .. What can be going wrong here?
(I want to find out if card is of ISO/IEC 14443 or ISO/IEC 7816 type).
You are trying to receive an ATR for a command specific for a ISO/IEC 7816-3 contact card. In this particular case, that's requested from a (SIM form) SAM card reader. However, you are trying to read out the contactless based reader.
Now contactless cards do not have an ATR. Some cards do have an ATS (i.e. ISO/IEC 14443 Type A cards), but that should be requested by a similar 14443 SELECT command. Some cards, particularly Type B cards, contain an EF.ATR to make up for the lack of (space within the) ATR. Still, an ATR/ATS has only limited functionality for identifying cards.
ISO/IEC 7816 is comprised of several parts: parts 1 to 3 describe contact cards and 4 and higher describe the Application level APDU commands and file structure of processor cards. If your contactless card implements ISO/IEC 7816-4 then you can - in general - also directly use the PCSC interface to send and receive APDU's to/from the card.
In general readers are for contact or contactless only. If you have a reader which contains both contact and contactless operation then in general they will show up as two different readers in the operating system. So in general, if you know the reader, you know if the card is a contact card or contactless card.
SAM slots may not be identified as readers by the operating system - you may only be able to access them using a low level interface. They are mainly used as a secure storage of keys from the terminal/inspection system/interface device or whatever the name is of the system that reads out the card.
HP Insight Diagnostics Version 8.4.0.3521A (x86_64)
Computer Name: ezsetupsystem3c4a927c9e88
During Device test it gives following error
Total Memory-ECC test Failed
Description- Uncorrectable ECC Events occurred in SEL log Device, Ran on CPU 0
Recommended Repair- Please refer IPMI Sensor Event Log for ECC events
Error Code- 021278
Please help me n finding why is this error coming.
Is it because of WAMP server installation??
This means that the server has a DIMM which has exceeded it's acceptable ECC error count. It's location is denoted in the error. Depending on the platform, you can identify the specific slot. Which HP ProLiant model is this? This is standard warranty repair.
You have faulty memory. To identify the faulty memory run HPS Reports:
http://update.external.hp.com/HPS/HPSreports/
Once completed you have to unzip the archive an open the index.html file insite.
It will collect all hardware information and highlight in
RED
the faulty components.
I just want to get confirmation on Battery Temperature data.
I am using GetSystemPowerStatusEx2 API to get battery temperature for windows ce device using c++..
I am using the variable say "psse" of type "SYSTEM_POWER_STATUS_EX2".
On success, the value returned for battery temperature is mentioned below:-
psse.BatteryTemperature = 29 //which is of dword type.
My doubt is what is the actual battery temperature representation?
Is it 2.9 degree celsius or 29 degree celsius & why?
Plz reply. Thanks in advance.
According to the documentation on MSDN
Battery temperature in degrees Celsius. This member can have a value in the range of –3,276.8 to 3,276.7; the increments are 0.1 degrees Celsius.
So a value of 29 means 2.9 degrees Celsius.
did you zero out the BatteryStatusEx2 struct memory to zero before calling the function?
OTOH the OEMs can, but do not need to fill all values correctly. So if the function returns 29, which is 2.9°C, I assume the OEM does not fill the value correctly. Either it is ment as 29°C, which is alos not a real value over time, as the battery temperature should go up during usage of the device.
Posibly the OEM offers a new firmware or service release for the device which corrects the wrong reading.
The accuracy of the values depends on the implementation of the driver. Possibly the battery does not expose any temperature at all and the driver always fills the struct with the value 29.
Do not trust to much in OEMs implementing all features correctl all the time.
~josef