Raims Platform Terms of Use

Who we are and when these Terms apply

Raims is a financial infrastructure technology platform for companies of different sizes, built to operate with security, scale, and advanced technology, with resources for customer registration and management, charge creation and monitoring, financial tracking, account settings, and operational support.

These Terms apply to business account creation and use of Raims public sites, platform environment, APIs, support channels, communications, and other official surfaces. By creating an account, completing registration with a password or identity provider, or continuing to use the platform after having access to these Terms, the business customer and its representative acknowledge and agree to them. Contracts, commercial proposals, policies, addenda, data processing documents, and applicable operational or financial partner rules may supplement these Terms.

When a business customer uses Raims to issue charges for products or services that it directly sells or provides to its end customers and payers, that business remains responsible for its commercial relationship, the legality of its offer, the accuracy of submitted information, and the legal bases required to use the platform.

Business use of the platform

Raims is intended for business and professional use. Each business customer is identified and subject to the applicable onboarding, compliance, KYB/KYC, and risk-management procedures. The platform was not designed for direct registration of end consumers as Raims customers without a relationship to a contracting business.

Certain resources may depend on registration review, homologation, commercial approval, technical configuration, operational integration, financial or operational partner validation, or another requirement needed for the operation.

• Access must be used only by companies, representatives, employees, service providers, or authorized users.
• The business customer is responsible for managing permissions, revoking improper access, and ensuring that users act within their roles.
• End customers and payers may interact with charges, payment channels, or receipts, but they do not become administrative users of the business customer's Raims account.

Registration, onboarding, and accuracy of information

To create or operate an account, Raims may request business data, representatives, responsible persons, contacts, address, corporate documents, tax information, website, industry, products, expected volume, and data required for support, compliance, security, and financial operations.

Registration may include company KYB, legal representative KYC, Politically Exposed Person declaration, supporting documents, industry review, risk assessment, commercial evidence, and additional validations required by Raims, financial partners, or applicable law.

• The business customer must provide truthful, complete, updated information compatible with its operation.
• Raims may request documents, receipts, contracts, licenses, proof of delivery, commercial justification, or other evidence when necessary.
• Relevant changes in activity, ownership, representative, bank account, transaction volume, website, offer, or risk must be communicated and updated in the platform when applicable.

Account, authorized users, and access security

The business customer is responsible for protecting credentials, devices, emails, authentication factors, authorized integrations, permissions, and sessions of its authorized users.

Raims may require additional confirmation for sensitive actions, including changes to account data, security, integrations, registration data, bank information, KYC/KYB, or critical operational decisions.

Raims adopts recognized information security practices, including strong authentication, session controls, permission segregation, access monitoring, audit records, protection of data in transit, and encryption controls at rest where applicable.

• Passwords, tokens, passkeys, MFA, verification codes, and technical credentials must be kept confidential and used only by authorized people.
• When a session, device, location, access behavior, or operation shows signs of risk, Raims may request additional validation, such as a two-factor authentication token, passkey, verification code, or renewed identity confirmation.
• Access profiles must follow least privilege, with segregation between viewing, editing, administration, compliance, disputes, and financial operations.
• Activity records, session events, sensitive changes, and security logs may be used for audit, fraud prevention, support, and defense of rights.

Charges, payments, and financial operations

The platform allows business customers to create, monitor, and manage charges arising from their own commercial operations, payment links, payment status, statements, authorized integrations, and, when enabled, other financial features made available by Raims or applicable partners.

Payment execution, settlement, availability of funds, reconciliation, disputes, chargebacks, refunds, reserves, holds, or release of funds may depend on financial partners, authorized institutions, contractual rules, risk policies, and legal obligations.

• The business customer is responsible for the legitimacy of each charge, delivery of the product or service, the relationship with its buyer, and commercial resolution with the payer.
• Settlement timelines and conditions may vary by payment method, account status, risk, reconciliation, operational review, and applicable financial partner rules.
• The business customer will have 30 (thirty) calendar days from the applicable transaction, entry, settlement, or statement date to report any discrepancy, error, or dispute involving fees, applied rates, settled amounts, or financial entries. After that period, the amounts will be considered accepted and confirmed, except for corrections required by law, an authority order, a regulated financial partner, or an operational error acknowledged by Raims.
• Resources that are not yet homologated, incomplete, unavailable, dependent on integration, or subject to approval may be limited, hidden, or released gradually.

Negative balance and repayment obligations

