<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>platform &#8211; BLOG</title>
	<atom:link href="https://dev.jack.com/en/tag/platform/feed/" rel="self" type="application/rss+xml" />
	<link>https://dev.jack.com</link>
	<description>Casino, sports and crypto news, guides and platform updates.</description>
	<lastBuildDate>Mon, 03 Aug 2026 11:24:02 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://dev.jack.com/wp-content/uploads/2026/08/jack-site-icon-150x150.png</url>
	<title>platform &#8211; BLOG</title>
	<link>https://dev.jack.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Platform update: faster withdrawals rolling out</title>
		<link>https://dev.jack.com/en/platform-update-faster-withdrawals-rolling-out/</link>
		
		<dc:creator><![CDATA[Jack Editorial]]></dc:creator>
		<pubDate>Thu, 23 Jul 2026 10:26:14 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[payments]]></category>
		<category><![CDATA[platform]]></category>
		<category><![CDATA[withdrawals]]></category>
		<guid isPermaLink="false">https://dev.jack.com/platform-update-faster-withdrawals-rolling-out/</guid>

					<description><![CDATA[Payout processing moves to a new queue over the next two weeks, cutting the manual review step for most requests.]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">The change affects how withdrawal requests are queued and reviewed. Most requests will clear without a manual step; the ones that still get reviewed are the ones that always did.</p>



<h2 class="wp-block-heading">What changes</h2>



<ul class="wp-block-list"><li>Automated checks run at request time rather than in a nightly batch</li><li>Requests below the review threshold clear without human involvement</li><li>Status updates appear in the account history immediately</li><li>Network fees are shown before confirming, not after</li></ul>



<h2 class="wp-block-heading">What has not changed</h2>



<p class="wp-block-paragraph">Verification requirements are unchanged. An unverified account still needs to complete verification before the first withdrawal, and that remains the single most common source of delay.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">Most withdrawal delays are not processing delays. They are verification delays wearing a processing badge.</p>
</blockquote>



<h3 class="wp-block-heading">Blockchain confirmation is separate</h3>



<p class="wp-block-paragraph">Once a payout is sent, arrival depends on the network, not the platform. A congested chain adds time no queue change can remove.</p>



<h2 class="wp-block-heading">Rollout order</h2>



<ol class="wp-block-list"><li>Accounts already fully verified</li><li>Accounts with a withdrawal history on the same method</li><li>Remaining accounts as verification completes</li><li>New payment methods added last, once the queue is stable</li></ol>



<h2 class="wp-block-heading">The short version</h2>



<p class="wp-block-paragraph">Faster for most, unchanged for the cases that need review. If a payout is slow, check verification status first.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
