Replies: 1 comment
-
Hello @damianham! We understand your point of providing the developers with more control of the whole process when desired. Also, because the linked page is a guide to help to integrate as fast as possible, I recommend you to have a look at our technical documentation at this current repository, where we specify the methods with more detail. The API section is where we describe the core methods that enable an integration in which you are able to control the whole process. I hope it helps you! Also, don't hesitate in contacting us again when needed. |
Beta Was this translation helpful? Give feedback.
-
I have been looking into integration of the SDK to create subscriptions. While reading the documentation - the section relating to creating a token for a customer credit card referred to the web checkout integration page which contained examples of code to integrate a web form to capture customer card data to convert to a token.
After spending 1.5 days reading the documentation and integrating the form as per the documentation into a web page the image attached below was the result of the form submit. This doesn't fill me with confidence to deploy this into production. I think you have gone about this entirely the wrong way. There is nothing wrong in having an SDK to make secure requests to your server APIs. However a developer should be able to make individual requests at each stage of the process and have a much greater degree of control over the whole process.
Rather than exposing a method to manipulate a web form e.g.
const mp = new MercadoPago('TEST-f0190789-1218-4810-9bb1-6d8280cd969a') cardForm = mp.cardForm({
Why not expose the helper methods to convert the card number to the issuer, the valid document types, expiry date formatting etc. Developers are entirely capable of building web forms that conform to their website style and using onChange handlers to handle data change events. Developers are entirely capable of submitting requests to APIs and dealing with the results. The SDK should expose methods to assist in doing so securely rather than be concerned with HTML form handling.
With epayco the process is
register a customer -> return customer ID
register a card for the customer -> returns a token
subscribe the customer to the service with the token -> returns a subscription ID
charge the subscription
All POST requests with JSON encoded data, simple and reliable. There are no issues with form styling or server errors, although epayco have other issues.
Beta Was this translation helpful? Give feedback.
All reactions