Skip to main content
Yuno is a payment orchestration platform: it connects a single integration to many acquirers, wallets and anti-fraud providers, routes each payment to the best one, and consolidates the result in one place. This source brings that consolidated view into your Lakehouse - payments and their individual transactions, payouts, settlement and fee detail per acquirer, reconciliation status, customer communications, and the configuration behind it all (accounts, users, roles, plans, subscriptions, recipients and checkouts).

​
1. Add your Yuno access

1

Collect your API credentials in Yuno

In the Yuno Dashboard, open Developers and stay on the Authentication tab. You need three values:The organization code is required: it identifies your organization on the Reports API that feeds the payments, transactions, payouts, settlement and reconciliation streams.
Test Mode (sandbox) and Live Mode use different keys. Use the pair that matches the environment you select in Nekt, or every request fails with invalid credentials.
If you use a customized API key instead of the organization key, edit it in the same tab and grant it access to the accounts and to the products you want to sync - reports, payments, subscriptions. A key without report access fails with “The merchant has no authorization to use this API”.
2

Check the allowed-IP list

Still in Developers > Authentication, open List of allowed IPs. If that list is not empty, Yuno rejects every request from any other address, so Nekt’s outbound addresses must be added to it. Ask Nekt support for the addresses of your environment. An empty list means no restriction and nothing to do.
3

Add the source in Nekt

In the Sources tab, click Add source, select Yuno from the list of connectors and click Next. You’ll be prompted to add your access:
  • Public API Key: the public key you collected.
  • Private Secret Key: the private key of the same pair.
  • Organization Code: your organization code.
  • Environment: us for US production, eu for EMEA production, sandbox for Test Mode. Defaults to us.
  • Initial sync date (optional): the earliest date to read report data from. Defaults to the last 90 days.
  • Account Code (optional): scopes every request to a single Yuno account. Only organizations with more than one account need it.
  • Account IDs filter (optional): restricts the reports to specific account identifiers, as a comma-separated list. Leave it empty to include every account.
  • Report window (days) (optional): how many days each generated report covers. Defaults to 30. Yuno rejects report ranges longer than two months, so values above 60 are capped.
  • Report lookback (days) (optional): how far before the last synced window each run reads again. Defaults to 0. See the note below.
  • Report columns (optional): documented (default) asks Yuno for every column of its Reports Fields reference; default keeps Yuno’s own smaller selection.
  • Include itemized payment columns (optional): adds the per-order-item and per-airline-leg columns to the payments report. Disabled by default.
Click Next.
How the payment data is read. Yuno has no endpoint that lists payments or transactions - the API only looks up one record at a time by its reference. Bulk data comes from Yuno’s asynchronous Reports API: Nekt queues a report for a date range, waits for Yuno to build it, and downloads the resulting file. Since Yuno accepts at most two months per report, the six report streams walk your history in windows and each row carries the report_window_end of the window that produced it, which is the replication key.Two consequences are worth knowing:
  • Report streams have no primary key. The report file has no guaranteed unique identifier per row - asking for the itemized payment columns, for instance, makes Yuno return one row per order item - so rows are appended rather than merged.
  • Status changes on older records need a full sync or a lookback. A window that was already read is not read again, so a chargeback registered months after the payment does not update the row that was extracted earlier. Schedule an Additional Full Sync to refresh the whole history, or set a Report lookback so the most recent windows are read on every run - at the cost of extracting the rows in the overlap more than once.

​
2. Select your Yuno streams

Choose which streams you want to sync. For faster extractions, select only the streams relevant to your analysis.
Tip: The stream can be found more easily by typing its name.
Each report stream asks Yuno to generate one report per window, and Yuno builds them asynchronously - a long history with a small window means many reports and a long run. Keep the report window at 30 days or more for the initial backfill, and set the initial sync date to the earliest date you actually need.
The plans, subscriptions, recipients and checkouts streams depend on Yuno products that may not be enabled on your account. If one of them is not available for your credentials, Nekt skips it with a warning in the run log instead of failing the extraction, and its table is not updated. Click Next.

​
3. Configure your Yuno data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once.
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE. Read more about Sync Types here.
Click Next.

