nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

New to SKY - Trying to place my first test charge

WBT Tech

One of our clients uses SKY for their payment system so I've been working my way through learning this system.

I can successfully perform the OAuth requests and get the access_token.

I'm now trying to do a test charge to a fake credit card number, but so far all I can get back is “Bad Request”.

I'm following the example from this page:

and it says only the amount and payment_configuration_id are required, but it seems like it would need some kind of credit card info as well, so I've included that in the request body.

I made a successful call to “paymentconfigurations” with my id and access token, so I know those are working.

I'm sending the “CreateTransaction” JSON request body below:

{
"amount":100,
"credit_card": {
"exp_month":2,
"exp_year":2026,
"name":"DC Test",
"number":"4111111111111111"
},
"csc":"234",
"payment_configuration_id":"280baa2b-ee01-4f47-9a1f-b58d44d5f79d"
}

What other information do I need to pass in this request so it will not be rejected as a “bad request?”

Find more posts tagged with

Comments

Mina Mistry

Hello

Thanks for posting your question. Per our logs I am seeing a couple of recent successful requests to the Transaction endpoint. Are you able to now successfully process a test or live transaction?

If you are still having any difficulty, please add the full exception message here and we can provide some guidance.

Thanks

Mina

WBT Tech

Thank you for your reply. I worked my way through the fields, adding them one by one, and finally got to a point where the request started being accepted.

For anyone else just starting out, you'll need to pass roughly this set of data before the request will be accepted:

{
"amount":100,
“billing_contact”:{
"address":"1234 Road",
"city":"Ann Arbor",
"country":"USA",
"first_name":"Sky",
"last_name":"Tester",
"state":"MI",
"post_code":"48108"
},
"credit_card": {
"exp_month":2,
"exp_year":2026,
"name":"DC Test",
"number":"4111111111111111"
},
"csc":"234",
"email":"sTester@email.com",
"payment_configuration_id":"280baa2b-ee01-4f47-9a1f-b58d44d5f79d",
"phone":"1112223333"
}

Dean Mercer

@Mina Mistry We did have an intgration to this endpoint that was working. It stopped working about two days ago but we did not make any changes on our end. Is this still working for you?

Mina Mistry

Hi @Dean Mercer

I see some recent transaction errors related to address verification / card security code - these details are passed back in the API response. The payment configuration record is where these are set.

For information on AVS and CSC levels please see What are the Card Security Code (CSC) settings in the merchant account settings? and What are Address Verification System (AVS) Settings?

If you continue to see errors and you need us to look at a specific transaction ID, please file a request through Support with details of the API request and response. Unfortunately, we cannot handle specific cases via this community to protect customer data and confidentiality.

Thanks!

Mina