The business customer's account may show a negative balance when chargebacks, lost or accepted disputes, reversals, refunds, returns, fees, reconciliation adjustments, improper credits, or other debits connected with its operations exceed the available amounts. A negative balance will not transfer to the business customer amounts arising exclusively from a proven fault of Raims or a partner under Raims's direct responsibility.

By accepting these Terms, the business customer acknowledges its obligation to repay every liquid, documented, and enforceable negative balance for which it is responsible. Raims will make available a statement or notice identifying the amount, source of the entries, available calculation details, due date, payment method, and dispute channel.

The negative balance must be paid in full within 30 (thirty) calendar days from the notice being made available in the dashboard or sent to the registered email address or another official account channel, whichever occurs first. The business customer must keep its contact details current and monitor account communications.

• The business customer may submit a specific, substantiated dispute within the payment period. A dispute does not suspend payment of the undisputed portion. While a good-faith dispute has not yet undergone Raims's initial review, the genuinely disputed portion will not be submitted for protest or reported to a credit bureau.
• If payment is not made when due, the business customer will be in default and the debt may be subject to monetary adjustment, default interest, legal fees, and reasonable collection expenses permitted by law, the applicable contract, or a specific instrument entered into by the parties.
• When permitted by law, contract, and the applicable operational structure, Raims may set off the negative balance against the business customer's own credits under Raims's contractual control. Any measure involving a payment account, regulated funds, reserve, hold, or settlement will depend on the rules, decisions, and procedures of the partner financial institution or payment institution, the competent authority, and the applicable contracts.
• After verifying the source, amount, due date, and responsible business, and following the applicable notices and procedures, Raims may pursue out-of-court or judicial collection, submit a debt instrument or document for protest, and request the registration of the business's Brazilian corporate taxpayer number in a credit bureau. These measures may only cover a correct, due, and enforceable debt and must be cancelled or updated after payment, an acknowledged correction, or a valid order.
• For material balances, Raims may require the legal representative to electronically sign a debt acknowledgment, payment agreement, or equivalent instrument identifying the amount, source, and due date. The absence of this additional instrument does not extinguish an obligation already constituted, but it may prevent continued use of the platform or proprietary features, subject to applicable contracts and regulated partner rules.
• The obligation to repay a negative balance and the rights to collect, set off, and preserve evidence survive suspension, account termination, and the end of the commercial relationship.

APIs, own operations, and use limits

Raims APIs are made available exclusively to approved business customers so they can integrate payment features into their own systems and use them in their own commercial operations, according to the permissions, limits, and resources enabled by Raims and applicable partners.

API access is only a technological means of using authorized features. It does not grant the business customer autonomy to operate payment accounts, hold third-party funds, or offer the underlying financial infrastructure as its own service.

• The Raims account must not be used to receive, hold, pool, or move funds owned by third parties or received for the benefit of third parties, including consumers, merchants, sellers, service providers, or commercial partners.
• The business customer may not open, offer, or make available payment accounts, subaccounts, wallets, individualized balances, or equivalent features to its customers, partners, or users.
• Marketplaces and platforms may not pool sales proceeds from merchants or service providers in their own Raims account for later payout, or use the account as a pooled or pass-through account.
• Reselling, sublicensing, assigning, white-labeling, or presenting Raims features as the business customer's own financial service is prohibited.

Business customer obligations

The business customer must ensure it has the legal basis, authorization, contract, policy, license, notice to data subjects, or other grounds required to insert, import, query, charge, communicate, or process its end customer data through Raims.

The business customer must use the platform lawfully, transparently, proportionally, and consistently with these Terms, applicable law, Raims policies, and financial partner rules.

• Make its own sales or service terms, cancellation and refund policy, support channels, and privacy notice clearly available to end customers before purchase or payment, in accordance with applicable law.
• For a Public API integration or transparent checkout, the business must display this notice in its own front end near the final payment command, discreetly, legibly, and visibly to the end customer: ‘Payment processed by Raims. By completing the payment, you agree to the Consumer Terms of Service and acknowledge the Privacy Policy’. In this sentence, ‘Consumer Terms of Service’ must be a functional href to https://raims.com/en/consumer-terms. The textual notice is sufficient: no checkbox or separate confirmation is required, and the payer does not need to open the link. Completing the payment formalizes acceptance.
• Clearly identify the business customer as the supplier of the product or service and never present Raims as the seller, provider of the purchased item, or party responsible for the business customer's commercial obligations.
• Inform its own end customers and payers about charges, data processing, support channels, delivery, cancellation, refund, and dispute processes.
• Keep sufficient evidence of sale, delivery, service provision, payer authorization, commercial communication, and customer support.
• Cooperate with compliance, fraud, security, dispute, chargeback, audit, support, reconciliation, and investigation requests when necessary.

