<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Novaza Pay on Novaza Docs</title><link>https://docs.novaza.ai/pay/</link><description>Recent content in Novaza Pay on Novaza Docs</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.novaza.ai/pay/index.xml" rel="self" type="application/rss+xml"/><item><title>Security &amp; Compliance</title><link>https://docs.novaza.ai/pay/security/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.novaza.ai/pay/security/</guid><description>&lt;h1 id="security--compliance"&gt;Security &amp;amp; Compliance&lt;a class="anchor" href="#security--compliance"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Novaza Pay is designed so that sensitive payment instrument data never touches the Novaza workspace, Novaza Billing, or any customer-facing Novaza application. All handling of card numbers and bank account numbers is performed under the PCI-DSS compliance envelope of the upstream processing partners that Pay routes to.&lt;/p&gt;
&lt;h2 id="tokenization"&gt;Tokenization&lt;a class="anchor" href="#tokenization"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;When a customer adds a card or bank account to their workspace, the payment details are submitted directly to the upstream processor over a secure channel. The processor returns an opaque token that represents the payment method. Only the token, along with non-sensitive metadata (card brand, last four digits, expiry month and year), is stored on the Novaza side.&lt;/p&gt;</description></item></channel></rss>