Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.y.uno/llms.txt

Use this file to discover all available pages before exploring further.

Discover the latest Yuno updates, including card type for vaulted tokens, enhanced account funding details, network transaction ID support, and a new smart routing flag. Check out the updates below to learn more. There have been some updates on Yuno. Please check the updates below.
  • Vaulted token with card type
  • Account funding transaction details
  • Network transaction ID
  • Smart routing flag
  • Trial period for subscriptions

​
Vaulted token with Card Type

While using vaulted tokens in Yuno, we’ve added the capability to specify the card type for each payment. For markets such as Brazil, where a user can use the same card for both credit or debit transactions, you can now specify in every payment if the transaction should be CREDIT or DEBIT. For this, you can use the already existing structure of card_details inside the payment methods object in payments. 
[...]
"payment_method": {
        "type": "CARD",
        "vaulted_token":"e2961d37-9898-4bac-8408-cc9f02c11cc2",
         "detail": {
            "card": {
                "card_data": {
                    "type":"DEBIT"
                }
            }
        }
    }
[...]
Please refer to the payments API reference section for more information.

​
Account funding transaction details

We’ve added a new capability to the Payments API, which allows you to specify the sender and beneficiary information necessary for account funding transactions. Account Funding Transactions (AFT) are financial transactions that facilitate funds transfer between payment accounts. They are widely used to load or top up user accounts and digital wallets and perform internal fund transfers within a payment platform. 
[...]
 "additional_data": {
    "account_funding": {
      "sender": {
        "first_name": "John",
        "last_name": "Doe",
        "email": "john.doe@mail.com"
      },
      "beneficiary": {
        "first_name": "Chris",
        "last_name": "Martin",
        "document": {
          "document_number": "38192019",
          "document_type": "CC"
        }
      }
    }
  }
[...]
For more information, please refer to the AFT guides section in the documentation.

​
Network Transaction ID

We’ve added the possibility to send in the Payments API the network_transaction_id recommended for subscription payments with enrolled payment methods. The Network Transaction ID Is a unique identifier assigned to a transaction by the card network. It tracks and references specific transactions, particularly in recurring payment scenarios, ensuring consistency and traceability across the payment lifecycle. 
"payment_method": {
        "type":"CARD",
        "vaulted_token": "eb8caa17-6407-457b-960e-125d8d7a90c1",
        "detail": {
           "card": {
               "stored_credentials":{
                  "reason":"CARD_ON_FILE",
                  "usage": "USED",
                  "network_transaction_id":"583103536844189"
              }
           }
        }
    }
For more information, please refer to the Stored credentials guides section in the documentation.

​
Smart routing flag

We’ve added a new field to the Payment object response called smart_routing. It’s a field inside the routing rules object specifying whether a transaction went through the smart routing feature.
Example
[...], 
"routing_rules": {
        "smart_routing": false,
        "condition": {
            "id": 133892,
            "name": null,
            "description": null
        }
    },
[...]
For more information, please refer to the payments API reference section.

​
Trial period for subscriptions

We’ve added the possibility of defining a trial period for Subscriptions in Yuno. This new feature lets you define a period where your customers can benefit from a reduced amount. Could be partial or total (in case you want to define a free trial for example), you need to determine the value to be reduced from the total amount of each subscription charge and the billing cycles it should apply to. 
[...],
"trial_period": {
        "billing_cycles":"1",
        "amount": {      
            "currency":"COP",
            "value": 2500,
             }
         }
[...]
For more information, please refer to the Subscriptions guides section in the documentation.