Re: status: 'BAD_REQUEST', code: 'NPPS012', message: 'Bad request'

kunalPrometteu
New Contributor

status: 'BAD_REQUEST', code: 'NPPS012', message: 'Bad request'

Getting this error for the https://sandbox.api.visa.com/visadirect/fundstransfer/v1/pushfundstransactions API

Here are the details:
1. URL

2. headers

3 body (payload data, normal and encrypted attached both)

 

{
'x-client-transaction-id': '1612321873781263',
Accept: 'application/json',
'Content-Type': 'application/json',
payload: {
surcharge: '11.2',
senderAddress: '901 Metro Center Blvd',
pointOfServiceData: { panEntryMode: 90, posConditionCode: 0, motoECIIndicator: 1 },
recipientPrimaryAccountNumber: '4104920120500001',
colombiaNationalServiceData: {
addValueTaxReturn: 10,
taxAmountConsumption: 10,
nationalNetReimbursementFeeBaseAmount: 20,
addValueTaxAmount: 10,
nationalNetMiscAmount: 10,
countryCodeNationalService: 170,
nationalChargebackReason: 11,
emvTransactionIndicator: 1,
nationalNetMiscAmountType: 'A',
costTransactionIndicator: '0',
nationalReimbursementFee: 20
},
transactionIdentifier: 617020001849971,
serviceProcessingType: { requestType: '01' },
acquiringBin: 408999,
retrievalReferenceNumber: '412770451036',
systemsTraceAuditNumber: 451018,
senderName: 'Mohammed Qasim',
businessApplicationId: 'AA',
settlementServiceIndicator: 9,
transactionCurrencyCode: 'USD',
recipientName: 'rohan',
sourceAmount: 123.12,
senderCountryCode: '124',
senderAccountNumber: '4104920120500002',
amount: 124.05,
localTransactionDateTime: '2024-05-23T18:41:07.000Z',
purposeOfPayment: 'purpose',
cardAcceptor: {
address: [Object],
idCode: 'CA-IDCode-77765',
name: 'Visa Inc. USA-Foster City',
terminalId: 'TID-9999'
},
senderReference: '',
acquirerCountryCode: 840,
sourceCurrencyCode: '840',
senderCity: 'Foster City',
senderStateCode: 'CA',
merchantCategoryCode: 6012,
sourceOfFundsCode: '05'
}
}
{
httpsAgent: Agent {
_events: [Object: null prototype] {
free: [Function (anonymous)],
newListener: [Function: maybeEnableKeylog]
},
_eventsCount: 2,
_maxListeners: undefined,
defaultPort: 443,
protocol: 'https:',
options: [Object: null prototype] {
cert: <Buffer 2d 2d 2d 2d 2d 42 45 47 49 4e 20 43 45 52 54 49 46 49 43 41 54 45 2d 2d 2d 2d 2d 0a 4d 49 49 44 77 54 43 43 41 71 6d 67 41 77 49 42 41 67 49 49 47 58 ... 1312 more bytes>,
key: <Buffer 2d 2d 2d 2d 2d 42 45 47 49 4e 20 52 53 41 20 50 52 49 56 41 54 45 20 4b 45 59 2d 2d 2d 2d 2d 0a 4d 49 49 45 6f 77 49 42 41 41 4b 43 41 51 45 41 6a 34 ... 1625 more bytes>,
noDelay: true,
path: null
},
requests: [Object: null prototype] {},
sockets: [Object: null prototype] {},
freeSockets: [Object: null prototype] {},
keepAliveMsecs: 1000,
keepAlive: false,
maxSockets: Infinity,
maxFreeSockets: 256,
scheduling: 'lifo',
maxTotalSockets: Infinity,
totalSocketCount: 0,
maxCachedSessions: 100,
_sessionCache: { map: {}, list: [] },
[Symbol(kCapture)]: false
},
headers: {
'Content-Type': 'application/json',
Accept: 'application/json',
Authorization: 'Basic WTA3VkwxVTZKNDlHQ1BCREFFTU4yMTZSVFlkc1FiNDBGVWF5ajA3Nk9OZFFKQzJVdzpkZjU4Z2YwaHNGV2k3UExVVQ==',
keyId: 'b12faae9-c546-4651-b272-fdd424ac64eb'
},
url: 'https://sandbox.api.visa.com/visadirect/fundstransfer/v1/pushfundstransactions',
method: 'POST',
data: {
encData: 'eyJpYXQiOjE3MjE3MzM2MjM5MDgsImVuYyI6IkExMjhHQ00iLCJhbGciOiJSU0EtT0FFUC0yNTYiLCJraWQiOiJiMTJmYWFlOS1jNTQ2LTQ2NTEtYjI3Mi1mZGQ0MjRhYzY0ZWIifQ.C4bGE0_R7WlaBSeG8DI1y7GJS0g1OKnNWmTnLm4DkxYzt8-8uRXObjX6ZmUkY1_tsjlO3VadfrTaOWrofprgRQw8A10adX2RSbCrFbqX8i1Vcj5YiICi_vFfx4AZYJ-pnUVh9gRzFUEjvpL6gkEbAJt_rdOfMhGz0NJ-iyApp59BTJitiRMi72-0j99nj01wr1NA1oOTApEZu0yDk0M_TLvoeqxRlpwn_bhBeqSLFtoosqGv0WUmAYNZ2bUluMtj9DsF3P8qh8_rRe0ZpNR7Y97F53HiIYQ8C2coClzLlCGlE6MJG9M5YsYnjqyTREvF8p8SUJwbBSUegIud2JcffQ.06pgtXGIdRQmF58J.Mt1u1YWFh2FPjIkYE0dpouqbP44HedPAfvF1EzW85RpAzgO3W4VapDc12OrXrMC7zM5OmORGKkgcE3_v2wxLoNBNO79SaZhgqAutVaYZwkFRGgiUrT-y-lARYaoRXVXlAXzthpvsTwIl_fAfPHtN3IBifsTspw-Em8ebIByrarpnVUcLbod-ShAeXsFPlAUwYbcr_ZQpW025_PGpEP3ZZXJ0LE7KtCIzidIAo45xcusaOFsX3Qu9LYcEEXA8YC2Q4R3VPge64dWyTZl1AiRp1gNlrCUV4zNwMOJoJz4dOoG1xEfccoqEBl7FgbyXdqA-7O2a7VlcI72ZEoowXfKAz3pp1aIWOFef9M-p5Yd-YIbEEn_dZK2mrmskF-eHTuEFsh_ol5ob_QjTNHNOJvCM9TG82DiI1g3L0almxppcNWzRPOPCpm1Bi1yhaoIAodoZCuWV6jKuOaF90bMthX3A-mkVsl2EkQ_wY8v3o0aVzuprs0O4olfm5sKJ6F-bc_AclSqfLrrN-tmgiAxj6xW1Ld3-nCEwXm1Z5eHOin1e-4Of0CCE9xn-hlEUJwHsKcdHmgvzM3DU0vL7nVLgt9Q8ZsebQwUMg1jUi4pJaHZ56ET4H-JlNU6WYv7bcBXzcctiUeH_IsQQ7N3b4Te-7cmD2vjBL-UrTvwDyXMe_7Aap-Xs2UTx26W8K8HltnpdhAG_TrPSt16rY0KD9bRVvTtznBgAjc0eGWXLL82AlwNpIen3B94somX6Zt5DRYB0UfNCq1BLqabV8Wu8qwaM3phhsQ9m9OV9HSxLm9IHT02zswIBPa8T2ZrwHtB_KQlt2d-bF6Hf5BIo7gSi7LfiN-rcHBzFb-P8BdIp3Qwqu-m2jou1j4pk0oN9tGVf29Uy5eQ8dxl1NgFI4IIBEZx4RweIwC_1RNuaxiUAZnDnYarvAAsGaDcaYobInXmq_eNYNg8Sz0Bzna_pxR3TkNYegDkw46HEJVhHsY8GT5fyzhvDK1x3iqXudZwJsdzV4ZAHiwwj0dfqvV2Bp015Ian-aIPFum7OEiR3yDbd6L8I90MHpE2IMI80Uz3wj3l7UGLFkCVq9lFoE03YACYehLNyc0A4eIWPKcaQkD7YXFyZ_4q_bgVjTzfkdL7ClWOfWHEeCdeEzqOmGQPbSGac7LSXUekdP4Yws_jiLeK2t_aX7-NvFnmEsgMI9C66GR0M7ADmuWN20o0TpyuWDWaWfG1h-JK8YY_qgDMdVyTW-AAmbvOEczlh8_vZwDEYnrgGYqU5pzlerxrvwenpH8x6OkhTdhKxUPMxnlkNoNJPGOihpyCNdqNbi3HBSo1gfGWNae5uXlyeXAT1Q1xMaVqTROgeviYlHrlLsOYZqH5X19yYyCej6MUf5mPsbhEUaHJQ8GUlXKSXuGKkpKq8SVumBLWWQMncyqSBaZZe08k6NA7VmzANNiyteslDa3jwA7gVuHax47HFANDnVxp4jAmaAyDWgGY6ZfnUn2sQsEmCXdi32fiRYEESTVj0xwJvFaZOwaoB0WmTsZ40V7B6-jF1q_C-jGZW2RYR7RrUanGgp8dI0pH3fCuinxelEYzTYs_yZfNP0TiPZanMqyYRF6MLY4V_8PteJLtghoypEPuJgtT_-kba4IzvfNW7KIdXXcWPdHFoe9LJT_2iPIpnOWKHJfCNE8GAMzS9HJpAxZW_Gh-cRpCt6Z9e-A7iTcl2fj1BMPVgNOis9I0lGnpQc69cHgx9t2aXy9ps6yk2HiDGg-_Sv-I9aHnGq5AmL9601wxB6iF9H4WKPbqNWeJNcrH0y8mVtOKVZbZ7vn6B4gqzvR5tyL0aE8cBdZuwe0g4lRGx1YvH2Na-a729mFH5bhMPrUuccEGwE0CGdKD4TX9C-xSGozXWksSs6MGNY8EaKh0M6uKhkrhy.idW1LLrQticDcWgeGuIzIQ'
}
}

