Error when charging

I am getting this error when trying to charge.

"[{\\"message\\":\\"Transaction is required.\\",\\"error_name\\":\\"TransactionValidationError\\",\\"error_code\\":4,\\"raw_message\\":\\"Transaction is required.\\"}]"

Comments

  • Mina Mistry
    Mina Mistry Blackbaud Employee
    Seventh Anniversary Kudos 2 Name Dropper Participant

    Hi Richard

    Can you please share your entire request parameters (mask any guids or sensitive data) and confirm the API endpoint you are calling?

    Thanks

  • @Mina Mistry
    Here is a sample

    {
    "amount":100,
    “billing_contact”:{
    "address":"123 Street,
    "city":"Baltimore",
    "country":"USA",
    "first_name":"Test",
    "last_name":"User",
    "state":"MD",
    "post_code":"21740"
    },
    "credit_card": {
    "exp_month":9,
    "exp_year":2024,
    "name":"Test User",
    "number":"4111111111111111"
    },
    "email":"Testuser@test.com",
    "payment_configuration_id":"payment config here",
    "phone":"123456789"
    }

  • Mina Mistry
    Mina Mistry Blackbaud Employee
    Seventh Anniversary Kudos 2 Name Dropper Participant

    Hi Richard

    This error is typically used when the API is unable to parse your input into the format expected by the API. The first thing is to ensure your parameter types are all accurate and that the GUID being passed in for the payment configuration ID is a valid one (and matches what you got in the GET Payment Configuration List endpoint. You can try using different values to test the request to try and isolate the issue.

    Please let us know if this is helpful or if the issue persists.

    Thank you.

  • Mina Mistry
    Mina Mistry Blackbaud Employee
    Seventh Anniversary Kudos 2 Name Dropper Participant

    Hi Richard

    Another thing to try to help you debug is calling the API from the “Try It” button on the endpoint documentation page here: Blackbaud SKY API Developer Portal. There is also some sample JSON on this page that you can try using (replacing the payment config ID, etc.).

    We are not seeing any additional errors other than what you are already seeing, so something is not parsing correctly in the parameters being used in the current requests. Let me know if this helps.

    Thanks.