Subscription to Swift Go service
With Swift Go, financial institutions can enable their SME and retail customers to send predictable, fast, highly secure, and competitively priced low-value cross-border payments anywhere in the world, direct from their bank accounts.
If you are about to subscribe to Swift Go to implement the beneficiary role in Self-onboarding, please note that Swift has released the Project Navigator, to help you track progress and manage the Swift Go Onboarding. Remember to bookmark the Project Navigator and use it as your main starting point.
Ordering checklist
- The Customer Parent Destination (CPD) which will place the orders aims to provision the BICs of its own hierarchy, from the user category Supervised Financial Institutions (SUPE) or Payments System Participants (PSPA), into the Swift Go service.
- You must be authorized to use the ordering application before you can begin the process.
- All mandatory fields, as indicated by an orange triangle in the Swift Go e-forms, must be filled.
Note that below forms are categorized as “Swift Go for non-GPI customers” and “Swift Go for GPI customers”.
The parent destinations already subscribed to “Swift GPI” and “Swift Go for GPI customers” can complete the “Swift Go for non-GPI customers” e-forms to provision non-GPI SUPE/PSPA(1) entities from the group hierarchy in the Swift Go service.
(1) SUPE/PSPA includes: member, non-shareholding member, sub-member, supervised financial institution, payments system participant.
Place orders
Swift Go for non-GPI customers
The ordering and provisioning process is composed of the following 3 steps and must be followed sequentially:
1. Subscribe to the Swift Go service for non-GPI customers
This first e-form enables your non-GPI parent destination (CPD) to become a Swift Go customer and determine its preferred Swift Go onboarding approach.
2. Add non-GPI BICs in the Swift Go service in Test
This second e-form allows your parent destination (CPD) to determine which non-GPI SUPE/PSPA(1) BICs from its hierarchy should be provisioned in the Swift Go Closed User Group in the Test & Training environment.
3. Add non-GPI BICs in the Swift Go service in Live
This third e-form allows your parent destination (CPD) to determine which non-GPI SUPE/PSPA(1) BICs from its hierarchy should be provisioned in the Swift Go Closed User Group in the Live environment.
Subscribing to Live should be done after successfully completing testing in the Test & Training environment.
(1) SUPE/PSPA includes: member, non-shareholding member, sub-member, supervised financial institution, payments system participant.
Swift Go for GPI customers
The ordering and provisioning process is composed of the following 3 steps and must be followed sequentially:
1. Subscribe to the Swift Go service for GPI customers
This first e-form enables your GPI parent destination (CPD) to become a Swift Go customer and determine its preferred Swift Go onboarding approach.
2. Add GPI BICs in the Swift Go service in Test
This second e-form allows your parent destination (CPD) to determine which GPI SUPE/PSPA(1) BICs from its hierarchy should be provisioned in the Swift Go Closed User Group in the Test & Training environment.
3. Add GPI BICs in the Swift Go service in Live
This third e-form allows your parent destination (CPD) to determine which GPI SUPE/PSPA(1) BICs from its hierarchy should be provisioned in the Swift Go Closed User Group in the Live environment.
Subscribing to Live should be done after successfully completing testing in the Test & Training environment.
(1) SUPE/PSPA includes: member, non-shareholding member, sub-member, supervised financial institution, payments system participant.
