Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
How Flip-Pay handles cookies and personal data, and what European websites must do to use it in a GDPR and ePrivacy compliant way.
Flip-Pay is a payment and checkout service. It is a payment and instalment service that lets merchants offer flexible payment terms at checkout. When it runs on a website it operates as a third party processor whose scripts, cookies and network requests are loaded into the browsers of your European visitors.
In a typical deployment Flip-Pay processes transaction and order amounts, fraud prevention signals, device identifiers and account data. Most of this information qualifies as personal data under the GDPR because it can be linked to an identifiable person, directly or through online identifiers stored on the device.
Any storage of or access to information on a visitor device is governed by Article 5(3) of the ePrivacy Directive, transposed into national law across the EU. The GDPR then governs the subsequent processing, so Flip-Pay must have a valid legal basis, a clear retention period and transparent information for the data subject.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
The strictly necessary functions of Flip-Pay can rely on contract or legitimate interest, but any analytics, marketing or personalisation cookies layered on top still require prior consent. Keep the essential and the optional layers clearly separated so the legal basis matches each purpose.
Flip-Pay processes payment data on infrastructure located in Australia, a third country without an adequacy decision. Transfers of personal data outside the European Economic Area need an appropriate safeguard such as an adequacy decision or Standard Contractual Clauses, together with a transfer impact assessment where required.
List Flip-Pay in your records of processing and your cookie policy, load it only through a consent management platform, document the consent you collect and review the vendor data processing agreement at least once a year. Test the site with consent refused to make sure no identifier is set before a choice is made.
Websites using Flip-Pay must obtain user consent under GDPR regulations.
DPIA considerations
Assess the volume and sensitivity of data processed through Flip-Pay, whether visitors are profiled or tracked across sites, and any transfer outside the EEA. A formal DPIA is advisable where Flip-Pay enables large scale monitoring or combines data from several sources.
Sample consent text
This site uses Flip-Pay to deliver core functionality. Optional analytics and marketing features of Flip-Pay are activated only with your consent, which you can change at any time in the cookie settings.
Third-party domains contacted
flippay.com.auflip-pay.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| flippay_session | necessary | Session | Maintains the checkout session |
| flippay_csrf | necessary | Session | Protects payment forms against cross site request forgery |
Flip-Pay uses cookies for user preferences — inform visitors with a consent banner.
Flip-Pay typically stores session identifiers and, depending on configuration, analytics or marketing cookies. The exact names and lifetimes appear in the cookie table on this page, and you should scan your own site because deployments differ.
For its strictly necessary functions Flip-Pay can rely on contract or legitimate interest, but any analytics or marketing cookies it adds still require prior consent.
The non essential cookies rely on consent under Article 6(1)(a) GDPR combined with Article 5(3) ePrivacy. Strictly necessary processing can rely on contract under Article 6(1)(b) or legitimate interest under Article 6(1)(f).
Flip-Pay processes payment data on infrastructure located in Australia, a third country without an adequacy decision. Any such transfer needs Standard Contractual Clauses or an adequacy decision and a transfer impact assessment.
A DPIA is required when processing is likely to result in a high risk, for example large scale tracking or profiling. Where Flip-Pay monitors behaviour at scale or combines data sources, run a DPIA before going live.
Load Flip-Pay only after consent through a consent management platform, keep it blocked by default, document each consent, list it in your records and cookie policy, and sign a data processing agreement with the vendor.
Yes. Depending on your goal you can choose privacy first or cookieless tools, or self hosted options that keep data in the EEA. Whichever you pick, the same consent and transparency duties apply.
Add Flip-Pay to the cookie policy with its purpose, the cookies it sets, their duration and the recipient, note any third country transfer and the safeguard used, and refresh the entry whenever you change configuration or after a new cookie scan.