html error response about frames-ios

[nicolas-maalouf-cko]

Hi @ViktorAmelin

It seems you are mixing 2 endpoints here:

1. https://sandbox.checkout.com/api2/v2/tokens which is the only URL that can be called directly from mobile SDKS with the API public key
2. https://api.sandbox.checkout.com/payments which is to be used from a backend server with the API secret key along with the temporary card token obtained in 1)

Please make sure to never use any endpoints involving the secret key from a mobile app. This would be breaching PCI compliance

The flow with mobile SDKs should be as follows:

[ViktorAmelin]

Hello. I've talked with our backend developer, and he told that the chain above is correct and we don't mix endpoints.
This is what we are getting from you. Can you check what's going on there?

checkout.rtf.zip

[nicolas-maalouf-cko]

Hi @ViktorAmelin
This would happen if you call https://sandbox.checkout.com/api2/v2/payments which is an invalid URL

https://sandbox.checkout.com/api2/v2/tokens is the URL that needs to be called from the app and
https://api.sandbox.checkout.com/payments the one from your backend server

[ViktorAmelin]

@nicolas-maalouf-cko Hello. Are the links in your framework are correct:
var urlApi: String {
switch self {
case .live:
return "https://api2.checkout.com/v2/"
case .sandbox:
return "https://sandbox.checkout.com/api2/v2/"
}
}

var urlPaymentApi: String {
    switch self {
    case .live:
        return "https://api.checkout.com/"
    case .sandbox:
        return "https://sandbox.checkout.com/api2/"
    }
}

[nicolas-maalouf-cko]

These work, but we are releasing an updated SDK soon with the latest URLs

[nicolas-maalouf-cko]

Hi @ViktorAmelin 3.0.1 is now released

[nunepradeepkumar]

Hi ,
How to change the pay button position in default frame.