Updates for Febraury, 2024

There have been some updates on Payments object and response messages. Please check the updates below.

Transactions history
Tip amount
Invalid transaction response message
Neighborhood field

Transactions History

We've added a new object to the Payment object response called transactions_history. It is an array of objects that represents the list of the transactions that are part of a payment. The amount of transactions is going to depend on how many providers you have set up in your payment method route.

Tip amount

We've added a new field to the Payment object inside the additional_data.order struct called tip_amount. It represents the tip amount of the order. This field is for informational purposes, the tip amount is already included in the final transaction amount and is not added separately.

curl --request POST \
     --url https://api-sandbox.y.uno/v1/payments \
     --header 'X-Idempotency-Key: <Your idempotency-key>' \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --header 'private-secret-key: <Your private-secret-key>' \
     --header 'public-api-key: <Your public-api-key>' \
     --data '
{
    "description": "Test",
    "account_id": "{{account-code}}",
    "merchant_order_id": "0000023",
    "country": "CO",
    "merchant_reference" : "reference-{{$randomUUID}}",
    "amount": {
        "currency": "COP",
        "value": 5000.00
    },
    "customer_payer": {
        "id":"967ecd18-d898-4b88-9400-dd5b01b18edc"
    },
    "additional_data": {
          "order": {
              "tip_amount": 50.00
          }
      },
    "workflow": "DIRECT",
    "payment_method": {
        "type":"CARD",
        "vaulted_token": "eb8caa17-6407-457b-960e-125d8d7a90c1",
        "detail": {
           "card": {
               "stored_credentials":{
                  "reason":"CARD_ON_FILE",
                  "usage": "USED"
              }
           }
        }
    }
}
'

For more information, please refer to the payment amount details documentation.

Invalid transaction response message

We've added new information to the response_message of the API call when a capture transaction is trying to be made and there is already one in process.

{  
    "code": "INVALID_STATUS",  
    "messages": [  
        "Invalid transaction status. Transaction already in progress"  
    ]  
}

Neighborhood

We've added a new field to the Customer object inside the shipping_addresand billing_address called neighborhood. It represents the neighborhood of the address line of the customer (MAX 255; MIN 3).