You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Hosted payment page error after filling out payment information #99
Upon clicking pay you get an error "Unexpected error. Please try again."
I have tried several different ways to generate the token as well as several different types of credit card numbers (all test numbers) and amounts, etc. I cannot get a working sample to go through.
I even tried to do this in a production environment and had the same result. Can someone please let me know what exactly this error is?
You can duplicate the error using the sample codes api login or with any generated one from the sandbox.
Hi,
Apologies for the inconvenience caused.
There seems to be a bug in the way that DateTime values are handled in the C# SDK.
A fix has been sent and is pending release ( .NET SDK #257 ).
Your code for doing the payment does not have any issues. I believe the issue is from the GetAnAcceptPaymentPage sample, if you are also using the order information in the request.
A temporary workaround for this is to include a valid date for order.purchaseOrderDateUTC in the format "YYYY-mm-dd".
transactionRequest = new transactionRequestType {
amount = "100.00",
transactionType = transactionTypeEnum.authCaptureTransaction.ToString(),
order = new orderType {
invoiceNumber = invoiceId,
description = invoiceId,
purchaseOrderDateUTC = new DateTime(2018, 03, 23, 11, 00, 00, DateTimeKind.Utc)
}
}
Yikes. Five months later and this is still not fixed. For anyone trying to resolve this issue, I was able to get the sample code working by reverting to 1.9.6.
Still an issue as of now. Workarounds are either to leave the 'order' undefined, or to revert to dotnet SDK version 1.9.6. On reviewing the API documentation here, it seems like the orderType object has a lot of new fields in version 1.9.7 and later, that don't seem to be defined in the API as of today.
Upon clicking pay you get an error "Unexpected error. Please try again."
I have tried several different ways to generate the token as well as several different types of credit card numbers (all test numbers) and amounts, etc. I cannot get a working sample to go through.
I even tried to do this in a production environment and had the same result. Can someone please let me know what exactly this error is?
You can duplicate the error using the sample codes api login or with any generated one from the sandbox.
Activity
gnongsie commentedon Mar 6, 2019
Hi,
Apologies for the inconvenience caused.
There seems to be a bug in the way that DateTime values are handled in the C# SDK.
A fix has been sent and is pending release ( .NET SDK #257 ).
Your code for doing the payment does not have any issues. I believe the issue is from the GetAnAcceptPaymentPage sample, if you are also using the order information in the request.
A temporary workaround for this is to include a valid date for order.purchaseOrderDateUTC in the format "YYYY-mm-dd".
sstalder commentedon Mar 6, 2019
In the .NET SDK the purchaseOrderDateUTC is a DateTime type. How are you putting a string for that value?
Can this fix also be moved to the dotnet core sdk as well?
sstalder commentedon Mar 7, 2019
Unfortunately the workaround proposed doesn't appear to work. The only way I can get it to go through is to not include the "order" object.
gnongsie commentedon Mar 13, 2019
Hi,
Apologies for the inconvenience. I initially thought this would fix the issue.
In any case, I have escalated this to the relevant team and will update this thread with the progress.
sstalder commentedon May 16, 2019
Hey Gabriel, has there been any update on this issue? Thanks!
esw0000000 commentedon Aug 21, 2019
Yikes. Five months later and this is still not fixed. For anyone trying to resolve this issue, I was able to get the sample code working by reverting to 1.9.6.
SeriaWei commentedon Mar 2, 2020
Is there any plan to fix this issue? I have to return to use
1.9.6to make it works.ahawes-clarity commentedon Apr 15, 2020
Almost a year later. Any fix for this?
w7tcp commentedon Mar 3, 2021
Still an issue as of now. Workarounds are either to leave the 'order' undefined, or to revert to dotnet SDK version 1.9.6. On reviewing the API documentation here, it seems like the orderType object has a lot of new fields in version 1.9.7 and later, that don't seem to be defined in the API as of today.
popisms commentedon Apr 29, 2024
FIVE YEARS LATER, and this bug still has not been fixed.
krunalp-pulse commentedon Dec 23, 2024
I had the same problem with the most recent versions, however it was resolved once I used version 1.9.6.
Does anyone want a demo code for that?
Elizabeth-has commentedon Jan 29, 2025
devGBG commentedon Feb 5, 2025
Any update on the issue?
esw0000000 commentedon Feb 5, 2025
There are open issues going back six years. The last functional version appears to be 1.9.6. It's essentially abandonware.