Skip to main content
Use bulk shipping when multiple physical cards should go to the same receiving address in one shipment. You configure addresses on the Business API, then send the address id as bulkShippingGroupId on each physical issue call. The API does not attach a tenant default group when you issue a card. Omit bulkShippingGroupId and the card ships individually, even if a default address exists.

Configure receiving addresses

All routes require an approved KYB token. The first address you create becomes default. You can also send isDefault: true on create.
POST /cards/bulk-shipping-addresses
Response includes a local id. Use that id as bulkShippingGroupId on issue.
Create response
GET /cards/bulk-shipping-addresses/default

Issue physical cards into a group

Keep per-card shippingAddress as today. Rain still needs an individual delivery address on each card inside the bulk box. Send bulkShippingGroupId set to the address id (from create, list, or GET .../default) together with shippingAddress:
Issue physical card with bulk shipping
  • Unknown, deleted, or another tenant’s id returns 400.
  • Virtual cards must not send bulkShippingGroupId.
  • Omitting bulkShippingGroupId ships that card individually.
The group is set at card create time and cannot be changed later.

Editing an address

PATCH updates your stored address. The local id stays the same — keep sending that same id as bulkShippingGroupId on later issue calls. Setting default (POST .../{id}/default) only flips isDefault among your addresses.

Address characters

Recipient and address text must be Latin characters that Rain accepts: a-z, A-Z, 0-9, space, and . , # ' / & ( ) ° -.

Rain grouping notes

Cards share a bulk shipment when they use the same address id (as bulkShippingGroupId) and the same productRef (product). Rain groups cards submitted before 12:00 PM EST Monday–Friday. Bulk fulfilment requires at least two cards in the group.