With this service, the calling apps can check corresponding Cards that belongs to the CUSTOMER REF provided in the payload. In effect, take takes a customer ref and try to fetch all card attached to it. OnePipe will forward to the provider’s dedicated implementation. Providers will either use the CUSTOMER REF sent to fetch the corresponding card belonging to customer.
...
Sequence of calls
App calls
/transactwith the account number they want to lookup in the details object.auth.typeis expected to be nulltoken, account_number.Provider responds with any of the completion codes
SuccessfulorFailed.
...
| Code Block | ||
|---|---|---|
| ||
{
"request_ref":"{{request_ref}}",
"request_type":"lookup_cards",
"auth": {
"type": nulltoken,
"secure": null"9327691266219107,
"auth_provider": "BeeceptorMasterPass",
"route_mode": null
},
"transaction": {
"mock_mode": "live",
"transaction_ref": "{{transaction_ref}}",
"transaction_desc": "A random transaction",
"transaction_ref_parent": null,
"amount": 0,
"customer":{
"customer_ref": "{{customer_id}}", // Major Parameter to be used on the provider
"firstname": "Uju",
"surname": "Usmanu",
"email": "ujuusmanu@gmail.com",
"mobile_no": "234802343132"
},
"meta":{
"a_key":"a_meta_value_1",
"another_key":"a_meta_value_2"
},
"details": {
"account_number":"3065570057"
null
}
}
} |
Response
| Code Block | ||
|---|---|---|
| ||
{
"status": "Successful",
"message": "Transaction processed successfully",
"data": {
"provider_response_code": "00",
"provider": "Beeceptor",
"errors": null,
"error": null,
"provider_response": {
"cards": [
{
"sourceOfFunds": {
"provided": {
"card": {
"brand": "MASTERCARD",
"expiry": "0521",
"fundingMethod": "DEBIT",
"issuer": "FISERV SOLUTIONS, LLC",
"number": "511111xxxxxx1118",
"scheme": "MASTERCARD"
}
},
"type": "CARD"
},
"status": "VALID",
"token": "9327691266219107",
"usage": {
"lastUpdated": "2020-07-28T12:47:33.698Z",
"lastUpdatedBy": "OLTIO4MTN1",
"lastUsed": "2020-07-28T12:47:33.709Z"
},
"verificationStrategy": "BASIC"
},
],
"reference": "000022200225154318222333334432",
"meta":{
"field_key":"field_value",
"field_key":"field_value"
}
}
}
} |
Breakdown of the
...
auth type
For this service, the details object will have auth type can be any of the following:
Field | Type | Requirement | Description | |
|---|---|---|---|---|
token | string | required | Expect | |
account_number | stringnumeric | optional | The account number to lookup.required | Expect |
Possible status response codes
...