[{"data":1,"prerenderedAt":1170},["ShallowReactive",2],{"content-\u002Fresources\u002Fmore\u002Fcross-border-quote-screen-fee-disclosure":3,"resources-category-cross-border-quote-screen-fee-disclosure":775},{"id":4,"title":5,"authors":6,"body":7,"categories":6,"category":724,"categoryType":6,"compare":6,"contributors":6,"date":725,"description":726,"extension":727,"faq":728,"howto":744,"isBlog":765,"isChangelog":765,"meta":766,"navigation":768,"path":769,"pillar":765,"products":6,"rawbody":770,"role":6,"seo":771,"seoTitle":772,"stem":773,"thumbnail":6,"updated":725,"__hash__":774},"content\u002Fresources\u002Fmore\u002Fcross-border-quote-screen-fee-disclosure.md","How to show a cross-border payment quote to users: rate, fees, and expiry",null,{"type":8,"value":9,"toc":711},"minimark",[10,14,17,23,42,47,56,207,210,217,221,224,236,248,272,278,289,300,303,306,310,313,328,336,340,343,357,371,419,427,431,434,444,447,482,490,494,497,551,571,575,578,630,634,637,689,692,696],[11,12,13],"p",{},"A cross-border quote screen should show six things before the user confirms: amount sent, every fee, the exchange rate, the amount the recipient gets, when the quote expires, and when the money arrives. US consumer remittances must show most of these by law. BlindPay quotes return each figure as a field, with a 5-minute expiry, so the screen can render straight from the response.",[11,15,16],{},"Most quote screens fail in the same three places. They hide the margin in the rate, they let an expired rate through, and they promise \"instant\" for a rail that takes days.",[11,18,19],{},[20,21,22],"strong",{},"Key takeaways",[24,25,26,30,33,36,39],"ul",{},[27,28,29],"li",{},"Show amount sent, fees, total, rate, amount received, expiry, and delivery estimate. Leave nothing for the user to compute.",[27,31,32],{},"US consumer remittances fall under the CFPB Remittance Transfer Rule: pre-payment disclosure, receipt, 30-minute cancellation, and error resolution.",[27,34,35],{},"The EU requires online credit transfers with currency conversion to show estimated conversion charges and the estimated total before the payment starts.",[27,37,38],{},"Drive the countdown from the quote's expiry, disable confirm at zero, and requote visibly.",[27,40,41],{},"Delivery estimates depend on the rail. Pix and SPEI land in minutes; ACH, SEPA, and SWIFT take business days.",[43,44,46],"h2",{"id":45},"what-should-a-cross-border-quote-screen-show","What should a cross-border quote screen show?",[11,48,49,50,55],{},"It should show every number the user needs to judge the payment, taken from one firm quote, so the user never has to calculate anything. Here is the full list and where each line comes from in a BlindPay payout quote (",[51,52,54],"a",{"href":53},"\u002Fdocs\u002Fpayout-quotes","payout quotes",").",[57,58,59,75],"table",{},[60,61,62],"thead",{},[63,64,65,69,72],"tr",{},[66,67,68],"th",{},"Line on screen",[66,70,71],{},"Why it matters",[66,73,74],{},"BlindPay quote field",[76,77,78,94,114,128,141,154,167,181,196],"tbody",{},[63,79,80,84,87],{},[81,82,83],"td",{},"You send",[81,85,86],{},"The amount debited or funded",[81,88,89,93],{},[90,91,92],"code",{},"sender_amount"," (minor units)",[63,95,96,99,102],{},[81,97,98],{},"Fees, itemized",[81,100,101],{},"Separates your fees from provider fees",[81,103,104,107,108,107,111],{},[90,105,106],{},"flat_fee",", ",[90,109,110],{},"partner_fee_amount",[90,112,113],{},"billing_fee_amount",[63,115,116,119,122],{},[81,117,118],{},"Total charged",[81,120,121],{},"What actually leaves the user's balance",[81,123,124,125],{},"Derived from the amounts above and ",[90,126,127],{},"cover_fees",[63,129,130,133,136],{},[81,131,132],{},"Exchange rate, with direction",[81,134,135],{},"Shows the price of the currency",[81,137,138],{},[90,139,140],{},"blindpay_quotation",[63,142,143,146,149],{},[81,144,145],{},"Market rate (optional)",[81,147,148],{},"Makes the margin visible",[81,150,151],{},[90,152,153],{},"commercial_quotation",[63,155,156,159,162],{},[81,157,158],{},"Recipient gets",[81,160,161],{},"The number the recipient checks",[81,163,164,93],{},[90,165,166],{},"receiver_amount",[63,168,169,172,175],{},[81,170,171],{},"Quote expires in",[81,173,174],{},"Tells the user the numbers are firm, but not forever",[81,176,177,180],{},[90,178,179],{},"expires_at"," (epoch milliseconds)",[63,182,183,186,189],{},[81,184,185],{},"Estimated arrival",[81,187,188],{},"Sets expectations per rail",[81,190,191,192],{},"From the rail; see ",[51,193,195],{"href":194},"\u002Fdocs\u002Fkb\u002Fcut-off-times","cut-off times",[63,197,198,201,204],{},[81,199,200],{},"Recipient",[81,202,203],{},"Name and masked account, so the user can spot a mistake",[81,205,206],{},"From the saved bank account",[11,208,209],{},"Two formatting rules. Amounts come back as integers in minor units, so divide by 100 for USD, BRL, and MXN before display. And write the rate with its direction, such as \"1 USD = 5.3730 BRL\", because a bare \"5.373\" means nothing to someone comparing two apps.",[11,211,212,216],{},[51,213,215],{"href":214},"\u002Fresources\u002Fmore\u002Fstablecoin-api-quotes-explained","Stablecoin API quotes explained"," covers the API side of these fields: what a quote locks, fee direction, and minor units. This page is about what the user sees.",[43,218,220],{"id":219},"what-does-the-cfpb-remittance-transfer-rule-require","What does the CFPB Remittance Transfer Rule require?",[11,222,223],{},"For consumer remittances sent from the US, the CFPB's Remittance Transfer Rule (Regulation E, subpart B, 12 CFR 1005.30 to 1005.36) requires a disclosure before payment, a receipt after it, a 30-minute cancellation right, and an error resolution process.",[11,225,226,229,230,55],{},[20,227,228],{},"Who it covers."," A remittance transfer is an electronic transfer requested by a consumer to a recipient abroad, excluding transfers of $15 or less. The sender must be a consumer acting mainly for personal, family, or household purposes, so business-purpose payments generally fall outside it. A provider that made 500 or fewer remittance transfers in the previous calendar year and makes 500 or fewer in the current one is not treated as providing them in the normal course of business (",[51,231,235],{"href":232,"rel":233},"https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F12\u002F1005.30",[234],"nofollow","12 CFR 1005.30",[11,237,238,241,242,247],{},[20,239,240],{},"Pre-payment disclosure."," Before the sender pays, ",[51,243,246],{"href":244,"rel":245},"https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F12\u002F1005.31",[234],"12 CFR 1005.31"," requires:",[249,250,251,254,257,260,263,266,269],"ol",{},[27,252,253],{},"The transfer amount, in the currency the sender funds it with.",[27,255,256],{},"Fees and taxes the provider charges.",[27,258,259],{},"The total, the sum of the two.",[27,261,262],{},"The exchange rate, rounded consistently to between two and four decimal places.",[27,264,265],{},"Covered third-party fees, and the amount in the recipient's currency.",[27,267,268],{},"The total to recipient, in the recipient's currency.",[27,270,271],{},"A statement that fees or taxes charged by others may reduce what the recipient gets, where they may apply.",[11,273,274,277],{},[20,275,276],{},"Receipt."," Everything above, plus the date funds will be available, the recipient's name, a statement of error and cancellation rights, and contact details for the provider, the state regulator, and the CFPB.",[11,279,280,283,284,55],{},[20,281,282],{},"Cancellation."," The sender can cancel if the request arrives no later than 30 minutes after payment and the funds haven't been picked up or deposited. The provider refunds the full amount, fees included, within three business days (",[51,285,288],{"href":286,"rel":287},"https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F12\u002F1005.34",[234],"12 CFR 1005.34",[11,290,291,294,295,55],{},[20,292,293],{},"Errors."," The sender has 180 days after the disclosed availability date to report an error, such as a wrong amount or funds that arrive late. The provider has 90 days to investigate (",[51,296,299],{"href":297,"rel":298},"https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F12\u002F1005.33",[234],"12 CFR 1005.33",[11,301,302],{},"What this means for the screen: if you serve US consumers, the 30-minute window and the \"date available\" line belong in your product spec from day one. Adding them later means redesigning confirmation and receipt flows.",[11,304,305],{},"This is for information only and is not legal advice. Whether your product is a remittance transfer provider depends on your facts.",[43,307,309],{"id":308},"what-do-eu-rules-require-on-a-quote-screen","What do EU rules require on a quote screen?",[11,311,312],{},"For online credit transfers that include a currency conversion, EU rules require the payer's provider to show the estimated conversion charges and the estimated total amount before the payment starts.",[11,314,315,316,321,322,327],{},"The requirement is Article 3b of Regulation (EC) No 924\u002F2009, inserted by ",[51,317,320],{"href":318,"rel":319},"https:\u002F\u002Feur-lex.europa.eu\u002Flegal-content\u002FEN\u002FTXT\u002FHTML\u002F?uri=CELEX:32019R0518",[234],"Regulation (EU) 2019\u002F518"," and applied from 19 April 2020. The information has to be \"clear, neutral and comprehensible\". For card-based payments, the same regulation goes further and expresses conversion charges as a percentage markup over the latest ",[51,323,326],{"href":324,"rel":325},"https:\u002F\u002Fwww.ecb.europa.eu\u002Fstats\u002Fpolicy_and_exchange_rates\u002Feuro_reference_exchange_rates\u002Fhtml\u002Findex.en.html",[234],"ECB euro reference rates",".",[11,329,330,331,335],{},"Even outside the EU, that percentage-over-reference format is a good pattern. Users understand \"0.5% above the market rate\" faster than two rates with four decimals each. ",[51,332,334],{"href":333},"\u002Fresources\u002Fmore\u002Fhow-to-calculate-fx-spread","How to calculate FX spread"," shows how to compute that number from a quote.",[43,337,339],{"id":338},"how-should-the-screen-handle-who-pays-the-fee","How should the screen handle who pays the fee?",[11,341,342],{},"Decide which side of the payment is fixed, then show fees in a way that matches it. Two choices drive this: which amount the user types, and who absorbs the fees.",[11,344,345,348,349,352,353,356],{},[20,346,347],{},"Which amount is fixed."," A business paying a supplier invoice usually knows the amount the supplier must receive. A user sending money home usually knows how much they want to spend. Offer both modes. In BlindPay quotes, ",[90,350,351],{},"currency_type: \"sender\""," fixes the stablecoin amount sent, and ",[90,354,355],{},"currency_type: \"receiver\""," fixes the fiat amount the bank account receives.",[11,358,359,362,363,366,367,370],{},[20,360,361],{},"Who pays fees."," With ",[90,364,365],{},"cover_fees: false",", fees are deducted from the fiat the recipient receives. With ",[90,368,369],{},"cover_fees: true",", they are added on top of the amount sent, so the recipient gets the full figure. On screen:",[57,372,373,389],{},[60,374,375],{},[63,376,377,380,383,386],{},[66,378,379],{},"Mode",[66,381,382],{},"User types",[66,384,385],{},"Fees appear as",[66,387,388],{},"Recipient sees",[76,390,391,405],{},[63,392,393,396,399,402],{},[81,394,395],{},"Fixed receive, sender covers fees",[81,397,398],{},"R$10,000 to receive",[81,400,401],{},"Added to the amount sent",[81,403,404],{},"Exactly R$10,000",[63,406,407,410,413,416],{},[81,408,409],{},"Fixed send, recipient absorbs fees",[81,411,412],{},"$2,000 to send",[81,414,415],{},"Deducted before conversion",[81,417,418],{},"Less than $2,000 x rate",[11,420,421,422,426],{},"For invoices, fixed receive with the sender covering fees is almost always right. A supplier who gets R$9,940 against a R$10,000 invoice will chase the gap, and your user pays for the follow-up. ",[51,423,425],{"href":424},"\u002Fresources\u002Fmore\u002Fhidden-fees-international-wires-our-sha-ben","Hidden fees in international wires"," explains why the same problem shows up with SWIFT SHA and BEN charges.",[43,428,430],{"id":429},"how-should-you-handle-quote-expiry-in-the-ui","How should you handle quote expiry in the UI?",[11,432,433],{},"Run a visible countdown from the quote's expiry time, block confirmation when it reaches zero, and fetch a new quote that the user must confirm again. Never let an expired price through.",[11,435,436,437,439,440,443],{},"BlindPay payout and payin quotes expire after 5 minutes by default, and some rails can return less, such as SEPA payout quotes. ",[90,438,179],{}," is in epoch milliseconds, so compare it to ",[90,441,442],{},"Date.now()"," directly. Read it from every response instead of hardcoding 5 minutes.",[11,445,446],{},"A pattern that works:",[249,448,449,458,464,470,476],{},[27,450,451,457],{},[20,452,453,454,456],{},"Start the timer from ",[90,455,179],{},","," not from when the screen rendered. Network latency eats seconds.",[27,459,460,463],{},[20,461,462],{},"Leave a buffer."," Stop accepting confirmation a few seconds before expiry so the execute call lands while the quote is still valid.",[27,465,466,469],{},[20,467,468],{},"Disable, then explain."," \"This rate expired. Rates change every few seconds. Get a new quote?\"",[27,471,472,475],{},[20,473,474],{},"Show the new numbers."," If the rate moved, show what changed before the user confirms again.",[27,477,478,481],{},[20,479,480],{},"Requote on return."," If the user leaves the tab and comes back, check expiry immediately.",[11,483,484,485,489],{},"Short expiries are a feature. A provider that locks a rate for an hour has priced an hour of market risk into that rate. ",[51,486,488],{"href":487},"\u002Fresources\u002Fmore\u002Fstablecoin-fx-slippage-live-quotes","Stablecoin FX slippage"," explains the trade-off.",[43,491,493],{"id":492},"what-delivery-estimate-should-the-screen-show","What delivery estimate should the screen show?",[11,495,496],{},"Show an estimate per rail, adjusted for cut-offs and weekends, and never \"instant\" for a rail that runs on business days. The rail is the biggest driver of arrival time.",[57,498,499,509],{},[60,500,501],{},[63,502,503,506],{},[66,504,505],{},"Rail",[66,507,508],{},"Typical BlindPay payout timing",[76,510,511,519,527,535,543],{},[63,512,513,516],{},[81,514,515],{},"Pix (Brazil), SPEI (Mexico), Transfers 3.0 (Argentina)",[81,517,518],{},"Minutes; Pix and SPEI run 24\u002F7",[63,520,521,524],{},[81,522,523],{},"RTP (US)",[81,525,526],{},"Instant",[63,528,529,532],{},[81,530,531],{},"ACH, wire (US)",[81,533,534],{},"ACH about 2 business days; wire about 1 business day",[63,536,537,540],{},[81,538,539],{},"TED (Brazil), ACH Colombia, SEPA",[81,541,542],{},"About 1 business day",[63,544,545,548],{},[81,546,547],{},"SWIFT (POBO\u002FCOBO)",[81,549,550],{},"About 5 business days, after compliance documents are approved",[11,552,553,554,107,558,562,563,565,566,570],{},"Source: ",[51,555,557],{"href":556},"\u002Fdocs\u002Fbank-accounts","bank accounts",[51,559,561],{"href":560},"\u002Fdocs\u002Fkb\u002Fpayment-methods","payment methods",", and ",[51,564,195],{"href":194},". High volume can stretch any estimate, and payouts can be held for compliance review, so phrase it as \"usually arrives by\" rather than a promise. ",[51,567,569],{"href":568},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-cut-off-times-weekends-holidays","Do stablecoin payouts work on weekends?"," covers the calendar side.",[43,572,574],{"id":573},"what-should-the-receipt-and-status-screen-show","What should the receipt and status screen show?",[11,576,577],{},"The receipt should repeat the exact quote figures, add a payment reference and status, and tell the user how to get help. It is the screen users come back to when something looks wrong.",[24,579,580,586,614,624],{},[27,581,582,585],{},[20,583,584],{},"The same numbers as the quote."," Amount sent, fees, rate, amount received. If they differ, you have a bug.",[27,587,588,591,592,107,595,107,598,107,601,604,605,608,609,613],{},[20,589,590],{},"Status in plain words."," BlindPay payouts move through ",[90,593,594],{},"processing",[90,596,597],{},"on_hold",[90,599,600],{},"completed",[90,602,603],{},"failed",", or ",[90,606,607],{},"refunded",". Map each to a sentence. ",[51,610,612],{"href":611},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-statuses-explained","Stablecoin payout statuses explained"," has suggested wording.",[27,615,616,619,620,55],{},[20,617,618],{},"A reference the recipient's bank understands."," For SWIFT payouts, show the UETR once it is populated; every bank in the chain uses it. BlindPay sends SWIFT payments on behalf of the customer (POBO\u002FCOBO) with UETR tracking and MT103 confirmations (",[51,621,623],{"href":622},"\u002Fdocs\u002Fkb\u002Fpobo-cobo","POBO and COBO",[27,625,626,629],{},[20,627,628],{},"A help path."," For US consumer remittances, the receipt must include error and cancellation rights and contact details.",[43,631,633],{"id":632},"how-does-blindpay-help-you-build-the-quote-screen","How does BlindPay help you build the quote screen?",[11,635,636],{},"Every line on the screen maps to a field in one BlindPay quote, so the UI renders from a single response and executes against the same quote ID.",[24,638,639,660,672,683],{},[27,640,641,644,645,107,647,107,649,107,651,107,653,107,655,562,657,659],{},[20,642,643],{},"One quote, every figure."," ",[90,646,92],{},[90,648,166],{},[90,650,153],{},[90,652,140],{},[90,654,106],{},[90,656,110],{},[90,658,179],{}," in one response.",[27,661,662,644,665,667,668,671],{},[20,663,664],{},"Both fee modes.",[90,666,127],{}," and ",[90,669,670],{},"currency_type"," support fixed-send and fixed-receive screens without extra math on your side.",[27,673,674,677,678,682],{},[20,675,676],{},"Your margin, itemized."," A ",[51,679,681],{"href":680},"\u002Fdocs\u002Flearn\u002Fpartner-fees","partner fee"," adds your markup to the quote as its own line, so you can show it separately from BlindPay's fee.",[27,684,685,688],{},[20,686,687],{},"Rails behind one call."," Pix, SPEI, ACH, RTP, SEPA, Transfers 3.0, ACH Colombia, and SWIFT (POBO\u002FCOBO), funded from stablecoins at send time with no pre-funding.",[11,690,691],{},"The disclosure duties themselves sit with whoever is the provider to the end user. BlindPay gives you the numbers; your product decides how to present them and which rules apply.",[43,693,695],{"id":694},"what-to-do-next","What to do next",[11,697,698,699,703,704,706,707,327],{},"Sketch your quote screen against the table at the top of this page and mark any line you can't fill from a single quote. Then create a test quote from the ",[51,700,702],{"href":701},"\u002Fdocs\u002Fquickstart-payout","payout quickstart"," and render it: amount sent, fees, rate with direction, amount received, and a countdown from ",[90,705,179],{},". For the bigger picture, read ",[51,708,710],{"href":709},"\u002Fresources\u002Fmore\u002Fwhat-is-real-time-cross-border-settlement","what real-time cross-border settlement is",{"title":712,"searchDepth":713,"depth":713,"links":714},"",2,[715,716,717,718,719,720,721,722,723],{"id":45,"depth":713,"text":46},{"id":219,"depth":713,"text":220},{"id":308,"depth":713,"text":309},{"id":338,"depth":713,"text":339},{"id":429,"depth":713,"text":430},{"id":492,"depth":713,"text":493},{"id":573,"depth":713,"text":574},{"id":632,"depth":713,"text":633},{"id":694,"depth":713,"text":695},"payments","2026-10-07","What a cross-border quote screen must show: amount sent, rate, fees, amount received, expiry, and delivery date, plus the CFPB and EU disclosure rules.","md",[729,732,735,738,741],{"q":730,"a":731},"What must a cross-border payment quote show?","At minimum: the amount sent, every fee, the total charged, the exchange rate, the amount the recipient gets in their currency, when the quote expires, and when the money should arrive. For US consumer remittances the CFPB's Remittance Transfer Rule makes most of these mandatory before the sender pays, with the delivery date on the receipt.",{"q":733,"a":734},"Does the CFPB Remittance Transfer Rule apply to business payments?","The rule protects a sender who is a consumer sending money mainly for personal, family, or household purposes, so payments a company makes for business purposes generally fall outside it. Providers that made 500 or fewer remittance transfers in both the previous and current calendar year are also outside the provider definition. Confirm your own case with counsel.",{"q":736,"a":737},"How many decimal places should the exchange rate show?","For US consumer remittances, Regulation E requires the disclosed exchange rate to be rounded consistently for each currency to no fewer than two and no more than four decimal places. Outside that rule, four decimal places is a sensible default for most pairs, and the rate should always say which direction it runs, such as 1 USD = 5.3730 BRL.",{"q":739,"a":740},"What should happen when a quote expires on screen?","Disable the confirm button the moment the countdown hits zero, explain that rates move, and offer a one-click new quote. Show the refreshed numbers and make the user confirm again. Silently replacing an expired quote with a new rate at the moment of confirmation is the fastest way to lose trust.",{"q":742,"a":743},"Should a quote screen show the mid-market rate?","It helps. Showing the market rate next to your rate lets users see the margin, and EU rules already push card currency conversion toward a percentage markup over the ECB reference rate. At BlindPay, every quote returns commercial_quotation and blindpay_quotation, so you can display both without a separate data feed.",{"name":745,"steps":746},"How to build a cross-border payment quote screen",[747,750,753,756,759,762],{"name":748,"text":749},"Ask which side is fixed","Let the user choose between a fixed amount to send and a fixed amount to receive, and request the quote in that mode.",{"name":751,"text":752},"Request a firm quote","Call the quote endpoint with the amount, the recipient's bank account, and who pays the fees. Store the quote ID and its expiry.",{"name":754,"text":755},"Render every line","Show amount sent, each fee, total charged, exchange rate, amount received, and the estimated delivery date, all from the quote response.",{"name":757,"text":758},"Run a countdown from the expiry","Count down to the quote's expiry time. When it reaches zero, disable the confirm button and offer a new quote.",{"name":760,"text":761},"Requote visibly","Fetch a fresh quote and show the new numbers. Never swap in a different rate without the user seeing it before confirming.",{"name":763,"text":764},"Confirm and issue a receipt","Execute the payment against the quote ID, then show a receipt with the same figures, the payment reference, the status, and how to get help.",false,{"author":767},"BlindPay Team",true,"\u002Fresources\u002Fmore\u002Fcross-border-quote-screen-fee-disclosure","---\ntitle: \"How to show a cross-border payment quote to users: rate, fees, and expiry\"\nseoTitle: \"Cross-border quote screen: rate, fees, expiry, disclosure\"\ndescription: \"What a cross-border quote screen must show: amount sent, rate, fees, amount received, expiry, and delivery date, plus the CFPB and EU disclosure rules.\"\ndate: \"2026-10-07\"\nupdated: \"2026-10-07\"\ncategory: \"payments\"\nauthor: \"BlindPay Team\"\nhowto:\n  name: \"How to build a cross-border payment quote screen\"\n  steps:\n    - name: \"Ask which side is fixed\"\n      text: \"Let the user choose between a fixed amount to send and a fixed amount to receive, and request the quote in that mode.\"\n    - name: \"Request a firm quote\"\n      text: \"Call the quote endpoint with the amount, the recipient's bank account, and who pays the fees. Store the quote ID and its expiry.\"\n    - name: \"Render every line\"\n      text: \"Show amount sent, each fee, total charged, exchange rate, amount received, and the estimated delivery date, all from the quote response.\"\n    - name: \"Run a countdown from the expiry\"\n      text: \"Count down to the quote's expiry time. When it reaches zero, disable the confirm button and offer a new quote.\"\n    - name: \"Requote visibly\"\n      text: \"Fetch a fresh quote and show the new numbers. Never swap in a different rate without the user seeing it before confirming.\"\n    - name: \"Confirm and issue a receipt\"\n      text: \"Execute the payment against the quote ID, then show a receipt with the same figures, the payment reference, the status, and how to get help.\"\nfaq:\n  - q: \"What must a cross-border payment quote show?\"\n    a: \"At minimum: the amount sent, every fee, the total charged, the exchange rate, the amount the recipient gets in their currency, when the quote expires, and when the money should arrive. For US consumer remittances the CFPB's Remittance Transfer Rule makes most of these mandatory before the sender pays, with the delivery date on the receipt.\"\n  - q: \"Does the CFPB Remittance Transfer Rule apply to business payments?\"\n    a: \"The rule protects a sender who is a consumer sending money mainly for personal, family, or household purposes, so payments a company makes for business purposes generally fall outside it. Providers that made 500 or fewer remittance transfers in both the previous and current calendar year are also outside the provider definition. Confirm your own case with counsel.\"\n  - q: \"How many decimal places should the exchange rate show?\"\n    a: \"For US consumer remittances, Regulation E requires the disclosed exchange rate to be rounded consistently for each currency to no fewer than two and no more than four decimal places. Outside that rule, four decimal places is a sensible default for most pairs, and the rate should always say which direction it runs, such as 1 USD = 5.3730 BRL.\"\n  - q: \"What should happen when a quote expires on screen?\"\n    a: \"Disable the confirm button the moment the countdown hits zero, explain that rates move, and offer a one-click new quote. Show the refreshed numbers and make the user confirm again. Silently replacing an expired quote with a new rate at the moment of confirmation is the fastest way to lose trust.\"\n  - q: \"Should a quote screen show the mid-market rate?\"\n    a: \"It helps. Showing the market rate next to your rate lets users see the margin, and EU rules already push card currency conversion toward a percentage markup over the ECB reference rate. At BlindPay, every quote returns commercial_quotation and blindpay_quotation, so you can display both without a separate data feed.\"\n---\n\nA cross-border quote screen should show six things before the user confirms: amount sent, every fee, the exchange rate, the amount the recipient gets, when the quote expires, and when the money arrives. US consumer remittances must show most of these by law. BlindPay quotes return each figure as a field, with a 5-minute expiry, so the screen can render straight from the response.\n\nMost quote screens fail in the same three places. They hide the margin in the rate, they let an expired rate through, and they promise \"instant\" for a rail that takes days.\n\n**Key takeaways**\n\n- Show amount sent, fees, total, rate, amount received, expiry, and delivery estimate. Leave nothing for the user to compute.\n- US consumer remittances fall under the CFPB Remittance Transfer Rule: pre-payment disclosure, receipt, 30-minute cancellation, and error resolution.\n- The EU requires online credit transfers with currency conversion to show estimated conversion charges and the estimated total before the payment starts.\n- Drive the countdown from the quote's expiry, disable confirm at zero, and requote visibly.\n- Delivery estimates depend on the rail. Pix and SPEI land in minutes; ACH, SEPA, and SWIFT take business days.\n\n## What should a cross-border quote screen show?\n\nIt should show every number the user needs to judge the payment, taken from one firm quote, so the user never has to calculate anything. Here is the full list and where each line comes from in a BlindPay payout quote ([payout quotes](\u002Fdocs\u002Fpayout-quotes)).\n\n| Line on screen | Why it matters | BlindPay quote field |\n| --- | --- | --- |\n| You send | The amount debited or funded | `sender_amount` (minor units) |\n| Fees, itemized | Separates your fees from provider fees | `flat_fee`, `partner_fee_amount`, `billing_fee_amount` |\n| Total charged | What actually leaves the user's balance | Derived from the amounts above and `cover_fees` |\n| Exchange rate, with direction | Shows the price of the currency | `blindpay_quotation` |\n| Market rate (optional) | Makes the margin visible | `commercial_quotation` |\n| Recipient gets | The number the recipient checks | `receiver_amount` (minor units) |\n| Quote expires in | Tells the user the numbers are firm, but not forever | `expires_at` (epoch milliseconds) |\n| Estimated arrival | Sets expectations per rail | From the rail; see [cut-off times](\u002Fdocs\u002Fkb\u002Fcut-off-times) |\n| Recipient | Name and masked account, so the user can spot a mistake | From the saved bank account |\n\nTwo formatting rules. Amounts come back as integers in minor units, so divide by 100 for USD, BRL, and MXN before display. And write the rate with its direction, such as \"1 USD = 5.3730 BRL\", because a bare \"5.373\" means nothing to someone comparing two apps.\n\n[Stablecoin API quotes explained](\u002Fresources\u002Fmore\u002Fstablecoin-api-quotes-explained) covers the API side of these fields: what a quote locks, fee direction, and minor units. This page is about what the user sees.\n\n## What does the CFPB Remittance Transfer Rule require?\n\nFor consumer remittances sent from the US, the CFPB's Remittance Transfer Rule (Regulation E, subpart B, 12 CFR 1005.30 to 1005.36) requires a disclosure before payment, a receipt after it, a 30-minute cancellation right, and an error resolution process.\n\n**Who it covers.** A remittance transfer is an electronic transfer requested by a consumer to a recipient abroad, excluding transfers of $15 or less. The sender must be a consumer acting mainly for personal, family, or household purposes, so business-purpose payments generally fall outside it. A provider that made 500 or fewer remittance transfers in the previous calendar year and makes 500 or fewer in the current one is not treated as providing them in the normal course of business ([12 CFR 1005.30](https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F12\u002F1005.30)).\n\n**Pre-payment disclosure.** Before the sender pays, [12 CFR 1005.31](https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F12\u002F1005.31) requires:\n\n1. The transfer amount, in the currency the sender funds it with.\n2. Fees and taxes the provider charges.\n3. The total, the sum of the two.\n4. The exchange rate, rounded consistently to between two and four decimal places.\n5. Covered third-party fees, and the amount in the recipient's currency.\n6. The total to recipient, in the recipient's currency.\n7. A statement that fees or taxes charged by others may reduce what the recipient gets, where they may apply.\n\n**Receipt.** Everything above, plus the date funds will be available, the recipient's name, a statement of error and cancellation rights, and contact details for the provider, the state regulator, and the CFPB.\n\n**Cancellation.** The sender can cancel if the request arrives no later than 30 minutes after payment and the funds haven't been picked up or deposited. The provider refunds the full amount, fees included, within three business days ([12 CFR 1005.34](https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F12\u002F1005.34)).\n\n**Errors.** The sender has 180 days after the disclosed availability date to report an error, such as a wrong amount or funds that arrive late. The provider has 90 days to investigate ([12 CFR 1005.33](https:\u002F\u002Fwww.law.cornell.edu\u002Fcfr\u002Ftext\u002F12\u002F1005.33)).\n\nWhat this means for the screen: if you serve US consumers, the 30-minute window and the \"date available\" line belong in your product spec from day one. Adding them later means redesigning confirmation and receipt flows.\n\nThis is for information only and is not legal advice. Whether your product is a remittance transfer provider depends on your facts.\n\n## What do EU rules require on a quote screen?\n\nFor online credit transfers that include a currency conversion, EU rules require the payer's provider to show the estimated conversion charges and the estimated total amount before the payment starts.\n\nThe requirement is Article 3b of Regulation (EC) No 924\u002F2009, inserted by [Regulation (EU) 2019\u002F518](https:\u002F\u002Feur-lex.europa.eu\u002Flegal-content\u002FEN\u002FTXT\u002FHTML\u002F?uri=CELEX:32019R0518) and applied from 19 April 2020. The information has to be \"clear, neutral and comprehensible\". For card-based payments, the same regulation goes further and expresses conversion charges as a percentage markup over the latest [ECB euro reference rates](https:\u002F\u002Fwww.ecb.europa.eu\u002Fstats\u002Fpolicy_and_exchange_rates\u002Feuro_reference_exchange_rates\u002Fhtml\u002Findex.en.html).\n\nEven outside the EU, that percentage-over-reference format is a good pattern. Users understand \"0.5% above the market rate\" faster than two rates with four decimals each. [How to calculate FX spread](\u002Fresources\u002Fmore\u002Fhow-to-calculate-fx-spread) shows how to compute that number from a quote.\n\n## How should the screen handle who pays the fee?\n\nDecide which side of the payment is fixed, then show fees in a way that matches it. Two choices drive this: which amount the user types, and who absorbs the fees.\n\n**Which amount is fixed.** A business paying a supplier invoice usually knows the amount the supplier must receive. A user sending money home usually knows how much they want to spend. Offer both modes. In BlindPay quotes, `currency_type: \"sender\"` fixes the stablecoin amount sent, and `currency_type: \"receiver\"` fixes the fiat amount the bank account receives.\n\n**Who pays fees.** With `cover_fees: false`, fees are deducted from the fiat the recipient receives. With `cover_fees: true`, they are added on top of the amount sent, so the recipient gets the full figure. On screen:\n\n| Mode | User types | Fees appear as | Recipient sees |\n| --- | --- | --- | --- |\n| Fixed receive, sender covers fees | R$10,000 to receive | Added to the amount sent | Exactly R$10,000 |\n| Fixed send, recipient absorbs fees | $2,000 to send | Deducted before conversion | Less than $2,000 x rate |\n\nFor invoices, fixed receive with the sender covering fees is almost always right. A supplier who gets R$9,940 against a R$10,000 invoice will chase the gap, and your user pays for the follow-up. [Hidden fees in international wires](\u002Fresources\u002Fmore\u002Fhidden-fees-international-wires-our-sha-ben) explains why the same problem shows up with SWIFT SHA and BEN charges.\n\n## How should you handle quote expiry in the UI?\n\nRun a visible countdown from the quote's expiry time, block confirmation when it reaches zero, and fetch a new quote that the user must confirm again. Never let an expired price through.\n\nBlindPay payout and payin quotes expire after 5 minutes by default, and some rails can return less, such as SEPA payout quotes. `expires_at` is in epoch milliseconds, so compare it to `Date.now()` directly. Read it from every response instead of hardcoding 5 minutes.\n\nA pattern that works:\n\n1. **Start the timer from `expires_at`,** not from when the screen rendered. Network latency eats seconds.\n2. **Leave a buffer.** Stop accepting confirmation a few seconds before expiry so the execute call lands while the quote is still valid.\n3. **Disable, then explain.** \"This rate expired. Rates change every few seconds. Get a new quote?\"\n4. **Show the new numbers.** If the rate moved, show what changed before the user confirms again.\n5. **Requote on return.** If the user leaves the tab and comes back, check expiry immediately.\n\nShort expiries are a feature. A provider that locks a rate for an hour has priced an hour of market risk into that rate. [Stablecoin FX slippage](\u002Fresources\u002Fmore\u002Fstablecoin-fx-slippage-live-quotes) explains the trade-off.\n\n## What delivery estimate should the screen show?\n\nShow an estimate per rail, adjusted for cut-offs and weekends, and never \"instant\" for a rail that runs on business days. The rail is the biggest driver of arrival time.\n\n| Rail | Typical BlindPay payout timing |\n| --- | --- |\n| Pix (Brazil), SPEI (Mexico), Transfers 3.0 (Argentina) | Minutes; Pix and SPEI run 24\u002F7 |\n| RTP (US) | Instant |\n| ACH, wire (US) | ACH about 2 business days; wire about 1 business day |\n| TED (Brazil), ACH Colombia, SEPA | About 1 business day |\n| SWIFT (POBO\u002FCOBO) | About 5 business days, after compliance documents are approved |\n\nSource: [bank accounts](\u002Fdocs\u002Fbank-accounts), [payment methods](\u002Fdocs\u002Fkb\u002Fpayment-methods), and [cut-off times](\u002Fdocs\u002Fkb\u002Fcut-off-times). High volume can stretch any estimate, and payouts can be held for compliance review, so phrase it as \"usually arrives by\" rather than a promise. [Do stablecoin payouts work on weekends?](\u002Fresources\u002Fmore\u002Fstablecoin-payout-cut-off-times-weekends-holidays) covers the calendar side.\n\n## What should the receipt and status screen show?\n\nThe receipt should repeat the exact quote figures, add a payment reference and status, and tell the user how to get help. It is the screen users come back to when something looks wrong.\n\n- **The same numbers as the quote.** Amount sent, fees, rate, amount received. If they differ, you have a bug.\n- **Status in plain words.** BlindPay payouts move through `processing`, `on_hold`, `completed`, `failed`, or `refunded`. Map each to a sentence. [Stablecoin payout statuses explained](\u002Fresources\u002Fmore\u002Fstablecoin-payout-statuses-explained) has suggested wording.\n- **A reference the recipient's bank understands.** For SWIFT payouts, show the UETR once it is populated; every bank in the chain uses it. BlindPay sends SWIFT payments on behalf of the customer (POBO\u002FCOBO) with UETR tracking and MT103 confirmations ([POBO and COBO](\u002Fdocs\u002Fkb\u002Fpobo-cobo)).\n- **A help path.** For US consumer remittances, the receipt must include error and cancellation rights and contact details.\n\n## How does BlindPay help you build the quote screen?\n\nEvery line on the screen maps to a field in one BlindPay quote, so the UI renders from a single response and executes against the same quote ID.\n\n- **One quote, every figure.** `sender_amount`, `receiver_amount`, `commercial_quotation`, `blindpay_quotation`, `flat_fee`, `partner_fee_amount`, and `expires_at` in one response.\n- **Both fee modes.** `cover_fees` and `currency_type` support fixed-send and fixed-receive screens without extra math on your side.\n- **Your margin, itemized.** A [partner fee](\u002Fdocs\u002Flearn\u002Fpartner-fees) adds your markup to the quote as its own line, so you can show it separately from BlindPay's fee.\n- **Rails behind one call.** Pix, SPEI, ACH, RTP, SEPA, Transfers 3.0, ACH Colombia, and SWIFT (POBO\u002FCOBO), funded from stablecoins at send time with no pre-funding.\n\nThe disclosure duties themselves sit with whoever is the provider to the end user. BlindPay gives you the numbers; your product decides how to present them and which rules apply.\n\n## What to do next\n\nSketch your quote screen against the table at the top of this page and mark any line you can't fill from a single quote. Then create a test quote from the [payout quickstart](\u002Fdocs\u002Fquickstart-payout) and render it: amount sent, fees, rate with direction, amount received, and a countdown from `expires_at`. For the bigger picture, read [what real-time cross-border settlement is](\u002Fresources\u002Fmore\u002Fwhat-is-real-time-cross-border-settlement).\n",{"title":5,"description":726},"Cross-border quote screen: rate, fees, expiry, disclosure","resources\u002Fmore\u002Fcross-border-quote-screen-fee-disclosure","cLU92kjMNt50ZnAQIchUhLVWP_RUydkLH6HBfiN6WzU",[776,780,784,788,792,796,800,804,808,812,816,820,824,828,832,836,839,842,846,850,854,858,862,866,870,874,878,881,885,889,893,897,901,905,909,913,917,921,925,929,933,934,938,942,946,950,954,958,962,966,970,974,978,982,986,990,994,998,1002,1006,1009,1013,1017,1020,1024,1028,1032,1036,1039,1043,1047,1051,1055,1059,1063,1067,1071,1075,1079,1083,1087,1091,1095,1099,1103,1107,1111,1115,1119,1123,1127,1131,1135,1139,1142,1146,1150,1154,1158,1162,1166],{"path":777,"title":778,"description":779},"\u002Fresources\u002Fmore\u002Fblockchain-payment-use-cases","7 real-world blockchain payment use cases: payroll, remittances, B2B, and more","Seven places blockchain payments beat bank rails: contractor payroll, remittances, B2B suppliers, marketplaces, 24\u002F7 treasury, bill pay, and PSP payouts.",{"path":781,"title":782,"description":783},"\u002Fresources\u002Fmore\u002Fagent-payment-protocols-compared","AP2 vs ACP vs x402: agent payment protocols compared","AP2, ACP, and x402 each verify that an AI agent had permission to spend. Here is what every protocol covers, who backs it, and the reconciliation gap none of them close.",{"path":785,"title":786,"description":787},"\u002Fresources\u002Fmore\u002Fbest-real-time-cross-border-settlement-providers-2026","Best real-time cross-border settlement providers for fintechs in 2026: low fees compared","A 10-point checklist and a side-by-side of BlindPay, Wise Platform, Airwallex, Thunes, Bridge, and Circle for real-time, low-fee cross-border settlement.",{"path":789,"title":790,"description":791},"\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-platform-fintech-2026","Best stablecoin payment platforms for fintech in 2026: a US comparison","Seven stablecoin payment platforms compared for US fintechs in 2026: what makes an API production-ready, how each provider handles compliance, settlement speed against ACH, and how to run the evaluation.",{"path":793,"title":794,"description":795},"\u002Fresources\u002Fmore\u002Fbest-stablecoin-payment-providers-2026","Best stablecoin payment providers in 2026: how to choose","How to choose a stablecoin payment provider in 2026: the four provider types, a comparison of 10 options, and the questions that decide the fit.",{"path":797,"title":798,"description":799},"\u002Fresources\u002Fmore\u002Fwhat-are-blockchain-payments","Blockchain payments explained: how stablecoins move money without correspondent banks","Blockchain payments move a stablecoin on a public ledger instead of messages between banks. How they work, what they cost, and how they compare with SWIFT.",{"path":801,"title":802,"description":803},"\u002Fresources\u002Fmore\u002Fblockchain-payments-glossary","Blockchain payments glossary: 34 terms explained in plain English","Stablecoin, on-ramp, off-ramp, finality, gas, non-custodial, travel rule. The 34 terms of blockchain payments, each defined in one or two lines.",{"path":805,"title":806,"description":807},"\u002Fresources\u002Fmore\u002Fbuild-vs-buy-stablecoin-payments","Build vs buy: should you build stablecoin payouts in-house or use an API?","Building stablecoin payouts in-house means wallets, liquidity, banking partners, licenses, and a compliance program. When building makes sense.",{"path":809,"title":810,"description":811},"\u002Fresources\u002Fmore\u002Fcan-a-virtual-account-replace-a-bank-account","Can a virtual account replace a business bank account? What each one does for cross-border companies","Usually not. A virtual account collects and settles payments; a bank account runs payroll, taxes, and credit. A job-by-job guide for cross-border teams.",{"path":813,"title":814,"description":815},"\u002Fresources\u002Fmore\u002Flatam-payout-liquidity-partner-pix-spei","Choosing a liquidity partner for LatAm payouts: Pix, SPEI, and beyond","How to choose a liquidity partner for payouts into Latin America: how Pix and SPEI work, how a stablecoin liquidity layer replaces local bank accounts, and a checklist for coverage, pricing, and compliance.",{"path":817,"title":818,"description":819},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-mistakes","Common stablecoin payout mistakes: wrong network, expired quotes, and bad bank details","The mistakes that make stablecoin payouts fail or stall: wrong network or token, expired quotes, deposits below minimums, bad bank details, and cut-offs.",{"path":821,"title":822,"description":823},"\u002Fresources\u002Fmore\u002Fcorrespondent-banking-vs-stablecoin-liquidity","Correspondent banking vs stablecoin liquidity: why pre-funding traps your capital","Correspondent banking keeps cross-border payouts liquid by parking cash in nostro accounts in every country. What that trapped capital costs a treasury team, and what stablecoin liquidity changes.",{"path":825,"title":826,"description":827},"\u002Fresources\u002Fmore\u002Fcrypto-payment-processor-for-businesses","Crypto payment processor for businesses: what to compare before you choose","Compare crypto payment processors on six criteria: settlement speed, stablecoins, compliance, dev effort, payout coverage, and pricing. Scorecard inside.",{"path":829,"title":830,"description":831},"\u002Fresources\u002Fmore\u002Fcustodial-vs-non-custodial-off-ramps","Custodial vs non-custodial off-ramps: who holds the money, and what happens if the provider fails","A custodial off-ramp holds your stablecoins; a non-custodial one pulls them only at payout. What changes in insolvency, de-banking, and failed payouts.",{"path":833,"title":834,"description":835},"\u002Fresources\u002Fmore\u002Fcustodial-vs-non-custodial-vs-mpc-wallets","Custodial vs non-custodial vs MPC wallets: how to choose","Custodial, non-custodial, and MPC wallets differ in who holds the keys. Compare control, recovery, risk, and regulation, with product examples for each.",{"path":568,"title":837,"description":838},"Do stablecoin payouts work on weekends and holidays? Cut-offs and bank calendars by rail","The stablecoin leg runs 24\u002F7, and so do Pix, SPEI, and RTP. ACH, wire, SEPA, TED, and SWIFT wait for a business day. Cut-offs and calendars by rail.",{"path":424,"title":840,"description":841},"Hidden fees in international wires: OUR, SHA, BEN, and a 7-point quote audit","Why suppliers get short-paid on international wires: SWIFT charge codes, intermediary deductions, and FX markups. Plus a 7-step audit for any quote.",{"path":843,"title":844,"description":845},"\u002Fresources\u002Fmore\u002Fpay-suppliers-brazil-mexico-from-us-bank-account","How a US company pays suppliers in Brazil and Mexico from a US bank account","Three ways to pay suppliers in Brazil and Mexico from dollars in a US bank account: an international wire, a fintech transfer, or USD to Pix or SPEI.",{"path":847,"title":848,"description":849},"\u002Fresources\u002Fmore\u002Fstablecoin-cross-border-payments-savings","How businesses use stablecoins for cross-border payments (and where the savings come from)","Correspondent hops, FX markup, and pre-funding: what stablecoin settlement does to each cost of a cross-border payment, with a $50,000 example to Brazil.",{"path":851,"title":852,"description":853},"\u002Fresources\u002Fmore\u002Fhow-a-stablecoin-payment-works","How does a stablecoin payment move? From bank deposit to local payout, step by step","A stablecoin payment moves in legs: fiat collected, stablecoin settled, fiat paid out. What happens at each step, where delays hide, what recipients see.",{"path":855,"title":856,"description":857},"\u002Fresources\u002Fmore\u002Fcross-border-merchant-payments-without-pre-funding","How global merchants get paid across borders with stablecoins, no pre-funding required","Pre-funding means parking local currency in every market before money moves. Stablecoin virtual accounts remove it. A worked example across 4 countries.",{"path":859,"title":860,"description":861},"\u002Fresources\u002Fmore\u002Fstablecoin-payout-settlement-times","How long does a stablecoin payout take? Settlement times by country and rail","Stablecoin payouts settle in minutes on Pix, SPEI, RTP, and Transfers 3.0, and in 1 to 5 business days on ACH, SEPA, and SWIFT. Full table by rail.",{"path":863,"title":864,"description":865},"\u002Fresources\u002Fmore\u002Fcross-border-payment-costs-2026","How much do cross-border payments cost in 2026? Fees by corridor and what counts as cheap","Sending $200 abroad costs 6.36% on average, per the World Bank. Here is where that money goes, how corridors differ, and what a cheap payment looks like.",{"path":867,"title":868,"description":869},"\u002Fresources\u002Fmore\u002Fcrypto-on-ramp-fees-explained","How much does a crypto on-ramp cost? Fees, spreads, and how to read a quote","A crypto on-ramp charges through the rate spread, a service fee, the payment rail, and sometimes the network. How each works, and how to read the quote.",{"path":871,"title":872,"description":873},"\u002Fresources\u002Fmore\u002Fstablecoin-off-ramp-fees-explained","How much does a stablecoin off-ramp cost? Fees per transaction vs a bank wire","What a stablecoin off-ramp costs per transaction: network fee, FX spread, percentage and flat fees, worked at $200, $2,000, and $20,000 vs a bank wire.",{"path":875,"title":876,"description":877},"\u002Fresources\u002Fmore\u002Fhow-to-add-stablecoin-payments-to-your-wallet-integration","How to add stablecoin payments to your wallet integration","Connect the wallets you already run to bank deposits and local payouts: register addresses, open virtual accounts, quote, authorize, and track webhooks.",{"path":333,"title":879,"description":880},"How to calculate FX spread on an international payment (with worked examples)","FX spread % = (mid rate - offered rate) \u002F mid rate x 100. Here is how to get the mid rate, fix the quote direction, and price the spread in dollars.",{"path":882,"title":883,"description":884},"\u002Fresources\u002Fmore\u002Fhow-to-choose-a-virtual-account-provider","How to choose a virtual account provider: a 12-point checklist for developers and finance teams","Twelve criteria for evaluating a virtual account API, from rails and naming to custody, webhooks, and pricing, plus red flags and a scorecard to copy.",{"path":886,"title":887,"description":888},"\u002Fresources\u002Fmore\u002Fhow-to-choose-on-off-ramp-provider","How to choose the best on\u002Foff ramp provider for your fintech app","Six criteria for evaluating a crypto on\u002Foff ramp provider: corridor coverage, live quotes, fiat settlement speed, licensing, API quality, and liquidity depth. Each with concrete tests to run, a comparison table, and a scoring framework.",{"path":890,"title":891,"description":892},"\u002Fresources\u002Fmore\u002Fhow-to-evaluate-payment-orchestration-platform","How to evaluate a payment orchestration platform for cross-border payments","Six criteria that decide whether an orchestration platform works for cross-border money: rail coverage, compliance per corridor, developer experience, settlement speed, FX transparency, and pricing.",{"path":894,"title":895,"description":896},"\u002Fresources\u002Fmore\u002Fstablecoin-api-30-day-evaluation-plan","How to evaluate a stablecoin API in 30 days: a week-by-week plan","A 30-day plan to evaluate a stablecoin API: shortlist, sandbox tests, compliance review, and a live pilot, plus where costs hide and a worked cost model.",{"path":898,"title":899,"description":900},"\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-crypto-on-ramp-api","How to integrate a crypto on-ramp API: payin quotes, deposit instructions, and webhooks","The on-ramp API flow step by step: verify the customer, pick the wallet, quote, create the payin, show deposit instructions, and handle webhooks.",{"path":902,"title":903,"description":904},"\u002Fresources\u002Fmore\u002Fhow-to-issue-stablecoin-cards-api","How to issue stablecoin-funded cards through an API: a developer's guide","Build vs. buy for stablecoin card issuing, the objects a card issuing API must expose, a step-by-step integration flow, and where KYC and KYB sit in it.",{"path":906,"title":907,"description":908},"\u002Fresources\u002Fmore\u002Fhow-to-off-ramp-usdc-to-us-bank-account","How to off-ramp USDC to a US bank account: ACH, RTP, or wire","Cashing out USDC or USDT to a US bank account: when ACH, Same Day ACH, RTP, and wire pay out, the cut-offs in ET, the fields you need, and what delays it.",{"path":910,"title":911,"description":912},"\u002Fresources\u002Fmore\u002Fhow-to-off-ramp-usdc-to-euros-sepa","How to off-ramp USDC to euros over SEPA: networks, IBAN details, and timing","Converting USDC to EUR in a SEPA bank account: which networks work, the IBAN details you need, SEPA vs SEPA Instant timing, limits, and what MiCA changes.",{"path":914,"title":915,"description":916},"\u002Fresources\u002Fmore\u002Fhow-to-off-ramp-usdt-latin-america","How to off-ramp USDT to local currency in Latin America","Converting USDT to BRL, MXN, ARS, or COP: which networks work, the payout rail in each country, weekend timing, fees, and the documents a business needs.",{"path":918,"title":919,"description":920},"\u002Fresources\u002Fmore\u002Fhow-to-on-ramp-local-currency-latin-america","How to on-ramp BRL, MXN, ARS, and COP into stablecoins: Pix, SPEI, Transfers 3.0, and PSE","How Latin American bank payments become USDC or USDT: what each rail shows the payer, the payer data it needs, how fast it lands, and the traps by country.",{"path":922,"title":923,"description":924},"\u002Fresources\u002Fmore\u002Fhow-to-pay-invoices-with-stablecoins-api","How to pay invoices, boletos, and Pix codes with stablecoins through an API","Register the bill, quote it, pay it from USDC or USDT, and track two webhook streams. A developer guide to stablecoin bill pay, boleto gotchas included.",{"path":926,"title":927,"description":928},"\u002Fresources\u002Fmore\u002Fhow-to-send-usdc-to-bank-account-brazil","How to send USDC to a bank account in Brazil","Step-by-step: convert USDC to Brazilian reais and deliver them to a bank account over Pix using a stablecoin payout API. Quote, verify, send, settle in minutes.",{"path":930,"title":931,"description":932},"\u002Fresources\u002Fmore\u002Fhow-to-send-usdc-to-bank-account-mexico","How to send USDC to a bank account in Mexico: a step-by-step guide over SPEI","Send USDC to a Mexican bank account: verify the recipient, quote in pesos, fund from a wallet, and confirm on SPEI. Recipient data, statuses, and failures.",{"path":769,"title":5,"description":726},{"path":935,"title":936,"description":937},"\u002Fresources\u002Fmore\u002Fhow-to-test-virtual-accounts-sandbox","How to test a virtual accounts API integration before going live","The integration sequence for a virtual accounts API, what a sandbox simulates and what it can't, and a test plan with the statuses and webhooks to expect.",{"path":939,"title":940,"description":941},"\u002Fresources\u002Fmore\u002Fvirtual-account-reconciliation","How virtual accounts automate payment reconciliation (with a worked example)","Virtual accounts match each deposit to a customer by account number, not a free-text reference. A worked example with partial payments and micro-deposits.",{"path":943,"title":944,"description":945},"\u002Fresources\u002Fmore\u002Fstablecoin-api-idempotency-keys","Idempotency keys in a stablecoin API: how to never send the same payout twice","A timeout on a payout call is the most common way to pay someone twice. How idempotency keys prevent it, what replays, what conflicts, and how to retry.",{"path":947,"title":948,"description":949},"\u002Fresources\u002Fmore\u002Fhow-to-integrate-a-stablecoin-api","Integrating a stablecoin API: a developer's guide to cross-border payments with BlindPay","Step-by-step integration of a stablecoin API: authenticate, onboard a customer, create a virtual USD account, quote and send a cross-border payout, and handle signed webhooks. Endpoints, statuses, and SDKs for BlindPay.",{"path":951,"title":952,"description":953},"\u002Fresources\u002Fmore\u002Fliquidity-risk-global-payouts","Managing liquidity risk in global payouts: a practical guide for fintechs and PSPs","Liquidity risk in payouts is the chance funds aren't available at the right rate, in the right currency, when a payout settles. Its four sources and a six-step framework to manage them.",{"path":955,"title":956,"description":957},"\u002Fresources\u002Fmore\u002Fmarketplace-stablecoin-payouts-latam","Marketplace payouts in Latin America: stablecoin rails for sellers in Brazil, Mexico, Colombia, and Argentina","How marketplaces pay sellers, creators, and vendors across Latin America with stablecoin settlement: supported rails (Pix, SPEI, PSE, Argentine transfers), the end-to-end payout workflow, API integration, and what changes for speed, minimums, and FX cost.",{"path":959,"title":960,"description":961},"\u002Fresources\u002Fmore\u002Fnon-custodial-payments-explained","Non-custodial payments: what they are and why they reduce risk for businesses","A non-custodial payment provider moves your money without holding it between payments. Who controls the funds, who carries the risk, and what to ask.",{"path":963,"title":964,"description":965},"\u002Fresources\u002Fmore\u002Fon-ramp-widget-vs-api","On-ramp widget vs API: which integration fits your product?","Hosted on-ramp widget or API-first ramp? Compare who owns the UX, KYC, quotes, webhooks, branding, and compliance, plus a decision table and checklist.",{"path":967,"title":968,"description":969},"\u002Fresources\u002Fmore\u002Fon-ramp-or-off-ramp-which-does-your-product-need","On-ramp, off-ramp, or both? How to tell which stablecoin API your product needs","Match your use case to the direction money moves: on-ramp, off-ramp, or both. Covers payroll, remittance, marketplaces, treasury, and 10 questions to ask.",{"path":971,"title":972,"description":973},"\u002Fresources\u002Fmore\u002Fon-off-ramp-liquidity-live-quotes","On\u002Foff ramp liquidity with live quotes: how it works and why it matters","What on\u002Foff ramp liquidity with live quotes means for developers: live quote vs batch rate, the quote ID flow in an API, what happens on expiry, how liquidity depth changes spread by transaction size, rate windows and UX, and a checklist for evaluating a live quote API.",{"path":975,"title":976,"description":977},"\u002Fresources\u002Fmore\u002Fonchain-settlement-vs-bank-settlement","Onchain settlement vs bank settlement: RTGS, ACH, cards, and blockchain finality compared","How onchain settlement compares with Fedwire, Pix, ACH, and card settlement: settlement asset, hours, finality, reversibility, and where payout risk sits.",{"path":979,"title":980,"description":981},"\u002Fresources\u002Fmore\u002Fswift-pobo-vs-cobo-explained","POBO vs COBO: SWIFT payments and collections on behalf of, explained","POBO sends a SWIFT payment for a customer, COBO collects one for them. Whose name shows, how UETR tracking works, and where stablecoin settlement fits.",{"path":983,"title":984,"description":985},"\u002Fresources\u002Fmore\u002Fpayment-orchestration-vs-payment-gateway","Payment orchestration vs payment gateway: what's the difference?","A gateway connects you to one processor. An orchestration platform connects to many rails and picks the best path per transaction. The table, the triggers, and a worked USD to BRL example.",{"path":987,"title":988,"description":989},"\u002Fresources\u002Fmore\u002Fpix-vs-spei","Pix vs SPEI: how Brazil's and Mexico's instant payment rails compare","Pix vs SPEI side by side: who runs each rail, how recipients are identified, hours, settlement, returns, and proof of payment for stablecoin payouts.",{"path":991,"title":992,"description":993},"\u002Fresources\u002Fmore\u002Fstablecoin-api-rfp-template","Stablecoin API RFP template: sections, scoring, and a vendor scorecard","How to write an RFP for a stablecoin API: the eight sections to include, pass or fail gates, 1 to 3 weighted scoring, a copyable scorecard, and a timeline.",{"path":995,"title":996,"description":997},"\u002Fresources\u002Fmore\u002Fstablecoin-api-openapi-sdks","Stablecoin API SDKs: how one OpenAPI spec keeps five languages in sync","BlindPay's stablecoin API is described by one OpenAPI 3.1 spec that drives validation, docs, SDKs for Node, Python, Go, PHP, and Swift, and the MCP server.",{"path":999,"title":1000,"description":1001},"\u002Fresources\u002Fmore\u002Fstablecoin-api-sla-settlement-finality","Stablecoin API SLAs and settlement finality explained","Stablecoin API uptime numbers cluster near 99.9% for a reason: most providers measure API acceptance instead of the point where money becomes final and spendable.",{"path":1003,"title":1004,"description":1005},"\u002Fresources\u002Fmore\u002Fstablecoin-api-objects-explained","Stablecoin API objects explained: customers, bank accounts, wallets, quotes, payouts, and webhooks","The core objects behind a stablecoin API, how they relate, which IDs to store in your ledger, and 8 data-model mistakes that break payout integrations.",{"path":214,"title":1007,"description":1008},"Stablecoin API quotes explained: expiry, fee direction, and minor units","A stablecoin API quote locks the rate, fees, and amounts for a few minutes. How expiry works, which side pays the fee, and the field that flips meaning.",{"path":1010,"title":1011,"description":1012},"\u002Fresources\u002Fmore\u002Fstablecoin-api-sandbox-vs-production","Stablecoin API sandbox vs production: what testing misses","Most stablecoin API sandboxes pass every integration test and still leave a team unprepared for production, because webhook delivery and idempotent retries are exactly what sandboxes fake or skip.",{"path":1014,"title":1015,"description":1016},"\u002Fresources\u002Fmore\u002Fstablecoin-api-webhooks-reconciliation","Stablecoin API webhooks: signature checks, duplicate events, and reconciliation","How to handle stablecoin API webhooks in production: verify signatures on raw bytes, dedupe retries, never regress a final status, reconcile daily.",{"path":487,"title":1018,"description":1019},"Stablecoin FX slippage: how live quotes turn the quoted rate into the rate you get","FX slippage is the gap between the rate a stablecoin on-ramp or off-ramp shows and the rate that settles. Why quote freshness is a liquidity signal, and how to check a quote-then-execute flow.",{"path":1021,"title":1022,"description":1023},"\u002Fresources\u002Fmore\u002Fstablecoin-cards-latin-america","Stablecoin cards in Latin America: how they work in Brazil, Mexico, Argentina, and Colombia","How USD stablecoin cards work in Brazil, Mexico, Argentina, and Colombia: local card and crypto rules, costs at the point of sale, and when a Pix or SPEI payout fits better.",{"path":1025,"title":1026,"description":1027},"\u002Fresources\u002Fmore\u002Fstablecoin-liquidity-provider-vs-fx-desk","Stablecoin liquidity providers vs traditional FX desks: what finance teams should know","A bank FX desk prices cross-border payouts by relationship. A stablecoin liquidity provider prices them by API. How the two compare on cost, speed, minimums, coverage, and compliance.",{"path":1029,"title":1030,"description":1031},"\u002Fresources\u002Fmore\u002Fstablecoin-payment-fees-vs-card-processing-fees","Stablecoin payment fees vs credit card processing fees: what merchants actually pay","Cards cost merchants 1.5% to 3.5% plus cross-border, FX, and chargeback fees. Stablecoin payments cost cents on-chain plus a sub-percent conversion spread.",{"path":1033,"title":1034,"description":1035},"\u002Fresources\u002Fmore\u002Fstablecoin-payments-guide","Stablecoin payments explained: a guide for businesses","Stablecoin payments move dollar-pegged tokens between parties and settle in minutes, 24\u002F7. How they work, what they cost, and how businesses accept and send them.",{"path":611,"title":1037,"description":1038},"Stablecoin payout statuses explained: processing, on hold, completed, failed, and refunded","What each stablecoin payout status means, which are final, why an on-chain confirmation isn't a completed payout, and how to test every failure.",{"path":1040,"title":1041,"description":1042},"\u002Fresources\u002Fmore\u002Fstablecoin-payroll-latam-contractors","Stablecoin payroll for LATAM contractors: how it actually works in 2026","How US companies pay contractors in Argentina, Brazil, Mexico, and Colombia with stablecoins in 2026: USDC vs USDT, the step-by-step payout flow, US tax reporting, a platform comparison, and how to start.",{"path":1044,"title":1045,"description":1046},"\u002Fresources\u002Fmore\u002Fstablecoin-settlement-for-merchants","Stablecoin settlement explained: how merchants get paid faster than card networks","Stablecoin payments settle in seconds to minutes, final and 24\u002F7. Cards take 1 to 3 business days and wires up to 5. How it works and how to cash out.",{"path":1048,"title":1049,"description":1050},"\u002Fresources\u002Fmore\u002Fstablecoin-virtual-accounts-explained","Stablecoin virtual accounts explained: from bank transfer to wallet balance","A stablecoin virtual account is a bank account in your customer's name whose deposits convert to USDC or USDT. How approval, deposits, and fees work.",{"path":1052,"title":1053,"description":1054},"\u002Fresources\u002Fmore\u002Fstablecoin-virtual-cards-cross-border-payouts","Stablecoin-funded virtual cards vs. traditional virtual cards for cross-border payouts","Stablecoin-funded vs. bank-funded virtual cards for paying contractors and vendors abroad: funding speed, pre-funding, FX cost, settlement finality, and a Brazil walkthrough.",{"path":1056,"title":1057,"description":1058},"\u002Fresources\u002Fmore\u002Fstablecoins-local-rails-latin-america","Stablecoins plus local rails: how cross-border payments actually land in Latin America","A stablecoin crosses the border in seconds, but the payment lands over Pix, SPEI, or another local rail. How that last mile works in Brazil and Mexico.",{"path":1060,"title":1061,"description":1062},"\u002Fresources\u002Fmore\u002Fstablecoin-vs-swift-b2b-payments","Stablecoins vs SWIFT for B2B cross-border payments: a real comparison","Where SWIFT wires still win, where stablecoin settlement wins, and how to compare the two on cost, speed, traceability, and failure modes for business payments in 2026.",{"path":1064,"title":1065,"description":1066},"\u002Fresources\u002Fmore\u002Fswift-instant-cross-border-scheme-vs-stablecoins","Swift's new payments scheme and blockchain ledger vs stablecoins: what changes in 2026","Swift launched a retail payments scheme in June 2026 and a blockchain ledger pilot in July. What each one changes, and how they compare with stablecoins.",{"path":1068,"title":1069,"description":1070},"\u002Fresources\u002Fmore\u002Fusdc-to-ars-routes-2026","USDC to ARS in 2026: routes, fees, and rules compared","Four ways to convert USDC to Argentine pesos in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with Transfers 3.0. Fees, speed, KYC, and Argentina's PSAV rules compared.",{"path":1072,"title":1073,"description":1074},"\u002Fresources\u002Fmore\u002Fusdc-to-brl-routes-2026","USDC to BRL in 2026: routes, fees, and rules compared","Four ways to convert USDC to Brazilian reais in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with Pix. Fees, speed, KYC, and Brazil's VASP rules compared.",{"path":1076,"title":1077,"description":1078},"\u002Fresources\u002Fmore\u002Fusdc-to-cop-routes-2026","USDC to COP in 2026: routes, fees, and rules compared","Four ways to convert USDC to Colombian pesos in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with PSE. Fees, speed, KYC, and Colombia's VASP rules compared.",{"path":1080,"title":1081,"description":1082},"\u002Fresources\u002Fmore\u002Fusdc-to-mxn-routes-2026","USDC to MXN in 2026: routes, fees, and rules compared","Four ways to convert USDC to Mexican pesos in 2026: stablecoin payout APIs, local exchanges, P2P, and global exchanges with SPEI. Fees, speed, KYC, and Mexico's rules compared.",{"path":1084,"title":1085,"description":1086},"\u002Fresources\u002Fmore\u002Fvirtual-account-deposit-not-received","Virtual account deposit not received? Why deposits get delayed, held, or returned","Why a virtual account deposit is late, on hold, or returned: arrival windows, payin statuses, RFIs, wrong rails, and how to trace a wire or SWIFT payment.",{"path":1088,"title":1089,"description":1090},"\u002Fresources\u002Fmore\u002Fvirtual-account-vs-virtual-iban","Virtual account vs virtual IBAN vs real bank account: what's the difference?","A real account holds funds for one holder. A virtual account routes deposits into a master account. A virtual IBAN is the IBAN version. When to use each.",{"path":1092,"title":1093,"description":1094},"\u002Fresources\u002Fmore\u002Fvirtual-account-vs-wallet-address-vs-payment-link","Virtual account vs wallet address vs payment link: how to collect in stablecoins","Three ways to collect money that ends in stablecoins: a virtual account, a deposit wallet address, or a payment link. Compare rails, refunds, KYC, and fit.",{"path":1096,"title":1097,"description":1098},"\u002Fresources\u002Fmore\u002Fvirtual-accounts-cross-border-payments","Virtual accounts for cross-border payments: use cases, payment rails, and costs","How virtual accounts let payers abroad pay a local-style account, which rails collect and pay out, what drives the cost, and five questions to ask.",{"path":1100,"title":1101,"description":1102},"\u002Fresources\u002Fmore\u002Fvirtual-account-vs-one-time-deposit-instructions","Virtual accounts vs one-time deposit instructions: how to collect bank transfers as stablecoins","One-time deposit instructions suit occasional payers and local rails. Virtual accounts suit repeat US payers. How each matches deposits and when to switch.",{"path":1104,"title":1105,"description":1106},"\u002Fresources\u002Fmore\u002Fnostro-vostro-accounts-explained","What are nostro and vostro accounts? And why they force pre-funding","A nostro account is a bank's account at a foreign bank, in that bank's currency. A vostro is the same account seen from the other side. Why both trap cash.",{"path":1108,"title":1109,"description":1110},"\u002Fresources\u002Fmore\u002Fpix-key-cpf-clabe-payout-details","What details do you need to pay someone in Brazil or Mexico? Pix keys, CPF, and CLABE","What a payout to Brazil or Mexico needs from the recipient: Pix key types, CPF and CNPJ formats, the 18-digit CLABE, and the checks that stop a bad payout.",{"path":1112,"title":1113,"description":1114},"\u002Fresources\u002Fmore\u002Fno-pre-funding-stablecoin-payouts","What does \"no pre-funding\" mean in a stablecoin API?","No pre-funding means each payout is funded when you send it, not from a balance parked in advance. The three funding models, the math, and what to ask.",{"path":1116,"title":1117,"description":1118},"\u002Fresources\u002Fmore\u002Fherstatt-risk-fx-settlement-risk","What is Herstatt risk? FX settlement risk, PvP, and what real-time settlement changes","Herstatt risk is paying your side of an FX trade and never getting the other. What happened in 1974, how PvP removes it, and where it remains.",{"path":1120,"title":1121,"description":1122},"\u002Fresources\u002Fmore\u002Fwhat-is-a-crypto-on-ramp-and-off-ramp","What is a crypto on-ramp and off-ramp? A guide for fintech builders","A crypto on-ramp converts fiat into stablecoins or crypto; an off-ramp converts them back into fiat in a bank account. How each works step by step, how they differ, which payment methods on-ramps support, and who they are built for.",{"path":1124,"title":1125,"description":1126},"\u002Fresources\u002Fmore\u002Fwhat-is-a-liquidity-market-cross-border-payments","What is a liquidity market in cross-border payments? And why stablecoin liquidity is changing it","A liquidity market in cross-border payments is where the currency to settle a transfer gets sourced. How correspondent banks pre-fund it, and how stablecoin liquidity changes the model.",{"path":1128,"title":1129,"description":1130},"\u002Fresources\u002Fmore\u002Fwhat-is-a-stablecoin-offramp","What is a stablecoin off-ramp? How crypto becomes cash","A stablecoin off-ramp converts stablecoins like USDC or USDT back into fiat currency in a bank account. How the conversion works and who regulates it.",{"path":1132,"title":1133,"description":1134},"\u002Fresources\u002Fmore\u002Fwhat-is-a-virtual-account","What is a virtual account? A plain-English guide for fintech teams","A virtual account is a unique set of bank details that routes incoming payments to one customer or purpose. How it works, who uses it, and where it fits.",{"path":1136,"title":1137,"description":1138},"\u002Fresources\u002Fmore\u002Fwhat-is-payment-orchestration","What is payment orchestration? The routing layer, explained","Payment orchestration is the routing layer between your app and every processor, bank, and rail you use. The five layers, how stablecoin settlement fits, and how it differs from a gateway.",{"path":709,"title":1140,"description":1141},"What is real-time cross-border settlement? A 2026 guide","Real-time cross-border settlement means the recipient can use the money minutes after you send it. Which rails do it, what it costs, and where it stops.",{"path":1143,"title":1144,"description":1145},"\u002Fresources\u002Fmore\u002Fstablecoin-payments-provider-due-diligence","What to ask a stablecoin payments provider: 30 due diligence questions","The questions to ask a stablecoin payments vendor before you sign: licensing, custody, pricing, rails, compliance, failure handling, security, and exit.",{"path":1147,"title":1148,"description":1149},"\u002Fresources\u002Fmore\u002Fwhen-not-to-use-blockchain-payments","When not to use blockchain payments: 7 cases where a bank rail wins","Blockchain payments beat wires on many corridors, not all of them. Seven cases where a domestic rail, a card, or a plain wire is still the better choice.",{"path":1151,"title":1152,"description":1153},"\u002Fresources\u002Fmore\u002Fhow-to-track-a-crypto-off-ramp-payout","Where is my off-ramp payout? How to track it rail by rail, and what to tell the recipient","Track an off-ramp payout from transaction hash to bank: the reference each rail gives you (Pix E2E ID, SPEI key, ACH trace, UETR) and status copy.",{"path":1155,"title":1156,"description":1157},"\u002Fresources\u002Fmore\u002Finstant-payment-systems-by-country","Which countries have instant payment systems? A 2026 reference table","Pix, SPEI, RTP, FedNow, SEPA Instant, Faster Payments, UPI, Bre-B, and more: who runs each instant payment system, when it launched, its hours, and limits.",{"path":1159,"title":1160,"description":1161},"\u002Fresources\u002Fmore\u002Fwho-pays-gas-fees-stablecoin-payments","Who pays gas fees in stablecoin payments?","Who pays network fees in each stablecoin payment flow, how gas works on Ethereum, Solana, Tron, Stellar, and Arc, and how to compare it across providers.",{"path":1163,"title":1164,"description":1165},"\u002Fresources\u002Fmore\u002Fwhy-are-cross-border-payments-slow","Why are cross-border payments slow? Where the days go in an international wire","Most SWIFT payments reach the destination bank within an hour. The days go to cut-offs, correspondent hops, compliance checks, and local crediting.",{"path":1167,"title":1168,"description":1169},"\u002Fresources\u002Fmore\u002Fwhy-crypto-on-ramp-deposits-fail","Why crypto on-ramp deposits fail: missing references, late transfers, holds, and refunds","Most failed on-ramps fail on the fiat side: a missing reference, the wrong payer, a late transfer, a hold. What happens to the money in each case.",1791570070057]