Flux hosted fields capture card data in origin-isolated iframes on payments.fluxpayments.com, so sensitive data never touches your servers or domain. You get a checkout customers trust and a much smaller PCI burden, backed by SAQ-D Level 2 coverage.
Why businesses use it
Card data off your systems
Fields render in origin-isolated iframes on payments.fluxpayments.com, so card data never touches your servers or domain.
Less PCI to carry
Hosted fields keep you out of an audited card environment, backed by SAQ-D Level 2 coverage.
Yours to style
Drop the fields into your own checkout and match your brand.
How it works
You embed the Flux fields where you want them in your checkout. The customer types their card into iframes served from payments.fluxpayments.com, Flux tokenizes and processes the payment, and your systems only ever see a token.
Simple, transparent pricing
Flux charges a flat 2.9% plus 30 cents per transaction, with volume discounts for higher-volume merchants and no setup fees or contracts. Accounts processing under $100,000 a year in card volume may be subject to a $20 monthly account fee. You can also pass the processing fee to the customer at checkout where local surcharging rules allow.
Frequently asked questions
How do hosted fields protect card data?
Card data is captured in origin-isolated iframes on payments.fluxpayments.com, so it never touches your servers or domain.
What PCI level does Flux hold?
Flux is SAQ-D, PCI DSS Level 2 certified.
Can I style the fields?
Yes. You place and style the fields inside your own checkout while the sensitive input stays in the isolated iframe.