Prohibited use and restricted activities

Raims may not be used for illegal, fraudulent, deceptive, or restricted activities, or any activity incompatible with laws, sanctions, payment method rules, third-party rights, platform security, or the risk appetite defined by Raims and its partners.

• Perform, facilitate, or conceal money laundering, terrorism financing, fraud, corruption, control evasion, scams, pyramid schemes, illegal sales, or operations without required authorization.
• Create false charges, manipulate receipts, misuse identity, cause chargebacks, simulate transactions, bypass limits, exploit failures, or abuse features, integrations, or payment channels.
• Act on behalf of people, countries, entities, products, segments, or operations subject to applicable sanctions, legal restrictions, blocks, or prohibitions.
• Attempt unauthorized access, compromise availability, improperly collect data, copy the platform, perform unauthorized reverse engineering, or interfere with service operation.

Compliance and risk policies

Raims maintains internal, contractual, and operational compliance, fraud prevention, AML/CFT, and risk-based monitoring controls described in a dedicated policy. These controls do not characterize Raims as a bank, financial institution, or payment institution authorized by the Central Bank of Brazil and may affect registration, platform use, limits, operational review, preventive holds, or communications with regulated partners and authorities when applicable.

Raims' risk approach considers operational context, transaction history, commercial evidence, technical signals, payer behavior, and requirements from regulated partners instead of relying only on isolated rules such as balance, revenue, or account age.

Automated signals, analytical models, and artificial intelligence technologies may support triage, review prioritization, and platform protection, while Raims seeks to reduce false positives and avoid unnecessary blocks that harm legitimate businesses.

• Company, representative, PEP, document, segment, activity, website, history, and registration consistency data may be reviewed using a risk-based approach.
• Relevant variations in volume, transaction behavior, recurrence, chargebacks, disputes, refunds, balance, and operational signals may trigger internal alerts.
• Atypical or higher-risk cases may be manually reviewed by operations, compliance, security, or authorized teams.
• When a relevant restrictive measure is necessary, Raims may consider proportionality, review by authorized teams, documented decision-making, and preservation of support channels where applicable.

Security measures, review, blocking, or suspension

Ordinary suspensions or terminations of Platform access or proprietary features, when they do not involve urgency, will be communicated with at least 1 month of prior notice. When there is suspected risk, fraud, contractual or policy breach, misuse, legal obligation, authority order, partner requirement, or need to protect the payment ecosystem, Raims may adopt immediate, proportionate, and documented technical measures over access, features, integrations, charges, and operational flow. Blocks, holds, refunds, returns, or termination related to payment accounts and regulated funds will follow the rules, decisions, procedures, or requirements of the BaaS/IP partner, authorities, or applicable contracts.

• Request additional information, documents, receipts, justifications, proof of delivery, registration review, or access revalidation.
• Apply operational limits, enhanced limits for new accounts, feature restrictions, withdrawal review, operational reserve or hold labels in the dashboard, interface command suspension, or escalation to the BaaS/IP partner, without characterizing a unilateral Raims decision over funds maintained by the regulated partner.
• When there are substantiated indications of illicit practices, anomalous transactional behavior, or critical volume of disputes opened by final payers, Raims may apply platform technical controls, restrict sensitive features, and escalate the case to the BaaS/IP partner for assessment of limits, blocks, holds, returns, refunds, or reserves over regulated funds. When a balance hold or restriction arises from partner procedure, applicable rule, authority order, contract, or rights defense, the operational window may observe up to 180 (one hundred eighty) days to cover disputes, refunds, reimbursements, contingencies, or losses generated by the business customer. If bad faith, intent, manifest fraud, or intentional breach of these Terms is proven, the business customer will be responsible for reimbursing direct losses proven to have been caused to Raims, including judgments, fines, and related costs.
• Suspend, refuse, terminate, or limit Platform access, charge, integration, user, proprietary operation, or technical feature with 1 month of prior notice when applicable, or without prior notice in cases of fraud, risk, policy breach, legal obligation, or platform protection. Termination of a payment account or restriction over regulated funds will follow the rule, decision, or procedure of the BaaS/IP partner, competent authority, or applicable contract.
• Notify, escalate, or execute operational procedures approved by financial partners, institutions, authorities, auditors, or other operationally responsible parties when applicable.