​
4. Configure your Yuno data source

  1. Describe your data source for easy identification within your organization.
  2. To define your Trigger, consider how often you want data to be extracted from this source.
  3. Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.

​
Check your new source

Click Next to finalize the setup. You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

​
Available streams

The six report streams are replicated incrementally by report window. The eight REST streams are read in full on every run, because Yuno exposes no update filter on them. Fields described as JSON hold a serialized object or array in a text column - query them with your warehouse’s JSON functions.
One row per payment created in Yuno, with the buyer, the amount, the selected payment method and the current status.Replicated incrementally on report_window_end.Key fields:
  • payment_id - A unique identifier assigned to a specific payment transaction.
  • transaction_id - Yuno’s internal transaction identifier associated with the payment.
  • account_id - The unique identifier of the account.
  • merchant_order_id - The identification of the order.
  • status - The status of the payment.
  • sub_status - The substatus of the payment.
  • amount_value - The payment amount (multiple of 0.0001).
  • captured - Indicates the total amount captured for payment.
  • refunded - The payment amount that has been refunded.
  • currency - The currency used to make the payment.
  • country - The country where the transaction must be processed.
  • payment_method_type - Specific payment method used (CARD, APPLE_PAY, PIX, NEQUI, YAPE, MERCADO_PAGO_WALLET, BANK_TRANSFER, GCASH, BOLETO, OXXO, etc.).
  • installments - Number of installments for the payment.
  • customer_id - The unique identifier of the customer.
  • customer_first_name - The customer’s first name.
  • customer_last_name - The customer’s last name.
  • email - The customer’s e-mail.
  • document_number - Document number of the individual.
  • document_type - Type of document (e.g., ID card, passport).
  • card_brand - Brand of the card used in the transaction (e.g., Visa, MasterCard).
  • card_type - Type of card (e.g., credit, debit).
  • card_iin - Issuer Identification Number (IIN) for the card (first 6 digits).
  • card_lfd - Last four digits of the card number.
  • card_holder_name - Name of the cardholder.
  • card_issuer_name - Name of the bank or institution issuing the card.
  • authorization_code - Authorization code returned by the acquirer / issuer when the transaction is approved. May be numeric or alphanumeric. Already documented in Transactions.
  • checkout_session - Unique identifier for the checkout session.
  • subscription_id - A unique identifier assigned to a recurring subscription or billing agreement.
  • connection_name - Merchant-assigned label of the provider connection (account_integration) through which the transaction was routed.
  • provider_number - The ticket’s number.
  • description - The description of the payment.
  • metadata_value - Custom metadata attached to the payment by the merchant at creation time, serialized as a JSON array of key, value objects.
  • ip_address - The customer’s IP address.
  • device_fingerprint - Unique identifier for the device used in the transaction.
  • pnr - Passenger Name Record (PNR) reference.
  • created_at - The payment creation date.
  • updated_at - The date and time of the last update for the payment.
