List the responsibilities that are actually changing
Start with one service and record its organization or account reference, current owner, billing contact, payment-method owner and next renewal date. These responsibilities may belong to different people. A developer leaving a project, an agency returning a website and a finance colleague taking over invoices are different handovers; write down which duties are moving.
For each duty, name the receiving person and the approval needed. Do not assume that sending a folder of invoices gives someone administrative access, or that granting access replaces the payment card. The output should be a short handover checklist with a person responsible for each item, not a shared document containing passwords.
Use the provider’s role-transfer mechanism
GitHub’s organization-ownership guidance provides a concrete example: establish another owner, confirm that person can reach the organization settings, update billing information where necessary and only then remove the departing owner. Its warning is explicit that leaving the organization does not itself remove the payment information on file. Apply that sequence to GitHub, not as an invented menu path for every service.
Find the equivalent official owner or billing-role instructions for the service you are handing over. Let the recipient accept the invitation with their own account and verify their access from that account. If the provider does not offer the required transfer, ask its support team about the appropriate process rather than sharing a login secret to imitate a role change.
Sources & further reading: [1]
Give billing access without assuming every role needs full control
GitHub documents a billing-manager role separately from full organization ownership. The exact availability depends on the account arrangement; for example, enterprise-owned organizations handle billing at the enterprise level. This illustrates why the recipient’s required billing scope should be checked before assigning a broader role.
Decide whether the receiving person needs invoices, payment-method changes, subscription changes or full service ownership. Match those duties to the provider’s documented permissions and verify the result together. A title such as project manager or finance lead outside the product does not automatically grant the corresponding permissions inside it.
Sources & further reading: [2]
Transfer records and the payment responsibility separately
Prepare a private packet containing the service reference, recent invoices, current contract term, next expected charge, invoice-recipient details, open billing questions and the masked payment-method reference. Record which documents are final and which amounts are estimates. Do not attach full card credentials, authentication codes, wallet recovery phrases or an Approval Plus account seed.
If the payer changes, have the authorized person update the merchant’s saved payment method using its own documented controls. Confirm the visible result and which future renewals it affects. Preserve any unsettled invoice as an explicit open item instead of assuming the new card settled it. Keep approval for the change alongside the confirmation, particularly when an agency’s card is being replaced by a client’s method.
Finish with proof of access and a named next action
Before the departing person’s service access is removed, ask the recipient to locate the actual billing settings and retrieve a recent invoice. Confirm the next renewal date, selected payment method and contact email. Note the date the handover was accepted and who will follow up on any outstanding issue. These checks should refer to the real account, not a screenshot from someone else’s session.
Approval Plus account access uses its own private seed; this guide does not create a shared workspace or a multi-user role system for that account. Use support for account-specific questions without transferring the secret. Finally, keep the service handover record separate from card replacement or funding records: changing who manages a subscription does not by itself issue a card, credit funds or confirm the merchant’s next payment.
Your questions, answered
Does leaving a service organization remove my payment card?
Do not assume that. GitHub specifically documents ownership departure and billing updates as separate steps; check the relevant provider’s actual process.
Should the new billing contact receive my Approval Plus seed?
No. Share non-secret invoice and payment references, and use legitimate provider roles for access. The account seed remains a private login credential.
What proves that the handover is ready?
The recipient can access the required settings with their own account, the intended payment update is confirmed, and the next renewal and unresolved items have named owners.
Sources & further reading
- GitHub: transferring organization ownership ↗Checked Nov 16, 2026
- GitHub: billing-platform roles and enterprise scope ↗Checked Nov 16, 2026
- Approval Plus: account and funding help ↗Checked Nov 16, 2026
- Approval Plus: support and privacy contacts ↗Checked Nov 16, 2026