Webservice payments

This payment process consists of three phases:

1. Generate the payment order.
   • The merchant sends the payment characteristics to the /payment endpoint.
   • Paylands returns an order object along with its UUID which will be used to finalize the payment.
   • IMPORTANT: with this method, the customer_ext_id field sent to /payment is mandatory, and must match the customer_ext_id used when saving the card in the system.
2. Complete the payment
   • The merchant completes the payment with the UUID of the order and the UUID of the card stored in the system. For this, a request has to be made to the /payment/direct endpoint.
   • The UUID of the card can be obtained from the notification of a previously completed payment or from the response of saving a card in the system.
   • If a new card is to be used, it must first be tokenized to obtain the corresponding UUID.
   • Paylands checks this data, processes the order and synchronously returns the result of the transaction.
   • Depending on the card issuing bank, the bank may require the transaction to be finalized by 3DS, which requires user intervention. In this case the response will contain a URL which the merchant must redirect the user to finalize the payment.
3. Notification
   • If a url_post was sent when generating the payment order, the merchant receives the notification at this url
   • The order object updated with the result of the operation is received.