Yuno’s payments report carries more than 130 columns. Beyond the ones above, the connector also brings the payment_seller_details_* columns (the seller behind a marketplace payment), browser_info_* (the device that submitted the checkout), network_token_* (network tokenization detail), payment_tax_* (taxes applied), billing_cycles_* (subscription cycle counters), and, when Include itemized payment columns is enabled, order_item_* and airline_*. The full column list is documented in Yuno’s Reports Fields reference.
Enabling Include itemized payment columns changes the grain of this table: Yuno returns one row per order item or airline leg instead of one row per payment.
Every operation performed against a payment - purchase, refund, chargeback, verification - with the provider that processed it and the raw response it returned. This is the finest grain Yuno exposes and the stream to use when you need provider-level detail.Replicated incrementally on report_window_end.Key fields:
  • transaction_id - Unique identifier for the transaction.
  • payment_id - Unique identifier for the payment.
  • account_id - Unique identifier for the account.
  • type - Type of transaction.
  • status - Status of the transaction.
  • provider_status - Status of the payment at the provider.
  • provider_status_detail - Detailed status from the provider.
  • provider_id - Unique identifier for the provider.
  • provider_transaction_id - Unique transaction identifier from the provider.
  • amount - Amount of the transaction.
  • currency - Currency code for the transaction.
  • country - Country where the transaction occurred.
  • payment_method_category - Category of the payment method (CARD, BANK_TRANSFER, etc.).
  • payment_method_type - Type of payment method (CARD, BANK_TRANSFER, etc.).
  • card_brand - Brand of the card used.
  • card_type - Type of card used (CREDIT or DEBIT).
  • card_iin - Issuer Identification Number (IIN) of the card.
  • card_lfd - Last four digits of the card number.
  • card_issuer_name - Name of the card issuer.
  • card_issuer_country - ISO Alpha-2 country code of the issuing bank, derived from the card IIN.
  • card_expiration_month - Card expiration month.
  • card_expiration_year - Card expiration year.
  • authorization_code - Authorization code for the transaction.
  • response_code - Response code from the system.
  • response_message - Response message from the system.
  • iso_code - ISO 8583 response code returned by the acquirer / network. 00/000 indicate approval.
  • iso_message - Response message associated with the ISO 8583 response.
  • merchant_order_id - Merchant’s order identifier.
  • merchant_transaction_id - Merchant’s transaction identifier.
  • retrieval_reference_number - Reference number for retrieving transaction details.
  • installments - Number of installments for the transaction.
  • installments_amount - Total amount of installments.
  • three_d_secure_version - Version of 3D Secure protocol used.
  • three_d_secure_electronic_commerce_indicator - Electronic commerce indicator for 3D Secure authentication.
  • has_challenge - Indicates if the transaction has a challenge step (3D Secure).
  • fraud_screening_provider_score - Fraud screening score provided by the fraud detection system.
  • provider_raw_response - Raw response body returned by the provider API. Wrapped as “value”:"".
  • provider_raw_notification - Raw webhook notification payload received from the provider. Wrapped as “value”:"".
  • subscription_id - Unique identifier for a subscription associated with the transaction.
  • customer_id - Unique identifier for the customer.
  • email - Email address of the customer.
  • created_at - Timestamp when the transaction was created (ISO 8601).
  • updated_at - Timestamp when the transaction was last updated (ISO 8601).
The report carries more than 110 columns in total, including the remaining three_d_secure_* fields, bank_transfer_* payment instructions, stored_credentials_*, wallet_*, ticket_provider_* and payment_link_* groups. The full column list is documented in Yuno’s Reports Fields reference.
Money sent from your Yuno balance to a beneficiary, with the beneficiary’s identification and the withdrawal method used.Replicated incrementally on report_window_end.Fields:
  • beneficiary_national_entity - National entity or organization of the beneficiary.
  • payout_id - Unique identifier for the payout.
  • beneficiary_legal_name - Legal name of the beneficiary.
  • account_id - Unique identifier for the account.
  • status - Status of the payout.
  • merchant_reference - Reference number assigned by the merchant.
  • description - Description of the payout.
  • purpose - Purpose of the payout transaction.
  • country - Country where the payout is processed.
  • amount_value - The payout amount (multiple of 0.0001).
  • currency - The currency used for the payout.
  • merchant_beneficiary_id - Beneficiary identifier assigned by the merchant.
  • provider_id - Unique identifier for the provider.
  • created_at - Timestamp when the payout was created (ISO 8601).
  • updated_at - Timestamp when the payout was last updated (ISO 8601).
  • beneficiary_first_name - First name of the beneficiary.
  • beneficiary_last_name - Last name of the beneficiary.
  • beneficiary_email - Email address of the beneficiary.
  • beneficiary_country - Country of residence of the beneficiary.
  • beneficiary_date_of_birth - Date of birth of the beneficiary.
  • beneficiary_document_number - Document number of the beneficiary.
  • beneficiary_document_type - Type of document for the beneficiary.
  • beneficiary_phone_country_code - Country code for the beneficiary’s phone number.
  • beneficiary_phone_number - Phone number of the beneficiary.
  • beneficiary_address_line_1 - First line of the beneficiary’s address.
  • beneficiary_address_line_2 - Second line of the beneficiary’s address.
  • beneficiary_city - City of the beneficiary’s address.
  • beneficiary_state - State or province of the beneficiary’s address.
  • beneficiary_zip_code - Postal code of the beneficiary’s address.
  • withdrawal_method_branch - Bank branch for the withdrawal method.
  • withdrawal_method_branch_digit - Branch digit for the withdrawal method.
  • withdrawal_method_account_number - Account number for the withdrawal method.
  • withdrawal_method_account_digit - Account digit for the withdrawal method.
  • withdrawal_method_account_type - Type of account for the withdrawal method.
  • withdrawal_method_address_line_1 - First line of the withdrawal method address.
  • withdrawal_method_address_line_2 - Second line of the withdrawal method address.
  • withdrawal_method_address_city - City of the withdrawal method address.
  • withdrawal_method_state - State of the withdrawal method address.
  • withdrawal_method_zip_code - Postal code of the withdrawal method address.
  • withdrawal_method_email - Email address for the withdrawal method.
  • withdrawal_method_document_number - Document number for the withdrawal method.
  • withdrawal_method_document_type - Type of document for the withdrawal method.
  • withdrawal_method_phone_country_code - Country code for the withdrawal method phone number.
  • withdrawal_method_phone_number - Phone number for the withdrawal method.
  • withdrawal_method_type - Type of withdrawal method.
  • withdrawal_method_code - Code for the withdrawal method.
  • withdrawal_method_country - Country for the withdrawal method.
What each acquirer actually settled for each transaction: gross and net amounts in both the original and the settlement currency, the fees and taxes withheld, and the settlement batch you can match against your bank statement.Replicated incrementally on report_window_end.Fields:
  • transaction_id - The unique identifier of the transaction assigned by Yuno.
  • payment_id - The unique identifier of the payment. A payment may group several transactions (e.g. PURCHASE plus REFUND).
  • reconciliation_id - The unique identifier assigned to a transaction when it is reconciled.
  • settlement_batch_id - Unique acquirer settlement batch number that you can find on your bank statement for the corresponding deposit.
  • account_id - The merchant account ID.
  • organization_code - Unique identifier of the organization associated with the transaction.
  • customer_id - The unique identifier of the customer.
  • merchant_order_id - Identification of the order assigned by the merchant.
  • merchant_transaction_id - Identification of the transaction assigned by the merchant.
  • provider_merchant_id - Merchant ID in the PSP system.
  • transaction_date - Transaction creation date.
  • settlement_date - Date the funds were settled to the merchant account.
  • reconciliation_date - The date the transaction was reconciled.
  • estimated_settlement_date - Date on which the funds are expected to be deposited to the merchant.
  • acquirer - Name of the acquirer that processed the original payment. In aggregator models the provider is the same as the acquirer. In other models they may be different entities.
  • provider_id - Identifier of the provider / gateway that processed the transaction.
  • provider_transaction_id - The unique identifier of the transaction assigned by the gateway. This field is empty if the gateway does not provide transaction information.
  • authorization_code - In case of a card transaction, the code assigned by the issuing bank to the transaction when it is authorized. Empty if the gateway does not provide it.
  • type - The transaction type. Possible values: PURCHASE, REFUND, CHARGEBACK.
  • currency - Currency code in which the original transaction was made.
  • settlement_currency - Currency code in which the settlement was made.
  • gross_credit - For credit transactions, the corresponding gross amount in the original currency (multiple of 0.0001).
  • gross_debit - For debit transactions (refunds, chargebacks), the corresponding gross amount in the original currency (multiple of 0.0001).
  • settlement_gross_amount - The corresponding gross amount for all transactions in settlement currency (multiple of 0.0001).
  • settlement_net_credit - The amount submitted in the credit transaction requests minus acquirer fees in settlement currency (multiple of 0.0001).
  • settlement_net_debit - The amount submitted in the debit transaction requests minus acquirer fees in settlement currency (multiple of 0.0001).
  • fx_rate - The exchange rate applied to the transaction at the time of settlement (multiple of 0.0001).
  • local_amount - Transaction amount expressed in the local currency of the merchant (multiple of 0.0001).
  • net_amount - Net amount in the original currency after fees and taxes (multiple of 0.0001).
  • settlement_fees - The commission fee that was withheld by the acquirer on transactions in settlement currency. This should be the difference between the gross and net amounts (multiple of 0.0001).
  • provider_fees - Fees retained by the provider in the original currency (multiple of 0.0001).
  • settlement_taxes - The value of taxes applied to the transactions in settlement currency. This should be the difference between the gross and net amounts (multiple of 0.0001).
  • local_tax - Local taxes applied to the transaction in local currency (multiple of 0.0001).
  • local_retention - Local tax retention applied to the transaction in local currency (multiple of 0.0001).
  • provider_fee_taxes - Taxes on provider-level fees in the original currency (multiple of 0.0001).
  • reconciliation_status - The reconciliation status of a transaction. Possible values: RECONCILED, NOT_RECONCILED, CONFLICT, NON_RECONCILABLE.
  • reconciliation_sub_status - The reconciliation substatus of a transaction. Possible values: AUTOMATICALLY, MANUAL, PENDING.
  • payment_method_category - Category of the transaction (e.g. CARD, WALLET, BANK_TRANSFER).
  • payment_method_type - The type of payment method selected by the customer (e.g. VI, MD, PIX, BOLETO).
  • card_brand - Brand of the card used in the transaction (e.g. VISA, MASTERCARD, AMEX).
  • card_type - Type of card used in the transaction. Possible values: CREDIT, DEBIT.
  • card_iin - The issuer identification number (IIN), i.e. the first digits of the payment card. Stored as string to preserve leading zeros.
  • card_lfd - Last four digits of the payment card.
  • installments - In case of a card transaction, the number of installments in which the payment was requested.
  • country - Country of the merchant account.
Reconciliation status of each transaction against the provider’s settlement file, with the amounts, fees and taxes Yuno matched.Replicated incrementally on report_window_end.Fields:
  • transaction_id - The unique identifier of the transaction assigned by Yuno.
  • payment_id - The unique identifier of the payment.
  • reconciliation_id - The unique identifier assigned to a transaction when it is reconciled.
  • account_id - The unique identifier of the account.
  • customer_id - The unique identifier of the customer.
  • merchant_order_id - Identification of the order assigned by your company.
  • merchant_transaction_id - Identification of the transaction assigned by your company.
  • created_at - Transaction creation date.
  • updated_at - The date and time from the last time the transaction was updated (ISO 8601).
  • reconciliation_date - The date the transaction was reconciled.
  • reconciliation_settlement_date - Date by the acquirer on which the funds will be deposited in the merchant’s bank account.
  • estimated_settlement_date - Date on which the funds are expected to be deposited to the merchant.
  • provider_id - The ID of the provider that processed the transaction.
  • provider_status - The transaction status from the provider.
  • provider_transaction_id - The unique identifier of the transaction from the provider.
  • retrieval_reference_number - Unique reference number for transaction retrieval.
  • response_code - The code that represents the response to the outcome of the transaction.
  • authorization_code - The acquirer’s response code.
  • amount - The amount of the transaction in the original currency.
  • currency - The currency used to make the payment.
  • country - The country where the transaction must be processed.
  • local_amount - Transaction amount expressed in the local currency of the merchant (multiple of 0.0001).
  • net_amount - Net amount after fees and taxes in the original currency (multiple of 0.0001).
  • settlement_gross_amount - Gross transaction amount in the settlement currency (multiple of 0.0001).
  • settlement_fees - Total commission fee withheld by the acquirer in the settlement currency (multiple of 0.0001).
  • settlement_net_credit - Credit amount minus fees in the settlement currency (multiple of 0.0001).
  • local_retention - Local tax retention applied to the transaction (multiple of 0.0001).
  • local_tax - Local taxes applied to the transaction (multiple of 0.0001).
  • provider_fee_taxes - Taxes on provider-level fees in the original currency (multiple of 0.0001).
  • provider_fees - Fees retained by the provider in the original currency (multiple of 0.0001).
  • status - The status of the transaction.
  • type - The transaction type. Possible values: PURCHASE, REFUND, CHARGEBACK.
  • reconciliation_status - The reconciliation status of a transaction. Possible values: RECONCILED, NOT_RECONCILED, CONFLICT, NON_RECONCILABLE.
  • reconciliation_sub_status - The reconciliation substatus of a transaction. Possible values: AUTOMATICALLY, MANUAL, PENDING.
  • payment_method_category - Category of the transaction (e.g. CARD, WALLET, BANK_TRANSFER).
  • payment_method_type - The type of payment method selected by the customer.
  • card_brand - The card’s brand information standardized by Yuno.
  • provider_card_brand - The payment method or card brand as reported by the provider.
  • card_category - Category of the card used in the transaction.
  • card_type - The type of the card’s issuer. Possible values: CREDIT, DEBIT.
  • card_iin - The issuer identification number (IIN) of the payment card. Stored as string to preserve leading zeros.
  • card_lfd - Last four digits of the card.
  • card_issuer_country - Country of the card issuer.
  • card_issuer_name - Bank to which the card corresponds.
  • card_expiration_month - Card expiration month.
  • card_expiration_year - Card expiration year.
  • installments - In case of a card transaction, the number of installments in which the payment was requested.
  • description - Free-text description of the transaction provided by the merchant.
  • pnr - The passenger name record.
Calls and messages Yuno campaigns sent to customers - for example to recover a declined payment - with the transcription, the summary and the reason the payment failed.Replicated incrementally on report_window_end.Fields:
  • communication_id - Unique identifier for the communication.
  • order_id - Identifier of the order associated with the communication.
  • payment_id - Identifier of the payment associated with the communication.
  • communication_status - Current status of the communication.
  • destination_phone - Phone number where the communication was sent.
  • created_at - Date and time when the communication was initiated (ISO 8601).
  • country - Country code where the communication was sent (ISO 3166-1 alpha-2; MAX 2; MIN 2).
  • transcription - Text transcription of the communication content.
  • call_duration - Duration of the call in seconds.
  • messages - Array of messages exchanged during the communication.
  • summary - Summary of the communication content.
  • channel - Communication channel used (e.g., VOICE, SMS, WHATSAPP; MAX 50; MIN 3).
  • focus - Main topic or focus of the communication.
Accounts of your Yuno organization. Their identifiers are what the Account IDs filter setting expects.Read in full on every run.Fields:
  • id - Unique identifier of the account.
  • name - Display name of the account.
  • created_at - When the account was created.
  • updated_at - When the account was last updated.
Groups used to organize accounts, in organizations that run whitelabel partnerships.Read in full on every run.Fields:
  • id - Unique identifier of the account group.
  • name - Display name of the account group.
  • merchant_id - Identifier of the merchant that owns the account group.
  • created_at - When the account group was created.
  • updated_at - When the account group was last updated.
Dashboard users of the organization and the roles granted to them on each account and account group.Read in full on every run.Fields:
  • id - Unique identifier of the user.
  • email - Email address the user signs in with.
  • first_name - First name of the user.
  • last_name - Last name of the user.
  • account_permissions - Roles the user holds on individual accounts, as a JSON array of objects with account_id and role_id.
  • account_group_permissions - Roles the user holds on account groups, as a JSON array of objects with account_group_id and role_id.
  • created_at - When the user was created.
  • updated_at - When the user was last updated.
Roles available in the organization and the permissions each one grants. Join permission_ids against Yuno’s permissions catalog to read them by name.Read in full on every run.Fields:
  • id - Unique identifier of the role.
  • name - Display name of the role.
  • description - Description of the role.
  • admin - Whether the role grants full administrative access.
  • permission_ids - Identifiers of the permissions granted in Live Mode.
  • testing_permission_ids - Identifiers of the permissions granted in Test Mode.
  • role_type - Scope of the role: account or organization.
  • created_at - When the role was created.
  • updated_at - When the role was last updated.
Subscription plans configured in the account, with the recurring amount and the billing frequency.Read in full on every run. Skipped with a warning when the Subscriptions product is not enabled.Fields:
  • id - Unique identifier of the plan.
  • account_id - Identifier of the account that owns the plan.
  • name - Display name of the plan.
  • merchant_reference - Identifier of the plan on your side.
  • status - Current status of the plan, for example ACTIVE.
  • base_amount_currency - Currency of the plan’s base amount (ISO 4217).
  • base_amount_value - Base amount charged on every billing cycle.
  • frequency_type - Unit of the billing frequency, for example MONTH.
  • frequency_value - Number of frequency units between two billing cycles.
  • subscribers_count - Number of subscriptions currently linked to the plan.
  • countries - Countries where the plan is available (ISO 3166-1 alpha-2).
  • created_at - When the plan was created.
Recurring subscriptions of the account, with the customer being charged, the amount and the next billing date.Read in full on every run. Skipped with a warning when the Subscriptions product is not enabled, or when a multi-account organization has no Account Code configured.Fields:
  • id - Unique identifier of the subscription.
  • name - Display name of the subscription.
  • status - Current status of the subscription, for example ACTIVE or PAUSED.
  • merchant_reference - Identifier of the subscription on your side.
  • account_id - Identifier of the account that owns the subscription.
  • customer_payer_id - Unique identifier of the customer being charged.
  • amount_currency - Currency charged on every billing cycle (ISO 4217).
  • amount_value - Amount charged on every billing cycle.
  • frequency_type - Unit of the billing frequency, for example MONTH. Empty on subscriptions billed on a fixed billing date.
  • frequency_value - Number of frequency units between two billing cycles.
  • billing_cycles_total - Total number of cycles the subscription will be charged for.
  • billing_cycles_current - Next billing cycle to be charged, not the one in progress.
  • billing_cycles_next_at - When the next charge is scheduled.
  • payment_method_type - Payment method used to charge the subscription, for example CARD.
  • plan_id - Plan the subscription is linked to. Empty for subscriptions created with a raw amount and frequency.
  • created_at - When the subscription was created.
Payout recipients (beneficiaries) registered in the account, with their identification, bank details and onboarding status with each payout provider.Read in full on every run. Skipped with a warning when the payouts product is not enabled.Fields:
  • id - Unique identifier of the recipient.
  • account_id - Identifier of the account the recipient belongs to.
  • merchant_recipient_id - Identifier of the recipient on your side.
  • national_entity - Whether the recipient is an INDIVIDUAL or an ENTITY.
  • entity_type - Type of organization of the recipient.
  • first_name - First name of the recipient.
  • last_name - Last name of the recipient.
  • legal_name - Legal name of the recipient.
  • email - Email address of the recipient.
  • date_of_birth - Date of birth of the recipient.
  • country - Country of the recipient (ISO 3166-1 alpha-2).
  • website - Website URL of the recipient.
  • industry - Industry of the recipient.
  • merchant_category_code - Merchant category code (MCC) of the recipient.
  • document - Identification document of the recipient (JSON object).
  • phone - Phone number of the recipient (JSON object).
  • address - Address of the recipient (JSON object).
  • legal_representatives - Legal representatives of the recipient (JSON array of objects).
  • withdrawal_methods - Bank accounts the recipient is paid to (JSON object).
  • documentation - Documents attached to the recipient (JSON array of objects).
  • onboardings - Onboarding processes of the recipient with each payout provider (JSON array of objects).
  • created_at - When the recipient was created.
  • updated_at - When the recipient was last updated.
Checkout configurations of the account, as built in the Yuno Checkout Builder.Read in full on every run.Fields:
  • id - Unique identifier of the checkout.
  • name - Display name of the checkout.
  • description - Description of the checkout.
  • status - Checkout status: PUBLISHED, NOT_PUBLISHED or ARCHIVED.
  • is_default - Whether this checkout is the account’s default.
  • created_at - When the checkout was created.
  • updated_at - When the checkout was last updated.

​
Troubleshooting

“Yuno rejected the API credentials” - the public and private keys must come from the same pair and from the environment selected in the source. Test Mode keys do not work against production. “the request came from an IP address that is not on your allowed-IP list” - the allowed-IP list in Developers > Authentication is not empty and does not include Nekt’s outbound addresses. Ask Nekt support for the addresses of your environment, or clear the list. “Your Yuno credentials do not have permission to use this API” - a customized API key is being used without access to the reports or to the accounts being read. Grant it in Developers > Authentication. A run takes a long time on the first extraction - each report window is generated asynchronously by Yuno, so a long history means many reports. This is expected on the backfill; later runs only read the windows since the last one. A payment’s status looks out of date - report windows already read are not read again. Schedule an Additional Full Sync, or set a Report lookback so recent windows are refreshed on every run.