5 REPLIES 5
jenn_kh
Community Moderator

Re: status: 'BAD_REQUEST', code: 'NPPS012', message: 'Bad request'

Hi @kunalPrometteuThank you for reaching out. One of our agents will look into this and get back to you soon. In the meantime, if any community member knows a solution, feel free to reply to this thread.

API_Products
Visa Developer Support Specialist

Re: status: 'BAD_REQUEST', code: 'NPPS012', message: 'Bad request'

Hey @kunalPrometteu,

 

Are you still experiencing an error? If so please refer to the Error Codes page for cause/resolution. Let us know if the error persists.




Thanks,

Diana



Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.

javascript2018-
Regular Visitor

Re: status: 'BAD_REQUEST', code: 'NPPS012', message: 'Bad request'

if you have already solved this that is good and if not, contact me I can do it one time

Rubel Hossain
shindevishnu31
New Contributor

Re: status: 'BAD_REQUEST', code: 'NPPS012', message: 'Bad request'

I am also facing similar issue for {{baseUrl}}/connect/v1/cardServices/new api

API_Products
Visa Developer Support Specialist

Re: status: 'BAD_REQUEST', code: 'NPPS012', message: 'Bad request'

Hey @shindevishnu31,

 

Based on the review of the developer.visa.com platform pages, here are the steps and clarifications to address the error encountered when attempting to call the `{{baseUrl}}/connect/v1/cardServices/new` API:

