Updates for October, 2024

There have been some updates on Yuno. Please check the updates below.

• Subscription retries
• Parent payment method type
• Connection ID
• Receipts for Cancel transactions
• Shipping details

Subscription retries

We've added a new capability to the Subscription feature called Smart Retries. Employ advanced machine learning techniques to identify the optimal timing for retrying a declined recurring credit card payment. By analyzing extensive data points and transaction attributes, it improves the probability of payment success, ensuring a steady flow of revenue and reducing involuntary subscriber churn.

Now Yuno implements a retry scheme for every declined transaction if the merchant wants to forget about that logic.

For more information, please refer to the smart retries documentation in the guides section.

Parent payment method type

We've added a new field to the Payment object called parent_payment_method_type. The field (insidetransactions.payment_method) represents the wallet provider used while creating a payment. When using a wallet for payments through a direct integration, this field indicates the provider from which the card information was obtained. Enum: APPLE_PAY, GOOGLE_PAY or CLICK_TO_PAY.

[...]
    "transactions": {
        "id": "b9f76b64-fd70-413b-b79d-fe33403475de",
        "type": "AUTHORIZE",
        "status": "SUCCEEDED",
        "category": "CARD",
        "amount": 5000.00,
        "provider_id": "YUNO_TEST_PAYMENT_GW",
        "payment_method": {
            "vaulted_token": "29b44e45-57fe-41b0-81c8-586deeb699b2",
            "type": "CARD",
            "vault_on_success": true,
            "token": "",
            "parent_payment_method_type": "CLICK_TO_PAY,
            "detail": {
 [...]

For more information, please refer to the payment object in the API reference section.

Connection ID

We've added a new object to the Payment object called connection_data. The field (inside every transaction) specifies the connection data object, which represents the connection used to process the transaction.. Inside the same object, we've added a new field called id that represents the unique identifier of the payment connection in Yuno

[...]
 "connection_data": {
            "id": "88292fd3-bf5b-4b23-bb95-7186ba4e7f88"
        },
 "created_at": "2024-10-09T11:47:17.596575Z",
 "updated_at": "2024-10-09T11:47:17.722686Z",
[...]

For more information, please refer to the payment object in the API reference section.

Receipts for Cancel Transactions

We've added a new capability to the cancel requests called Receipts. This capability lets you obtain a receipt for every cancel transaction made in Yuno. As Yuno does not actually executes the cancelation to the acquirers, this receipt represents the execution of the cancel request to the provider in order to cancel the previously made authorization.

{
  "description": "Duplicate",
  "reason": "REQUESTED_BY_CUSTOMER",
  "merchant_reference": "AAB01-432245",
  "response_additional_data": 
    	{
          "receipt": true
        }
}

Once the CANCEL is created, you can do a get of the payment to find the receipt created in the "receipt_url" field in the payment.transaction object.

For more information, please refer to the cancel request in the API reference section.

Shipping

We've added a new object to the Payment object called shipping. The field specifies the shipping data object defined bu the merchant in every payment.

[...]
 "shipping": {
            "type": "STANDARD",
            "description":"Test shippment",
            "carrier":"UPS",
            "deliver_at":"2024-09-17T20:43:54.786342Z"
        },
[...]

For more information, please refer to the payment object in the API reference section.