This page explains how to add Zip to your existing iOS Drop-in integration.
Requirements
Requirement | Description |
---|---|
Integration type | Make sure that you have built your iOS Drop-in integration. |
Setup steps | Before you begin, add Zip in your test Customer Area. |
API reference
Select which endpoint you are using:
Drop-in configuration
Recurring payments
We support recurring transactions for Zip. To make recurring payments, you need to:
Create a token
To create a token, include in your /payments request:
storePaymentMethod
: true- shopperReference: Your unique identifier for the shopper.
When the payment has been settled, you receive a recurring.token.created webhook containing:
type
: recurring.token.createdshopperReference
: your unique identifier for the shopper.eventId
: thepspReference
of the initial payment.storedPaymentMethodId
: the token that you need to make recurring payments for this shopper.
Make sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.
Make a payment with a token
To make a payment with the token, include in your /payments request:
-
paymentMethod.storedPaymentMethodId
: ThestoredPaymentMethodId
from the recurring.token.created webhook.You can also get this value using the /listRecurringDetails endpoint.
-
shopperReference
: The unique shopper identifier that you specified when creating the token. -
shopperInteraction
: ContAuth. -
recurringProcessingModel
: Subscription or UnscheduledCardOnFile.
For more information about the shopperInteraction
and recurringProcessingModel
fields, refer to Tokenization.
Test and go live
Create Zip test accounts using the credentials on Zip's test credentials page. You can then use your test account to make a payment in the test environment.
Check the status of Zip test payments in your Customer Area > Transactions > Payments.
Before you can accept live Zip payments, you need to submit a request for Zip in your live Customer Area.