Personal data and privacy

Use of Raims involves personal data processing related to authorized users, representatives, invited employees, end customers, payers, visitors, leads, suppliers, partners, and people receiving support, as described in Raims Privacy Policy.

The business customer must observe the LGPD and other applicable rules, inform its own data subjects when acting as controller, and ensure Raims receives data only when there is a legitimate purpose, legal basis, and operational need.

Intellectual property

Raims, its brands, systems, screens, flows, materials, design, integrations, texts, images, code, databases, processes, and other assets remain protected by intellectual and industrial property rights.

Names, trademarks, logos, icons, images, distinctive signs, names of financial institutions, banks, card networks, partners, providers, or other third parties that may appear in the platform belong to their respective owners. Raims uses them only when necessary for identification, informational reference, operational compatibility, routing, institution selection, integration, or user experience facilitation, without any transfer of ownership, broad license, corporate association, sponsorship, endorsement, or presumed commercial authorization.

Suggestions, comments, ideas, or feedback sent to Raims may be used to improve products without any obligation of compensation, exclusivity, or incorporation.

Availability, changes, and liability limitations

Raims was built for high availability, security, performance, and continuity, with an architecture designed for scaled operations and a best-efforts operational target when applicable to the contracted service, without constituting a guarantee of uninterrupted availability. Maintenance, partial degradation, delays, or unavailability may occur, especially when caused by providers, partner financial institutions, official settlement rails, payment methods, external infrastructure, networks, regulatory changes, or operational and financial partners.

The business customer remains responsible for its offer, legal compliance, product delivery, service performance, support, cancellations, and refunds owed to payers. If a complaint, claim, proceeding, loss, or reasonable expense demonstrably arises from the business customer's act or omission, including misleading information, delivery failure, consumer-law breach, or omission of the required transparent-checkout notice, the business customer must cooperate in Raims' defense and reimburse proven direct losses after notice and a reasonable opportunity to participate in the defense. This obligation does not apply to the extent the harm arises from Raims' own proven failure or a partner under Raims' direct responsibility, and it does not authorize settlement or admission of liability on behalf of the business customer without its consent, except where required by law or valid order.

Term, termination, and retention

An account or specific resources may be terminated, suspended, or limited according to contract, business customer request, risk decision, breach of these Terms, legal requirement, partner rule, or termination of the commercial relationship.

Even after termination, Raims may retain data, records, evidence, logs, documents, financial information, audit trails, and materials related to charges for as long as necessary for legal, accounting, tax, regulatory, antifraud, dispute, chargeback, security, and defense of rights purposes.

Updates to these Terms and contact

These Terms may be updated to reflect legal, regulatory, contractual, operational, technical, commercial, or product changes. When a material change affects rights, obligations, pricing, responsibilities, or personal data processing, Raims will notify active business customers through their registered email, a dashboard notice, or another reasonable channel, with reasonable advance notice where applicable. Merely editorial changes, corrections, or clarifications without a material change may be made by updating the version and date without individual notice. Urgent changes required by law, an authority, security, or a regulated partner may take effect immediately, with notice as soon as reasonably possible. Continued use of the platform, APIs, or services after publication and effectiveness of the changes constitutes acknowledgment and acceptance of the updated Terms, unless law, contract, or a regulated partner requires advance notice, an adaptation period, or additional consent.

The business customer acknowledges that contractual, operational, compliance, blocking, limitation, suspension, document request, and transactional communications may be delivered through the registered email, authorized users, the dashboard, or official platform channels. Unless required otherwise by law, an authority order, a specific contract, or a regulated partner, a communication is deemed received when it is sent, published, or made available as a digital record.

Questions about these Terms, platform use, or security may be sent to contact@raims.com. Privacy requests and communications should be sent to dpo@raims.com. Questions about compliance, AML/CFT, KYB/KYC, risk, or operational documentation should be sent to compliance@raims.com.

Governing law and venue

These Terms are governed by and interpreted in accordance with the laws of the Federative Republic of Brazil. The Central Court of the District of São Paulo, State of São Paulo, is elected as the sole court with jurisdiction to resolve any questions, controversies, or disputes arising from use of the platform, with express waiver of any other venue, however privileged it may be.