1. Endpoint Verification:
- Ensure that the `baseUrl` is correctly set and that the full endpoint URL is constructed properly. For example, the endpoint URL should be something like:
```
https://sandbox.api.visa.com/connect/v1/cardServices/new
```

2. Request Headers:
- Verify that all required request headers are included and correctly set. Common headers might include:
```
Authorization: {your_authorization_token}
Accept: application/json
Content-Type: application/json
```

3. Request Body:
- Ensure that the JSON payload in the request body is correctly formatted according to the API documentation. Double-check that all required fields are present and correctly structured.

4. Error Code NPPS012 - Bad Request:
- The error code `NPPS012` with the message "Bad request" indicates that there is likely an issue with the request payload or headers. This can happen if required fields are missing, incorrectly formatted, or if there are invalid values.

5. Common Issues to Check:
- Missing or Invalid Fields: Ensure that all required fields are included in the request body and that they have valid values.
- Incorrect Data Types: Verify that the data types of the fields in the request body match what is expected by the API.
- JSON Formatting: Ensure that the JSON payload is correctly formatted and does not contain any syntax errors.

6. Example Request Payload:
- Here is an example of what a correctly formatted request payload might look like:
```json
{
"cardNumber": "4111111111111111",
"expirationDate": "12/2023",
"cardholderName": "John Doe",
"billingAddress": {
"street": "123 Main St",
"city": "San Francisco",
"state": "CA",
"postalCode": "94105",
"country": "USA"
}
}
```

7. Further Assistance:
- If the issue persists, please share the detailed error message, the request payload, the X-Correlation ID and the steps you have taken for troubleshooting.

By following these steps and ensuring that all aspects of the request are correctly configured, you should be able to resolve the error and successfully call the `{{baseUrl}}/connect/v1/cardServices/new` API.

 




Thanks,

Diana



Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.