Ripple USD 백서

Ripple USD

원문

bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 9쪽 중 4쪽

new financial instrument types are now available: AE_IPI ( aeIpi ) — AED payouts to UAE bank accounts via IPI, with FTS fallback for larger transfers IN_NEFT ( inNeft ) — INR payouts to Indian bank accounts via NEFT ID_BIFAST ( idBifast ) — IDR payouts to Indonesian bank accounts via BI-FAST TR_FAST ( trFast ) — TRY payouts to Turkish bank accounts via FAST, with EFT fallback for larger transfers PH_NRPS ( phNrps ) — PHP payouts to Philippine bank accounts via InstaPay, with PESONet fallback for larger transfers CL_TEF ( clTef ) — CLP payouts to Chilean bank accounts via TEF TH_PROMPTPAY ( thPromptpay ) — THB payouts to Thai bank accounts via PromptPay KR_KFTC ( krKftc ) — KRW payouts to South Korean bank accounts via KFTC PE_LBTR ( peLbtr ) — PEN payouts to Peruvian bank accounts via LBTR AR_INTERBANKING ( arInterbanking ) — ARS payouts to Argentine bank accounts via Interbanking For field-level details on all new instrument types, see Financial instruments . Corridor-specific identity document type restrictions Some corridors now accept only a subset of the identity document-type enum for a given payment role. Requests that use an unsupported value for identityDocuments.type / idType (individual) or registration.type (business) are rejected with a 400 error . Enforcement is based on the corridors in validatePayoutRails (at identity creation) or the financial instrument type (at instrument creation). For example, business beneficiaries on the ETH_WALLET , SOL_WALLET , and TRON_WALLET corridors must use INCORPORATION_CERTIFICATE . For the accepted values per corridor and role, see Accepted document types by corridor . June 2026 Click to expand New financial instrument types: China A new financial instrument type supports an additional China payout scenario: CN_CFXPS ( cnCfxps ) — USD payouts to China via China Foreign Exchange Payment System (CFXPS) New financial instrument types: Crypto wallets Three new financial instrument types support stablecoin payouts to crypto wallet addresses: ETH_WALLET ( ethWallet ) — USDT, USDC, and RLUSD payouts on the Ethereum network TRON_WALLET ( tronWallet ) — USDT payouts on the Tron network SOL_WALLET ( solWallet ) — USDC payouts on the Solana network All crypto wallet instruments return ZZ for the country metadata field. New financial instrument type: Hong Kong bank payout HK_BANK_PAYOUT ( hkBankPayout ) enables HKD payouts to Hong Kong bank accounts via CHATS. Required fields include bankName , accountNumber , accountHolderName , and swiftCode . Pre-clearance is required for all senders. New financial instrument types: Africa bank payouts Five new financial instrument types for African bank payouts are now available, enabling NGN-era corridor expansion to additional markets: GH_BANK_PAYOUT ( ghBankPayout ) — Ghana (GHS), via GIS RW_BANK_PAYOUT ( rwBankPayout ) — Rwanda (RWF), via RSwitch ZA_BANK_PAYOUT ( zaBankPayout ) — South Africa (ZAR), via PayShap. Supported use case: C2B2C only. UG_BANK_PAYOUT ( ugBankPayout ) — Uganda (UGX) ZM_BANK_PAYOUT ( zmBankPayout ) — Zambia (ZMW), via ZECHL For field-level details on all new instrument types, see Financial instruments . Bank Codes lookup The Bank Codes lookup utility now covers all supported bank code corridors in a single interface. Select the destination country to view supported bank codes; for countries with multiple currencies, select the currency to narrow results. Nigeria (NGN): Returns Ripple Bank Codes (RBCs) in the format RPL:NG:[ALIAS]:BNK . China (CNY): Returns CNAPS codes (China National Advanced Payment System). China (USD): Returns SWIFT/BIC codes. For more information, see Bank Codes . April 2026 Click to expand New funding model: Just-in-time (JIT) funding A new payinCategory value, JIT_FUNDING , is now available when creating quotes. JIT-funded payments enter a new AWAITING_FUNDING state after creation and proceed once funds are received in your Ripple ledger account before the jitFundingExpiresAt deadline. For more information, see Funding model and Payment states . New payinCategory values: PRE_FUNDING and CREDIT_FUNDING Two new payinCategory values are introduced as the preferred replacements for the deprecated values: PRE_FUNDING replaces FUNDED CREDIT_FUNDING replaces T_PLUS_ONE The deprecated values FUNDED and T_PLUS_ONE continue to be accepted on v2 quote endpoints and are not being removed at this time. New integrations should use the new values. New payment state: AWAITING_FUNDING A new non-terminal payment state, AWAITING_FUNDING , is introduced for JIT-funded payments. For more information, see Payment states . New payment response fields: payoutExecutionDetails and jitFundingExpiresAt The GET /v3/payments/{paymentId} response now includes two new fields: payoutExecutionDetails (optional): metadata about how a payment was executed, including paymentRailUsed , payoutStartTime , payoutEndTime , and trackingReferences (network-specific identifiers such as IMAD/OMAD for Fedwire). Coverage varies by corridor and partner. For more information, see Payment execution details . jitFundingExpiresAt : present on JIT-funded payments; indicates the deadline by which funds must be transferred to your Ripple ledger account for the payment to proceed. New API endpoint: GET /v3/identities/by-internal-id/{internal-id} You can now retrieve an active identity using your own client-provided internalId , without needing the Ripple-generated identityId . The endpoint returns only identities in the ACTIVE state and always returns the latest version. For more information, see Create and manage identities . Renamed financial instrument type: AFRICA_BANK_PAYOUT is now NG_BANK_PAYOUT The Africa bank payout financial instrument type has been renamed from AFRICA_BANK_PAYOUT to NG_BANK_PAYOUT . Update any integration code, identity validatePayoutRails arrays, or internal tooling that references the old value. For more information, see Financial instruments . Reduced data requirements for US ACH Based on customer feedback, the following identity fields are no longer required when creating identity tokens for US ACH payments: registration — no longer required for BUSINESS ORIGINATOR and BUSINESS BENEFICIARY identities identityDocuments — no longer required for INDIVIDUAL BENEFICIARY identities For an updated list of required fields by corridor, use the Payload Schema Utility . Corrected GET /v2/ledger-transactions response schema The response schema for GET /v2/ledger-transactions was incorrectly defined as an array. It has been corrected to an object containing pagination metadata ( offset , pageSize , pageElements , total ) and a statementTransactions array. Customers using OpenAPI generators against a previous version of this spec may need to regenerate their client code. The text/csv response schema has also been corrected and now includes column documentation and an example row. March 2026 Click to expand Documentation versioning: v2026.03 and v2025.11 The Payments Direct documentation is now versioned. Use the version selector to switch between versions: v2026.03 (this version) - Documents the Payments Direct API with Identity Management v3 , including the v3 identity and financial instrument endpoints. v2025.11 - Documents the Payments Direct API with Identity Management v2 . January 2026 Click to expand New API endpoint: GET /v2/ledger-transactions Provides a paginated list of ledger transactions and running balances for a specified UTC time range, supporting customer reconciliation and operational reporting. For more information, see Ledger transactions . New payment state: RETURNED Payments that were previously marked as COMPLETED but later reversed by the payout partner or network are now marked as RETURNED . For more information, see Payment lifecycle and Payment returns . Feature enhancement: Tax transparency We have introduced a detailed tax breakdown structure to both Quote and Payment responses to support transparent reporting of tax liabilities and service fees. November 2025 Click to expand Enhancements and payout network expansions Released the Transaction Memo feature for EUR/GBP payouts Payouts enabled: PHP, CN-USD, and INR October 2025 Click to expand Enhancements and payout network expansions Released the Transaction Memo feature for USD payouts Payouts enabled: AED, AUD, CLP, COP, JPY, IDR, KRW, PEN, THB, and VND September 2025 Click to expand Enhancements Released FedWire payouts with Lead Bank Released FX benchmark improvements to reduce price gaps with stablecoins August 2025 Click to expand Enhancements Released Maker/Checker feature in Payments Direct , enabling payment approval workflows Released the OpenAPI specification for Payments Direct , available for download here . July 2025 Click to expand Enhancements Released off-ramp capabilities to deliver RLUSD June 2025 Click to expand Additional payout markets enabled RTP payouts enabled in the US EUR/GBP payouts enabled May 2025 Click to expand Additional payout markets enabled Payouts enabled for BRL, CNY, GHS, NGN, RWF, ZAR, UGX, and ZMW April 2025 Click to expand Enhancements and network expansions ACH payouts enabled using iPayout Payments Direct on-ramps launched for customers to send in stablecoins, beginning with USDC and USDT Re-designed payment flow in Payments Direct to simplify and enhance the user experience March 2025 Click to expand Off-ramps Beta launched Off-ramps beta launched for Payments Direct customers, allow customers to pay-in stablecoins in key payout markets February 2025 Click to expand Official launch of Payments Direct Payments Direct , allows you to connect to Ripple as a payments provider. Ripple takes care of delivering payments to beneficiaries, managing payout partners, providing funds to payout partners, and paying charges in exchange for payment delivery to the beneficiaries. With Payments Direct , you can send payments and manage beneficiaries using the Payments Direct UI . ## /products/payments-direct-2/support Support View as Markdown View as Markdown Open this page as Markdown Copy for LLM Copy page as Markdown for LLMs Open in Claude Get insights from Claude Open in ChatGPT Get insights from ChatGPT Ripple supports all issues and payment failures after go-live during the course of normal business activities. The Technical Services team at Ripple provides expert technical assistance for fast problem resolution. The Project team sets up a handover to the Technical Services team prior to commercialization, and the Technical Services team walks you through the channels available for raising support tickets. Support model Ripple's support model is built around two tiers of support: Level 1: Technical Service Engineering All issues submitted to Ripple Support are first routed to a Technical Services Engineer (TSE) for review. This team provides 24 x 7 x 365 support to customers based on the terms in their contract. A TSE reviews your request to confirm that all the details required to troubleshoot the issue have been provided. They will ask for any additional details, such as logs or the payment object, that were not included. Once received, the team reviews the data to troubleshoot the issue. If the TSE suspects the problem lies with the counterparty's Ripple setup rather than yours, they request logs or additional information from the counterparty. Once the TSE has all the requested information, they trace the payment flows between the parties to find the root cause, then communicate the root cause and the fix or workaround to you. If the TSE suspects the issue is caused by a bug or defect in Ripple's products, they request additional assistance from Level 2 support. Level 2: Ripple Engineering and Infrastructure Ripple Engineering and Infrastructure reviews any issue whose root cause could be a bug or defect. The first step is to recreate the issue in-house. The teams then identify the code defect causing the issue and evaluate potential solutions, which could include a code fix or a technical or business workaround for you to implement. If a code fix is necessary, Ripple Engineering releases a patch. Patches are tested in-house to confirm the issue is resolved, and further regression testing confirms the fix has not affected other system functionality. Depending on the severity of the issue, the fix is released either as an emergency fix for urgent issues, or as part of an upcoming release if you can resume business as usual with a workaround in the meantime. Ripple Services Support Portal You can report an incident and manage your support tickets through the Ripple Services Support Portal. Access to the Support Portal uses the same account you use to sign in to the Payments Direct UI at home.ripple.com . For more information, see Sign in to your Ripple account . Note The Ripple Support Portal uses Atlassian Jira to process support requests. If your company has firewall or network restrictions, ask your organization's IT team to allowlist https://ripplenet.atlassian.net . For more details, see IP addresses and domains for Atlassian cloud products . Open a support ticket To submit a support request: Go to home.ripple.com and locate the Get support widget. Select Contact support to display the Contact Support information. Note Use Go to Support Portal as your preferred way to contact Ripple support. The email address is provided mainly in case you have trouble reaching the Support Portal. Select Go to Support Portal . This displays the Support Portal page. Select the Ripple product you need support for. This displays the Ripple Support form. Complete the form and select Send to submit your request. This displays the new support ticket. You also receive an email confirming the ticket was created, containing a View request link. To check the progress of the ticket, use the View request link in the email to display the current status. To update the ticket, either add a comment in the ticket itself or reply to the email. ## /products/payments-direct-2/user-interface/home Home View as Markdown View as Markdown Open this page as Markdown Copy for LLM Copy page as Markdown for LLMs Open in Claude Get insights from Claude Open in ChatGPT Get insights from ChatGPT The Payments Direct UI lets you manage the operational and technical aspects of your payments business from one interface. You can access the Payments Direct UI at home.ripple.com . The Home page displays widgets containing tasks to complete before you can use Ripple Payments , payment statistics, an exchange rate calculator, and support resources. The following sections provide more information about these widgets. Switch between organizations If your account has access to more than one organization, the organization switcher at the top of the navigation menu lets you move between them without signing out. When you switch, Ripple Payments loads the data and permissions for the selected organization and returns you to its Home page. For more information, see Switch between organizations . Get started The Get started widget serves as your entry point into Ripple Payments . It shows which tasks you must complete before you can use Ripple Payments . Note This widget is available only as long as onboarding with Ripple Payments is in progress. Once onboarding is complete, this widget disappears. In the following example, the user has completed two out of three tasks related to onboarding, which must be completed to verify their business. The user hasn't completed any tasks related to account setup, which must be completed to make payments. Make sure to complete all tasks before you attempt to use Ripple Payments for the first time. Depending on the status of your task, you'll see the following buttons next to it: Start -- indicates that the task hasn't been started yet. Continue -- indicates that the task has been started but not completed yet. View -- indicates that the task has been completed and you can review the information you've provided. Note Make sure the information you enter is complete and accurate before you complete the task. Once a task is completed, you can no longer edit any of the information. For questions about onboarding, contact your Ripple liaison. Account balance For accounts using pre-funding -- that is, fiat assets are deposited before payments are processed -- the Account balance widget shows the balance for a given currency. Account balances aren't displayed in real time as it takes a moment to update the balance after a funds transfer, longer if the transfer was initiated on the weekend. Each currency in the widget has an options menu (⋮) that provides the following actions: How to deposit funds -- Opens deposit instructions for the selected currency. For more information, see Deposit funds . How to withdraw funds -- Opens the Withdraw Funds panel, where you can submit a request to return prefunded assets to your registered bank account or crypto wallet. For more information, see Withdraw funds . For a general overview of pre-funding and other funding methods, see Funding methods . Last payments The Last payments widget shows you the last five payments you've created, including: the date and time when you created the payment the name of the beneficiary the amount and currency sent the amount and currency received the status of the payment The status can either be Executed , In Progress , or Failed . Select one of the payments to see its details or select View All to see a list of all payments you've created. Exchange rate In the Exchange Rate widget, change the values and currency pairs as you want in either the top or bottom field to see the rate change. Note Any changes you make to the currency defaults will be reflected in the widget the next time you load the Home page. Get support The Get support widget guides you to the contact page for Ripple's Technical Support team, and the technical documentation website. ## /products/payments-direct-2/user-interface/guides/send-a-payment Send a single payment View as Markdown View as Markdown Open this page as Markdown Copy for LLM Copy page as Markdown for LLMs Open in Claude Get insights from Claude Open in ChatGPT Get insights from ChatGPT This tutorial describes the steps involved in sending a single payment using Payments Direct . Select the Payments tab. Select Create Payment > Individual . Only if you're approved to send a payment on behalf of someone else: In the Originator section, select one of the following originator options: < Name >: Select this option if you're the one originating the payment. Another business or individual : Select this option if you're originating the payment on someone's behalf. If you selected 'Another business or individual' : Select the originator identity that you want to use to send the payment. Then select Next . In the Beneficiary section, select the beneficiary identity that you want to use. Then select Next . Tip Search for your beneficiary by entering their nickname, identity type, or date created in the search field. Alternatively, if you don't see the beneficiary you want to use, select + Add beneficiary to create a new beneficiary. For more information on how to create a beneficiary identity, see Beneficiaries . In the Payment details section, enter all required payment details. Funds from -- Specifies where the funds for the payment come from. Sending amount -- Specifies the amount and currency you want to send. Note You can select from either fiat currency or cryptocurrency (Stablecoin). Receiving amount -- Specifies the amount and currency you want the beneficiary to receive. Transaction purpose -- Specifies the purpose of the transaction. Once you've entered either the sending or receiving amount, you'll see a quo
프로젝트로 돌아가기