--- title: "Connecting RD Station to Qualy" description: "How the Qualy–RD Station integration works—a one-way sync of customers into RD Station contacts with custom fields for visas and payment status, payments as conversion events for automations, and matching by email." lastModified: "2026-08-27" lang: "en" wordCount: 654 url: https://qualyhq.com/training/integrations/rd-station --- ## Site navigation - [For schools](/international-education/for-schools.md) — For international education schools - [For agents](/international-education/for-education-agents.md) — For international education agents - [Explore](/training.md) — Watch videos on how to use Qualy - [About](/about.md) — Learn about Qualy's mission and values - [Pricing](/pricing) - [5-min demo](/demo.md) - [Login](https://dashboard.qualyhq.com) # Connecting RD Station to Qualy > Feed your Qualy customers and their payment status into RD Station marketing automations. ## At a glance - **Intended for:** Marketing - **Category:** Marketing (Brazil) - **Reading time:** 4 minutes - **Last updated:** 12th July 2026 ## Quick summary Connect RD Station in Settings → Add-ons & integrations. Qualy keeps your RD Station contacts in step with your customers—one-way, from Qualy to RD Station. Each contact carries custom fields for the Qualy number, visa details and payment status (amount due, number overdue, next due date, next payment and a pay link), and every payment is sent as a conversion event you can trigger automations on. Contacts match by email. One setup note: the Qualy custom fields must exist in your RD Station account—we create these with you during onboarding. ## Overview The RD Station integration feeds your Qualy customers—and their payment status—into **RD Station** marketing automation, so your campaigns can react to real payment data. It's a **one-way** sync, from **Qualy to RD Station**. ## What reaches each contact - **Standard details** — name, email, phone, city, state and country, plus tags - **Custom fields** — the Qualy number, birthday, address and visa details (issue, expiry, country) - **Payment fields** — amount due, number overdue, next due date, next payment and a pay link - **Conversion events** — each payment is sent as a conversion event, identified by its status, ready to trigger flows ## Building automations Between the **payment custom fields** on the contact and the **conversion events** for each payment, you can build automations that respond to where a student is financially—an approaching due date, an overdue balance, or a completed payment—and use the pay-link field to send them straight to checkout. Segment by **visa expiry** for renewal journeys, or by **overdue balance** for a reminder flow. The fields are there to filter and automate on. ## A setup note about custom fields Qualy writes into **custom fields that must already exist** in your RD Station account—there's no auto-creation. We set these fields up with you during onboarding. If the Qualy payment fields look empty, that's the first thing to check. ## Matching and reliability Contacts are matched—and created or updated—by **email address**, so keeping emails correct is what makes the sync land on the right contact. Qualy refreshes its RD Station access automatically; if RD Station permanently rejects that authorisation, Qualy disconnects the integration rather than keep failing—reconnect it from **Settings → Add-ons & integrations**. ## Frequently asked questions ### Does RD Station sync both ways? No—it's one-way, from Qualy to RD Station. Qualy keeps your RD Station contacts current; changes in RD Station don't flow back to Qualy. ### What reaches each contact? Standard details (name, email, phone, city, state, country) and tags, plus custom fields for the Qualy number, birthday, address and visa details, and payment custom fields—amount due, number overdue, next due date, next payment and a pay link. ### How do payments show up for automations? Each payment is sent to RD Station as a conversion event, identified by its status, so you can trigger flows on it—alongside the payment custom fields on the contact, which you can segment and automate on directly. ### My payment fields in RD Station are empty. Why? The Qualy custom fields have to exist in your RD Station account for Qualy to write to them—there's no auto-creation. We set these up with you during onboarding; if they're empty, that's the first thing to check. ### How are contacts matched? By email address—Qualy upserts the RD Station contact for that email. Keep emails correct so the right contact is updated. ### My RD Station connection dropped. What happened? If RD Station permanently rejects the stored authorisation, Qualy disconnects the integration rather than keep failing. Reconnect it from Settings → Add-ons & integrations. ## Prefer doing this via the Qualy API? Head over to our developer docs for everything you need—endpoints, examples, and simple how-tos. [View API Docs](https://docs.qualyhq.com/docs) ## More on Qualy **Industries** - [For schools](/international-education/for-schools.md) — For international education schools - [For agents](/international-education/for-education-agents.md) — For international education agents **Support** - [Training](/training.md) - [System status](https://qualyhq.statuspage.io/) — Qualy system status - [Product updates](https://changelog.qualyhq.com) — As we work on Qualy, here we spotlight what we’ve learned and updated across our products - [Contact](/contact-us.md) **Product** - [Demo](/demo.md) - [Enterprise](/enterprise.md) - [Testimonials](/testimonials.md) — Learn what some customers have to say about Qualy - [About](/about.md) — Learn about Qualy's mission and values - [Blog](/blog) — International education payments blog by Qualy - [Trust center](/trust.md) - [API](/api.md) — Qualy API for international education payments - [Zapier](/zapier.md) — Connect Qualy to 7,000+ apps with Zapier - [NexPay](/nexpay.md) — Qualy + NexPay — automate everything around the payment **Legal** - [General terms](/terms-and-conditions.md) - [Payer terms](/terms-for-payers.md) - [Privacy policy](/privacy-policy.md) - [BECS DDR](/becs-dd-service-agreement.md)