Move saved payment methods from Versapay or NMI
Updated 4 days ago
Move your recurring giving from Versapay or NMI to Gratona while preserving amounts and collection dates. Identify the gateway, affiliate and integration that currently manage your recurring payments.
Before you begin
This guide covers what is specific to Versapay and NMI. The shared steps are in the migration overview; have these in place first:
Onboarding path chosen. Growth plans and above require guided or white-glove onboarding. “Migration coordinator” below means your organization’s lead or the Gratona owner named in your onboarding plan; use their email in the samples.
Stripe connected to Gratona and its account ID noted, as in Prepare payments for your migration.
Donor emails paused with the email pause instructions, before any records are imported.
Your account holder authorizes the provider release. Existing collections keep running until the approved switch.
1. Identify the gateway and its owner
Record your gateway name and ID, current affiliate or reseller, and destination Stripe account. Ask Versapay or your reseller to coordinate the NMI request; NMI’s current instructions require the affiliate partner to initiate it.
2. Check the systems that trigger payments
Confirm whether recurring payments depend on an ERP or accounting integration, such as NetSuite. The payment gateway may not continue charging on its own after that integration is disconnected, so agree on how collections will continue while the transfer is prepared.
3. Arrange the secure transfer
Open a request with Stripe and connect it to your source-provider case. The providers exchange keys, credentials and compliance documents through their approved channel, following the shared secure upload step.
NMI’s current export instructions cover eligible data, minimum record counts, pricing and approval requirements. These are the points that shape your request:
NMI requirement | What it means for you |
|---|---|
Who approves it | After the affiliate partner initiates the export, its authorized contact approves it. |
Minimum size | NMI’s published minimum is 25 records. |
Part of the vault | For a subset, provide a CSV of customer-vault or subscription IDs. The file lists IDs, not full card data. |
Receiving provider documents | Stripe, as the receiving provider, supplies its PCI Level 1 Attestation of Compliance and public PGP key. Ask Stripe for its current Level 1 PCI Attestation of Compliance if the source team requests it. |
Price and date | NMI lists export pricing separately from imports and internal gateway transfers, which are different services. Obtain a written quote and schedule for your scope before authorizing it. An NMI import estimate is not an export turnaround promise. |
Request to your affiliate partner
Hello,
Please arrange a copy of our NMI customer-vault and recurring payment data for transfer to Stripe.
Organization: [organization]
Gateway name and ID: [gateway]
Destination Stripe account: [verified acct_ ID]
Authorized account contact: [name and business email]Please initiate NMI’s export request and send the authorization, quote and available dates. [Export all records / export the customer-vault and subscription IDs in the attached scope list.] Existing recurring donations should remain active.
Please encrypt the payment-data export with Stripe’s current public PGP key and upload it using the SFTP credentials supplied by Stripe for this migration. Please send Stripe your public PGP key so Stripe can encrypt the SFTP credentials for your export team. Confirm the upload date, record count and any excluded records on the support case.
Please copy [migration contact email] on your reply.
Thank you,
[account holder]
Submit the receiving Stripe request
Follow the Stripe intake and approval steps in Prepare payments for your migration. Use the receiving account connected to Gratona and keep the acknowledgment with this provider case.
Check the partner’s response
The response is complete when each of these is confirmed in writing:
The affiliate submitted the NMI request and the authorized contact approved it.
The source gateway ID and the all-records or subset scope match your request.
Stripe’s receiving contact and compliance documentation are accepted.
The quoted export charge and export date cover the intended vault and recurring records.
Any ERP or NetSuite dependency stays in place until its role in collections is covered by the switch plan.
Use the current NMI export policy when reviewing the quote.
4. Prepare schedules while the export runs
Could you please share a list of donors in Versapay with their payment schedules and amounts? Please include the next charge dates.
Separate the total recurring charge from its sponsorship allocations. Record next due dates, source references and any payments that fall during the transition. Treat gifts already in another Stripe account as a separate group.
5. Verify the export and start approved collections
Get written export confirmation, then reconcile the returned Stripe references with Gratona donors. Resolve mismatched account IDs and payment methods updated elsewhere. Allow time for matching and testing after the provider finishes its export.
Agree on the last source collection and first destination collection, then follow Launch and hand over your migration. It sets the order: collection readiness is confirmed, with Gratona’s confirmation for any historical imports; the source schedules for the group stop; then the Gratona schedules are activated.
What happens next
Ask for the source provider’s export date and record cutoff, and follow up on the same case after the promised date. If no date was given, your migration coordinator follows up after two business days. This is our follow-up schedule, not a promised provider turnaround.
Stripe’s reply and import times, and the time to allow after the export, are in Timing and follow-up in Prepare payments for your migration and in Stripe’s current process and timing.
Continue in Gratona
Complete the switch in step 5.
Use the receipt instructions to review and activate only the approved messages.
Keep the provider’s upload confirmation, mapping report and stopped-schedule confirmation in your migration record.