-
Couldn't load subscription status.
- Fork 2.2k
Closed
Milestone
Description
Expected behavior
Credit card transaction goes through
Actual Behavior
Client Recieves a 'Match failed [400]' error.
The server reports the following:
Exception while invoking method 'authnetSubmit' Error: Match error: Failed Match.Where validation in field cardNumber
at exports.check (packages/check.js:57:15)
at [object Object].Meteor.methods.authnetSubmit (imports/plugins/included/payments-authnet/server/methods/authnet.js:44:5)
at packages/check.js:130:16
at [object Object]._.extend.withValue (packages/meteor.js:1122:17)
at Object.exports.Match._failIfArgumentsAreNotAllChecked (packages/check.js:129:41)
at maybeAuditArgumentChecks (packages/ddp-server/livedata_server.js:1734:18)
at packages/ddp-server/livedata_server.js:719:19
at [object Object]._.extend.withValue (packages/meteor.js:1122:17)
at packages/ddp-server/livedata_server.js:717:40
at [object Object]._.extend.withValue (packages/meteor.js:1122:17)
at packages/ddp-server/livedata_server.js:715:46
at [object Object]._.extend.protocol_handlers.method (packages/ddp-server/livedata_server.js:689:23)
at packages/ddp-server/livedata_server.js:559:43
Sanitized and reported to the client as: Match failed [400]
Steps to Reproduce the Behavior
Enable Authorize.net payments in 'Live - Production Mode'
Enter correct card information
Observe Error message
I understand clearly that this seems like a simple mis-entered card. I have entered this card across multiple browsers on multiple machines. The system returns the Error: Match failed [400] error every time.
This happens regardless of firewall (or lack of) settings on the server.
P.S. I checked with the Authorize.net to ensure that the company account is in good standing. Both times I checked Authorize.net assured me that, "there is no reason why the transactions should not go through."
Metadata
Metadata
Assignees
Labels
No labels