Skip to main content

​
Terms - Integrating Machines Card

​
Partner Branding and Compliance Requirements

These requirements apply to all partners integrating Machines virtual card infrastructure under the Machines Partner Integration.
White-label usage is not permitted.
Production API access is conditional on compliance with the requirements below.

​
1. Brand Visibility Requirements

The Machines brand must be clearly visible anywhere the card product is displayed or marketed. Minimum requirements:
  • The Machines logo must be present on the card visual.
  • The Machines wordmark must be visible within the card interface or card details view.
  • The product must not be presented as solely the partner’s proprietary card.
The following disclosure is required:
“This card is powered by Machines and is subject to Machines Terms of Service and Privacy Policy.”
This disclosure must be clearly visible before card issuance. Before issuing a card, the end user must:
  • Explicitly accept Machines Terms of Service.
  • Explicitly accept Machines Privacy Policy.
  • Be informed that they are becoming a Machines cardholder under the Machines card program.
Checkbox acceptance must not be pre-selected. Links to the following must be provided at the point of acceptance:
  • Machines Terms of Service
  • Machines Privacy Policy

​
3. Card Design Requirements

Allowed:
  • Custom card background color.
  • Limited visual customization, subject to approval.
  • Co-brand layouts where Machines branding remains clearly visible.
Not allowed:
  • Removal of the Machines logo.
  • Removal of the Machines wordmark.
  • Designs that imply the card is issued solely by the partner.
  • Alterations to regulatory or issuer disclosures.
Final card design must be approved by Machines prior to production activation.

​
4. Compliance Structure

Partners may not:
  • Resell Machines card access.
  • Sub-license API access.
  • Offer card issuance outside approved flows.
  • Modify KYC, AML, or compliance flows.
All issuance must:
  • Flow through Machines infrastructure.
  • Use Machines compliance logic.
  • Follow issuer guidelines provided by Machines.

​
5. API Key Controls

  • Development keys may be issued for testing.
  • Production keys are granted only after:
    • Branding review
    • UX review
    • Compliance flow review
    • Legal acceptance verification
Machines reserves the right to suspend or revoke API keys if requirements are not met.

​
6. Marketing and Announcements

Any public announcement referencing the card must:
  • Clearly state the card is part of Machines Card Program.
  • Avoid implying exclusive ownership by the partner.
  • Not misrepresent the issuer or program structure.
Marketing materials may require prior review.

​
7. Enforcement

Failure to comply may result in:
  • Suspension of production API access.
  • Immediate key revocation.
  • Termination of partner access.
These requirements should be implemented and validated before requesting production activation.