cancel
Showing results for 
Search instead for 
Did you mean: 

magento

Hello Sir, In time of payment we send the request data like Card Number, Expiration Date and Card Verification Number along with authorize.net Login Id and Client Key to this following authorize.net CDN url CDN URL: https://js.authorize.net/v1/Accept.js Request Data: {authData: {clientKey: '7JNLgZdUCtK346yft3LB9V465y6RZWYR285CpPzJRmLL6bgpg83qbtW6h3Nf459v', apiLoginID: '536mUBf32'} cardData: {cardNumber: '4315********2000', month: '05', year: '2024', cardCode: '123'}} Response Data: {"securePaymentContainerRequest":{"merchantAuthentication":{"name":"536mUBf32","clientKey":"7JNLgZdUCtK346yft3LB9V465y6RZWYR285CpPzJRmLL6bgpg83qbtW6h3Nf459v"},"data":{"type":"TOKEN","id":"42a8b1b5-0f27-b3c6-177e-1900bd8f6ff2","token":{"cardNumber":"4315********2000","expirationDate":"052024","cardCode"704}}}} From here the authorize.net modify the request data and call authorize.net payment API but sometime after modified the request data new data not a valid json format that’s why the following response error is showing. API URL: https://api2.authorize.net/xml/v1/request.api Request Data: {"securePaymentContainerRequest":{"merchantAuthentication":{"name":"536mUBf32","clientKey":"7JNLgZdUCtK346yft3LB9V465y6RZWYR285CpPzJRmLL6bgpg83qbtW6h3Nf459v"},"data":{"type":"TOKEN","id":"42a8b1b5-0f27-b3c6-177e-1900bd8f6ff2","token":{"cardNumber":"4315********2000","expirationDate":"052024","cardCode"704}}}} Response Data: {"messages": {"resultCode": "Error", "message": [{"code": "E00001","text": "Invalid character after parsing property name. Expected ':' but got: 7. Path 'securePaymentContainerRequest.data.token.expirationDate', line 1, position 303."}]}} So error IS not in the magento end.

SANSHA2080
Member
2 REPLIES 2

I recommend submitting your JSON to a validator such as:

JSON Validator 

marine2026
Trusted Contributor

Look at "cardCode"704

This is not valid JSON.

marine2026
Trusted Contributor