Skip to content
This repository has been archived by the owner on Mar 19, 2024. It is now read-only.

Unable to pay via credit-card #12

Open
matthias-94 opened this issue Nov 22, 2022 · 1 comment
Open

Unable to pay via credit-card #12

matthias-94 opened this issue Nov 22, 2022 · 1 comment

Comments

@matthias-94
Copy link

Hello,
it seems there's a problem with paying via credit-card, that seemingly has nothing to do with the SDK itself, but the backend itself.

We have tried to complete a purchase with versions 5.8.4, 5.7.0 and 5.2.0 of the Connect-SDK. It didn't work with any of these versions.

The error does not appear on iOS, despite using the same backend with the same data.

Our server is receiving the following error message from the payment-API:

{"error":{"code":0,"errors":[{"category":"PAYMENT_PLATFORM_ERROR","code":null,"httpStatusCode":403,"id":"AUTHENTICATION_FAILURE","message":null,"propertyName":null,"requestId":null}],"id":"637cc58d9ee44132e8ac58faa5fea8dc","result":{"creationOutput":null,"merchantAction":null,"payment":{"hostedCheckoutSpecificOutput":null,"paymentOutput":{"amountPaid":null,"amountReversed":null,"bankTransferPaymentMethodSpecificOutput":null,"cardPaymentMethodSpecificOutput":{"authorisationCode":null,"card":{"cardNumber":"XXXXXXXXXXXX4675","expiryDate":"1225"},"fraudResults":{"avsResult":null,"cvvResult":null,"fraugster":null,"retailDecisions":null,"fraudServiceResult":"no-advice","inAuth":null},"initialSchemeTransactionId":null,"schemeTransactionId":null,"threeDSecureResults":{"acsTransactionId":null,"appliedExemption":null,"authenticationAmount":null,"cavv":null,"directoryServerTransactionId":null,"eci":"92","exemptionOutput":null,"schemeRiskScore":null,"sdkData":null,"threeDSecureData":null,"threeDSecureVersion":null,"threeDServerTransactionId":null,"xid":null},"token":"62cdd10b-f5a2-47e4-9cf3-c693705b9f82","paymentProductId":1},"cashPaymentMethodSpecificOutput":null,"directDebitPaymentMethodSpecificOutput":null,"eInvoicePaymentMethodSpecificOutput":null,"invoicePaymentMethodSpecificOutput":null,"mobilePaymentMethodSpecificOutput":null,"paymentMethod":"card","redirectPaymentMethodSpecificOutput":null,"reversalReason":null,"sepaDirectDebitPaymentMethodSpecificOutput":null,"amountOfMoney":{"amount":1000,"currencyCode":"EUR"},"references":{"merchantOrderId":null,"merchantReference":"207fb17f-b81e-56b7-373f-834810442feb","paymentReference":null,"providerId":null,"providerReference":null,"referenceOrigPayment":null}},"status":"REJECTED","statusOutput":{"isAuthorized":false,"isRefundable":false,"threeDSecureStatus":null,"errors":null,"isCancellable":false,"statusCategory":"UNSUCCESSFUL","statusCode":2,"statusCodeChangeDateTime":null},"id":"3245942022_0"}}}}

Any help would be greatly appreciated. Thanks.

@IngenicoEPayments
Copy link
Contributor

Hello Matthias,

Apologies for the delayed reply. Does the issue still occur?

For issues with payments and the server in general, you should initially inquire with the support team. If you have not done so yet, please contact them.

We do however, understand you are perceiving differences between both SDKs. We may be able to help out if you could answer the following questions.

  • Are you executing the exact same scenario on both platforms?
    • What scenario are you testing with? (What payment product, amount, currency, etc.)
    • Can you verify that the requests that the SDKs make are exactly the same?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants