EN
Legal

Payment Policy

PAYMENT POLICY

Applicable to the Blogbio Platform

PREAMBLE

This Payment Policy sets out the principles, methods, procedures, and conditions governing payments made by Users in connection with paid service plans or other chargeable services available on the Blogbio platform.

This Policy is intended to ensure transparency in payment activities, protect the lawful rights and interests of Users and Metaconex Ltd (“Metaconex”), and minimize risks arising during transactions.

By using the services, the User acknowledges that they have read, understood, and agreed to comply with this Policy.

1. SCOPE OF APPLICATION

This Policy applies to:

  • Individuals and organizations that register for and use paid services on Blogbio;

  • Payment, renewal, upgrade, downgrade, refund, and other financial transactions arising on the platform;

  • Payment partners, banks, or payment intermediaries involved in processing transactions under agreements with Metaconex.

This Policy shall apply together with:

  • The Terms of Service;

  • The Privacy and Personal Data Protection Policy;

  • The Cookie Policy;

  • The Policy on Receiving and Handling Feedback, Requests, Complaints, and Appeals;

  • Other policies published by Metaconex.

Where there is any inconsistency between these documents, the subject-specific provisions of the relevant policy shall prevail with respect to the corresponding matter.

2. PAYMENT PRINCIPLES

Metaconex has established its payment process based on the principles of transparency, security, and legal compliance.

When using Blogbio’s paid services, Users agree to the following principles:

2.1 Service Prices

Service prices shall be publicly displayed on the Website or payment screen before the User confirms the transaction.

Any additional charges, where applicable, shall be clearly displayed before payment.

Metaconex shall not automatically charge any amount beyond what the User has confirmed, unless otherwise required by law or where the User initiates a new transaction.

2.2 Conditions for Recognizing Payment

A transaction shall only be considered completed when:

  • The payment system confirms that the transaction was successful;

  • The payment amount has been recorded in accordance with the payment partner’s procedures;

  • There are no indications of fraud or violations of applicable payment requirements.

A debit notification issued by the User’s bank does not necessarily mean that the transaction has been completed if the system has not yet received successful confirmation from the payment service provider.

2.3 Service Activation

Paid services shall be activated after:

  • The transaction has been successfully confirmed;

  • The system has completed the reconciliation process;

  • The User has satisfied all conditions applicable to the relevant service plan.

Where additional verification is required, activation may occur only after the verification process has been completed.

2.4 Lawful Payment Methods

Users may only use:

  • Bank accounts;

  • Payment cards;

  • Electronic wallets; or

  • Other payment methods

that they are legally authorized to use or that they have been authorized to use by the lawful owner.

Users are responsible for the legality of the payment method used.

2.5 Transaction Verification

Metaconex reserves the right to require additional verification for transactions showing signs of unusual activity, including but not limited to:

  • High-value transactions;

  • Payments made from multiple devices;

  • Multiple consecutive transactions within a short period;

  • Unusual changes in country or IP address;

  • Indications that a payment card or payment account is being used unlawfully.

Verification may include requests for additional information, OTP authentication, identity verification, or other appropriate measures.

2.6 Transaction Transparency

Metaconex is committed to:

  • Publicly disclosing service prices;

  • Clearly disclosing billing cycles;

  • Clearly disclosing renewal conditions;

  • Clearly disclosing refund conditions, where applicable;

  • Retaining transaction history in the User’s account, subject to system capabilities.

2.7 Legal Compliance

All payment activities on Blogbio must comply with applicable laws and regulations relating to:

  • E-commerce;

  • Electronic payments;

  • Anti-money laundering;

  • Fraud prevention;

  • Tax administration;

  • Personal data protection;

  • Other relevant legal requirements.

3. PAYMENT METHODS

3.1 Supported Payment Methods

Depending on the relevant time, country, service plan, and payment partner, Blogbio may support one or more of the following payment methods:

  • Bank transfers;

  • Domestic ATM cards;

  • Debit cards;

  • Credit cards;

  • Electronic wallets;

  • Online payment gateways;

  • Contract-based payments for enterprise customers;

  • Other lawful payment methods published by Metaconex.

The display of a payment method on the payment page does not mean that such method will always be available in every circumstance.

3.2 Payment Processing Providers

Transactions may be processed through:

  • Banks;

  • Payment intermediary organizations;

  • Payment gateways;

  • Financial partners; or

  • Other entities licensed in accordance with applicable law.

Metaconex does not directly process payment card information where a transaction is carried out through a specialized third-party payment service provider.

3.3 Payment Currency

The applicable payment currency shall be displayed when the User confirms the order.

Where the User makes payment in a currency other than the displayed currency, the applicable exchange rate and any conversion fees shall be determined by the relevant bank or payment method issuer.

Metaconex does not control and shall not be responsible for exchange rates or fees charged by third parties.

3.4 Changing the Payment Method

Users may update or change the payment method for service plans that support this feature.

A change shall only take effect after it has been successfully recorded by the system and shall not affect transactions completed before the change.

4. PURCHASE AND SERVICE ACTIVATION PROCESS

4.1 Purchase Process

To use a paid service plan on Blogbio, the User shall complete the following steps:

Step 1: Log in to the Blogbio account.

Step 2: Select the appropriate service plan, billing cycle, or additional service.

Step 3: Review the order information, including:

  • The name of the service plan;

  • The service term;

  • The benefits included in the plan;

  • The service price;

  • Taxes and fees, where applicable;

  • The commencement date;

  • The expiration date;

  • The renewal conditions.

Step 4: Select a supported payment method.

Step 5: Confirm the order and complete any authentication steps required by the bank or payment service provider.

Step 6: The system receives the transaction result from the payment partner.

Step 7: Once the transaction has been successfully confirmed, the system activates the service and updates the account’s usage rights.

Step 8: The User may review the transaction history, payment status, and service plan term in their Blogbio account.

4.2 Transaction Confirmation

A transaction shall only be recorded as successful when:

  • The payment partner confirms that payment was successful;

  • The Blogbio system records the transaction result;

  • The transaction is not subject to additional verification;

  • No indications of fraud or violations of this Policy are detected.

A debit notification from a bank or electronic wallet shall not, by itself, constitute confirmation that the transaction has been completed.

4.3 Service Activation

Following successful payment, Blogbio shall activate the usage rights corresponding to the purchased service plan.

In certain special circumstances, including:

  • Transactions requiring reconciliation;

  • Suspected fraud;

  • Technical errors affecting the payment partner;

  • System maintenance;

service activation may be delayed until the verification process has been completed.

5. SERVICE RENEWAL

5.1 Automatic Renewal

For service plans that support automatic renewal, Users may enable or disable this feature through their accounts.

By enabling automatic renewal, the User authorizes Blogbio or its payment partner to charge the applicable fee at the beginning of the next billing cycle using the saved payment method or another payment method authorized by the User.

5.2 Renewal Notices

Depending on the type of service plan, Blogbio may send a notice before the renewal date through:

  • Email;

  • Account notifications;

  • Notices on the Website;

  • Other communication channels registered by the User.

Failure to receive a notice due to an incorrect email address, spam filtering, or another cause attributable to the User shall not affect the validity of the renewal where the User has chosen to enable automatic renewal.

5.3 Renewal Process

When the renewal date arrives:

  1. The system submits a payment request to the payment method saved or authorized by the User.

  2. If the payment is successful, the service term shall be extended for the applicable billing cycle.

  3. The system shall update the service term and send a confirmation notice to the User.

  4. If the transaction is unsuccessful, Blogbio may retry the charge one or more times within a reasonable period.

5.4 Cancellation of Automatic Renewal

Users may disable automatic renewal at any time before the system charges the fee for the next billing cycle.

Disabling automatic renewal shall not affect the remaining usage period of a service plan that has already been paid for.

Upon expiry of the service term, the account shall be transferred to an appropriate service plan in accordance with Blogbio’s then-current policies.

6. FAILED PAYMENTS

6.1 Circumstances in Which Payment May Fail

A payment may be unsuccessful in circumstances including but not limited to:

  • Insufficient funds in the account;

  • An expired payment card;

  • An invalid or inactive payment method;

  • Rejection of the transaction by the bank;

  • Failure to complete the required authentication step;

  • Connection errors between relevant systems;

  • Suspected fraud;

  • Payment limits imposed by the bank;

  • Other circumstances beyond the parties’ reasonable control.

6.2 Handling Failed Payments

Where a payment is unsuccessful, Blogbio may:

  • Notify the User of the reason, where it can be identified;

  • Require the User to update the payment method;

  • Allow the User to retry the transaction;

  • Retry the charge for automatically renewing service plans;

  • Suspend service activation until payment has been completed.

6.3 Late Payment

If the User fails to fulfill their payment obligations by the applicable due date, Blogbio may apply one or more of the following measures:

  • Suspend certain service features;

  • Suspend the renewal process;

  • Transfer the account to a free service plan;

  • Restrict access to certain features;

  • Terminate the service plan in accordance with the Terms of Service.

The application of any such measure shall not relieve the User of their obligation to pay valid charges already incurred.

6.4 Responsibility for Interrupted Transactions

Metaconex shall not be responsible for transactions that are rejected, delayed, or subject to additional charges by:

  • Banks;

  • Card issuers;

  • Payment gateways;

  • Electronic wallet providers;

  • Telecommunications providers;

  • Other third parties outside Metaconex’s control.

Where reasonably possible, Blogbio shall cooperate with the relevant parties to support transaction reconciliation, provided that the User supplies complete information and supporting documents.

7. INVOICES AND TRANSACTION DOCUMENTS

7.1 Issuance of Invoices

For transactions that qualify under applicable law, Blogbio shall issue electronic invoices based on the information provided by the User.

Users are responsible for providing complete and accurate information, including:

  • The name of the individual or organization;

  • Tax identification number, where applicable;

  • Address;

  • Email address for receipt of the invoice;

  • Other information required by law.

7.2 Invoice Adjustments

Where an error is identified, the User must submit a request for adjustment within a reasonable period together with the relevant supporting documents.

Invoice adjustments shall be made in accordance with applicable electronic invoicing laws and Metaconex’s internal procedures.

7.3 Transaction Documents

In addition to electronic invoices, Blogbio may provide:

  • Payment receipts;

  • Transaction confirmation emails;

  • Payment history available in the User’s account;

  • Successful payment notifications.

Such documents only confirm the transaction as recorded in the system and shall not replace an electronic invoice where applicable law requires an invoice to be issued.

7.4 Rejection of Adjustment Requests

Metaconex reserves the right to reject an invoice adjustment request where:

  • The request is submitted after the period permitted by law;

  • The information provided by the User is inaccurate;

  • The submitted documents are incomplete;

  • The request is inconsistent with applicable law;

  • The invoice is not eligible for adjustment.

8. SERVICE PLAN UPGRADES, DOWNGRADES, AND CHANGES

8.1 Service Plan Upgrades

Users may upgrade their service plan at any time, provided that the selected plan is supported by Blogbio.

Before payment is confirmed, the system shall display all relevant information, including:

  • The new service plan;

  • The benefits available after the upgrade;

  • The amount payable;

  • The remaining value of the current plan, where applicable;

  • The effective date of the new plan;

  • The service term following the upgrade.

Once the transaction has been successfully confirmed, the new service plan shall be activated in accordance with the information displayed by the system.

8.2 Service Plan Downgrades

Users may switch to a lower-tier service plan where this feature is supported by Blogbio.

Unless otherwise stated, the downgrade shall take effect at the end of the current billing cycle.

Before the downgrade takes effect, the User is responsible for ensuring that their data, number of websites, storage usage, and other resources remain within the limits of the new service plan.

Where the applicable limits are exceeded, Blogbio may:

  • Suspend certain features;

  • Restrict editing capabilities;

  • Require the User to reduce the amount of stored data;

  • Apply other necessary technical measures to ensure that the system operates in accordance with the registered service plan.

8.3 Changes to the Billing Cycle

Users may change their billing cycle, such as from a monthly plan to an annual plan or vice versa, where this feature is supported.

Before the change is confirmed, Blogbio shall display:

  • The total cost;

  • Any price difference, where applicable;

  • The commencement date of the new billing cycle;

  • The next renewal date;

  • The applicable conditions.

Blogbio shall not automatically change the billing cycle without the User’s confirmation.

9. REFUNDS AND TRANSACTION ADJUSTMENTS

9.1 Duplicate Charges

Where a User is charged more than once for the same order, the User may submit a reconciliation request together with:

  • The order ID;

  • The transaction ID;

  • The date and time of payment;

  • The amount paid;

  • A bank statement or other proof of payment.

Following verification, Metaconex may:

  • Refund the duplicate payment; or

  • Credit the amount to the User’s account for use in future transactions,

depending on applicable law and the User’s choice in the relevant circumstances.

9.2 Incorrect Payment Amounts

Where the system charges an amount greater than the amount confirmed by the User, the difference shall be refunded or offset as agreed between the parties.

Where the system records a lower payment amount due to a technical or system error, Blogbio shall notify the User before making any additional charge.

9.3 Payment Completed but Service Not Activated

Where a transaction has been successfully recorded but the service has not been activated, Blogbio shall prioritize:

  • Reviewing the transaction status;

  • Reconciling the transaction with the payment service provider;

  • Activating the service within a reasonable period.

Where Blogbio is unable to provide the service covered by the completed payment, the User may be entitled to a refund in accordance with the Refund Policy or applicable law.

10. TRANSACTION DISPUTES AND RECONCILIATION

10.1 Notification of Errors

Users should notify Blogbio of any transaction-related error as soon as reasonably possible after discovering it.

The notification should include:

  • The transaction ID;

  • Account information;

  • The date and time of the transaction;

  • The amount;

  • A description of the issue;

  • Supporting documents, where available.

10.2 Transaction Reconciliation

Upon receiving a request, Blogbio shall coordinate with:

  • The relevant bank;

  • Payment gateway;

  • Payment intermediary;

  • Other relevant partner

to verify the transaction information.

The processing period shall depend on the procedures of the relevant parties. However, Blogbio shall provide the User with progress updates to the extent reasonably possible.

10.3 Chargebacks

Where a User submits a chargeback request to a bank or card issuer, Blogbio reserves the right to:

  • Suspend the User’s access to the services;

  • Retain transaction data;

  • Provide supporting evidence to the payment institution;

  • Cooperate with the relevant parties in resolving the dispute.

Where it is determined that the User has intentionally initiated a fraudulent chargeback after using the services, Blogbio may apply measures under the Terms of Service, including suspending the account or seeking compensation for losses in accordance with applicable law.

11. FRAUD PREVENTION

To protect Users and the system, Blogbio may implement transaction risk-assessment measures, including but not limited to reviewing:

  • IP addresses;

  • Device information;

  • Login history;

  • Transaction history;

  • Access locations;

  • Payment methods;

  • Data provided by payment partners;

  • Other indicators of unusual activity.

Depending on the circumstances, Blogbio may:

  • Require identity verification;

  • Require verification of the User’s authority to use the payment method;

  • Delay service activation;

  • Reject the transaction;

  • Place a refund on hold during the verification period;

  • Limit the number of transactions;

  • Apply other appropriate technical measures to protect the system.

Where a lawful request is received from a competent government authority, Blogbio may provide relevant information for investigative purposes in accordance with applicable law.

12. PAYMENT INFORMATION SECURITY

Metaconex prioritizes the use of payment service providers that meet appropriate security standards.

Blogbio does not require Users to provide the following information through support channels:

  • Full payment card numbers;

  • CVV or CVC codes;

  • OTP codes;

  • Banking passwords;

  • Internet Banking login credentials.

Payment information shall be stored, processed, and protected in accordance with Blogbio’s Privacy Policy.

Where tokenization or similar technologies are used, payment card data may be replaced with an identifier managed by the payment service provider.

Users are responsible for protecting their accounts, email addresses, telephone numbers, and devices used to make payments.

13. TAXES, FEES, AND RESPONSIBILITIES OF THE PARTIES

13.1 Taxes

Service prices shall be displayed in accordance with the information published at the time of the transaction and may include or exclude taxes, depending on applicable law.

Users are responsible for providing complete information required for invoice issuance where needed.

13.2 Third-Party Fees

Fees charged by:

  • Banks;

  • Card issuers;

  • Electronic wallet providers;

  • Payment gateways;

  • Telecommunications providers;

  • Other financial institutions

under their own terms and policies shall not be the responsibility of Metaconex, unless otherwise agreed.

13.3 Responsibilities of Metaconex

Metaconex is responsible for:

  • Publicly disclosing service prices before payment;

  • Recording transactions in accordance with the applicable procedures;

  • Supporting transaction reconciliation where errors arise;

  • Protecting payment data within its scope of control;

  • Complying with applicable legal obligations.

13.4 Responsibilities of Users

Users are responsible for:

  • Providing accurate payment information;

  • Maintaining a valid payment method;

  • Making payments on time;

  • Protecting payment authentication information;

  • Promptly reporting any unusual transactions;

  • Refraining from using unlawful payment methods.

14. POLICY UPDATES

Metaconex reserves the right to amend, supplement, or update this Payment Policy where necessary in order to:

  • Comply with applicable law;

  • Reflect changes to the business model;

  • Reflect changes to payment partners;

  • Reflect changes to payment methods;

  • Upgrade the system;

  • Enhance security;

  • Address other lawful operational requirements.

The updated version shall be published on the Website and shall take effect from the date specified in the relevant notice.

Where a change creates new obligations for Users, such change shall apply from the next billing cycle or as otherwise required by law.

15. FINAL PROVISIONS

This Policy shall take effect from the date on which it is published by Metaconex on the Website.

If any provision of this Policy is determined to be invalid under applicable law, the remaining provisions shall remain in full force and effect.

This Policy shall be governed by applicable law and shall apply together with the Terms of Service, Privacy Policy, and other Blogbio policies.